Latest lab write-up. Came out a bit long but very informative.
https://medium.com/@marduk.i.am/blind-sql-injection-with-conditional-responses-46ee90b5f2c0
Quickest way to reliably find business logic flaws is to change your mindset:
You're not looking for bugs, you're hunting for assumptions.
Somewhere out there, a dev assumed no one would ever do *that*. So be the first person to do it.
The Seven Stages of Bug Bounty grief
1.) Bug Bounty customer writes up rules and launches a program
2.) Bug bounty platform invites hackers
3.) Hacker provides a handful of findings
4.) Customer: “No not like that!”
5.) Hacker adds a few dozen findings that highlight a similar problem
6.) Customer: “Now listen here you little shi-“
7.) Hacker moves onto other programs - and possibly other platforms I am here
This is where Bug Bounty Platform reputation amongst the hacker community (which is - effectively - the "product") really matters. When customers sign-up to engage with security researchers through a platform so they can "check the box" that their application has been tested, and then abuse the trust that the hacker community has placed in the platform, everyone loses.
I know that Casey Ellis and co. at Bugcrowd as well as Jobert Abma and co. at HackerOne work hard to make sure that their customers are ready for what the hacker community will inevitably throw at them - but there are definitely times where a customer clearly signals that they never wanted the findings. They wanted to check the box.
And at the end of the day, if the hacker community gets mistreated by a customer, word will absolutely get around - and those hackers will vote with their feet.
I interview a hacker who hacked NASA in 60 seconds and he shows us how (a Real World Tutorial).
YouTube video: https://youtu.be/ZpdgqsviAiA
In bug bounty, nothing is as valuable as a good Proof of Concept to easily prove impact.
Recently, I wanted to showcase a simple Login CSRF (missing OAuth 2.0 "state" or PKCE) while using Google SSO.
This is the minimal NodeJS PoC I came up with: https://gist.github.com/lauritzh/90d68c0b68652882648e0ca9b8b6683e
Netflix — Bypassing Multi-Factor Authentication (MFA) - by @lyubo_tsirkov
Password Reset Poisoning with Host Header Injection
https://infosecwriteups.com/password-reset-poisoning-with-host-header-injection-345b902a9ca5
Bugbounty hunters/Pentesters life
How I fuzz and hack APIs?
Understanding the API
Where to fuzz and how to fuzz?
SSRF bypass list:
-------
Base-Url: 127.0.0.1
Client-IP: 127.0.0.1
Http-Url: 127.0.0.1
Proxy-Host: 127.0.0.1
Proxy-Url: 127.0.0.1
Real-Ip: 127.0.0.1
Redirect: 127.0.0.1
Referer: 127.0.0.1
Referrer: 127.0.0.1
Refferer: 127.0.0.1
Request-Uri: 127.0.0.1
Uri: 127.0.0.1
Url: 127.0.0.1
X-Client-IP: 127.0.0.1
X-Custom-IP-Authorization: 127.0.0.1
X-Forward-For: 127.0.0.1
X-Forwarded-By: 127.0.0.1
X-Forwarded-For-Original: 127.0.0.1
X-Forwarded-For: 127.0.0.1
X-Forwarded-Host: 127.0.0.1
X-Forwarded-Port: 443
X-Forwarded-Port: 4443
X-Forwarded-Port: 80
X-Forwarded-Port: 8080
X-Forwarded-Port: 8443
X-Forwarded-Scheme: http
X-Forwarded-Scheme: https
X-Forwarded-Server: 127.0.0.1
X-Forwarded: 127.0.0.1
X-Forwarder-For: 127.0.0.1
X-Host: 127.0.0.1
X-Http-Destinationurl: 127.0.0.1
X-Http-Host-Override: 127.0.0.1
X-Original-Remote-Addr: 127.0.0.1
X-Original-Url: 127.0.0.1
X-Originating-IP: 127.0.0.1
X-Proxy-Url: 127.0.0.1
X-Real-Ip: 127.0.0.1
X-Remote-Addr: 127.0.0.1
X-Remote-IP: 127.0.0.1
X-Rewrite-Url: 127.0.0.1
X-True-IP: 127.0.0.1
-----
https://twitter.com/0dayCTF/status/1556279777455386627?t=Z51UbhiolM5RuAww32v3Ww&s=19
Credit: @0dayCTF
OSCP Preparation Guide by
@0xSh1v4
How `he` cleared OSCP in his First Attempt
0xsh1v4.github.io/posts/oscp/
Bypassing OGNL sandboxes for fun and charities
OGNL injections led to some serious remote code execution (RCE) vulnerabilities
https://github.blog/2023-01-27-bypassing-ognl-sandboxes-for-fun-and-charities/
FirebaseExploiter
a vulnerability discovery tool that discovers Firebase Database which are open and can be exploitable
Primarily built for mass hunting bug bounties and for penetration testing.
OTP Bypassing and Vulnerabilities from Email fields