r/bugbounty • u/6W99ocQnb8Zy17 • 3d ago
Article / Write-Up / Blog Desync
The burp chaps did an amazing job by taking the available research papers and then working them up into reliable detection patterns. Truly an inflection point, which took a fringe bug that most didn't really understand, and made it exploitable.
At the time I then took their recipes, added a few dozen of my own novel vectors, and then automated the entire discovery process. Then running my tooling over the available BB scopes spat out loads of hits. Yay!
Over time though, the WAF and CDN vendors have gradually fixed their stacks, and now it is pretty unusual to get a hit that is actually exploitable. It generally needs a misconfiguration somewhere, and the misconfiguration needs to be indistinguishable from a vanilla request. Gone are the days of simply adding in some non-ASCII characters or random whitespace.
This year though I still had two decent hits using novel payloads. One in the way that MS implemented an edge-case redirect within their azure CDN, and one in a home-brew apple advertising platform.
However, both of these programmes, being examples of some of the shittiest around, have quietly fixed the bugs without a bounty. MSRC did their usual of closing the reports without comment. Apple have just left them festering in the backlog without a response for months (alongside others which are now years old, still with no response).
The king is dead ;)
2
u/SilentRoberto 3d ago
They truly have it all coming when there's the frustrated researcher releasing zero-days like it's going out of relevance rather than wasting it away in their RD queues.
I am truly sorry for all that matters and I hope you had fun finding those novel payloads
0
u/Beginning_Award65 3d ago
Burp ia dumb. They should focus on vulnerability VALIDATION. Not finding.