@zomasec@GodfatherOrwa جزاكم الله خيرًا. أنا كنت لخصت أغلب فيديوهات Orwa في صفحة Notion وساعدتني كتير وأنا بتعلم Recon، وحابب أشاركها لعلها تفيد أي حد بيبدأ. بس الرابط مش راضي يتحط في التعليقات على اليوتيوب، فلو حضرتك ممكن تضيفه في تعليق مثبت عندك هتفيد الناس
https://t.co/4cH5DGX3s9
New video is live.
Shopify Account Takeover via Email Verification Bypass $22,500 Bug Bounty PoC.
This wasn’t about injection or RCE.
It was a pure business logic flaw in the email verification flow that led to ATO.
🎥 https://t.co/IVBxmM2F9M
#BugBounty#CyberSecurity
Power of Yandex Dorking 🚀🚀🚀🚀
Tips- use Google Dorking Context into Yandex Search Query
Example: Site:https://t.co/DSqIYQGA6l ext:pdf,aspx,csv and Search 🔍
Don’t forget to Leverage it
Big shout out @Olamdeen@4osp3l@GodfatherOrwa@fattselimi@badcrack3r
Introducing my Bug Bounty Masterclass. 100% free.
I've made $2,000,000+ finding security bugs. I spent the last year turning my methodology into a complete blueprint.
4 hours of video - foundations, reconnaissance, web proxies, hands-on challenges, and certification.
Finish it in a weekend and start hacking real-world applications 🐞
Have you ever tried to find JSON Web Token (JWT) bugs?
5 ideas to try 👇
> Change alg to "none" and strip the signature but keep the trailing dot
> “jwt_tool <JWT> --crack -d <wordlist>” to crack weak secret keys
> Change alg from "RS256" to "HS256", then sign with the server public key
> Kid manipulation: try path traversal like "kid": "../../dev/null"
> Reuse JWTs between environments (staging vs prod). The same secret may be used and you may be able to takeover production accounts 💥
DoS bugs in graphQL are fun!
When you run into a GQL (graph query language) instance when testing, check for DoS (denial of service) if it is in scope for the program. It is very common for developers to create a structure that can be queried recursively to cause resource exhaustion, be it CPU, memory, etc, leading to a denial of service for the either the entire graph endpoint or a subset of services/APIs that drive it.
What is graphQL?
Its basically an annoyingly structured query language built around JSON for calling APIs. Everything is explicit, case sensitive, and generally hates you. Hundreds of APIs can all be gated by a single graphQL instance, allowing developers to create queries or mutations that pull or update data points from multiple back end APIs in a single call. Most of the time the endpoint is "/graphql" or "gql"
How does this Denial of Service thing work?
I've found a bunch of these in my time in bug bounty. Its actually the first thing I check when I hit a graph endpoint. In its simplest form, lets say we have three different points of data: users, friends, and posts.
If we query the "users" object, we can request the friends of that user, and any posts the user has made. As we drill into the friends, we see it also lists the friends posts, and if we drill into posts, we see posts list the "user" object again so we can see who made it. What is the problem?
We can build a query that grabs users, and all its posts. Then for each user, all the friends, and all their posts. Then for each post for each friend, which user: pause here. Now we are back to users. So we nest it another layer deeper, for each user of each post of each friend, do it all over again.. and repeat, and repeat, and repeat. Then you run it once and the server dies. But don't actually do that.
The catastrophic nature of this type of query is multiplied by the data points you return, so if you find a single intensive/robust field and return it for each loop, that is enough to kill it. When testing this, start small (only one or two deep to gauge the server response time) so you don't hurt anything. If you are able to see that the response time is doubling or more, go ahead and stop and report it for safety.
The $8000 bounty was the best I've gotten for this particular bug, most companies aren't super keen to pay for denial of service bugs but they are real enough.
Here are a couple good explanations on this:
https://t.co/s68mSY8RRt
https://t.co/RvZ6TaPozb
#hacking #appsec #bugbountytips
Me and a friend just landed a bounty for an RCE using a technique I addict it earlier and have kept refining ever since. Grateful for the results. Alhamdulillah.
More here:
https://t.co/rcXoFYE8r7 or https://t.co/1uaYDcSjFb