Skip to content
All tags

#web-security

4 posts

Bug Bounty from Zero: Series Guide — Walking Through XSS, Memory, VM Escape, TEE, and AI Bounty Payouts in Plain Language

This is the reading entry point for the `Bug Bounty from Zero` series (parts 0–14). Each post covers one decision in plain language, backed by verifiable official sources, for readers with no security background.

A Bug Bounty Workbench: Capture Requests, Change Parameters, and Check Authorization

Replay the control, then change one field; a status code or reflected text alone is not vulnerability proof.

The Two Most Common Web Bugs, XSS and IDOR, and Why Google Pays Them Differently

XSS happens when a site puts user input into a page unchanged, so another person's browser runs it as code; the fix is escaping on output. IDOR happens when a server hands over whatever id it is asked for without checking the record is yours; the fix is an ownership check on the server. Google's table puts XSS under 'execute code on the client' (C0), $10,000 base on a standard Google app, and IDOR under logic flaws (S2), priced by how sensitive the exposed data is: on the same standard Google app, $3,133.7 to $31,337.

Giving an Agent Access to Logged-In Websites: Sessions, Permissions, and Automation Boundaries

Authenticated browser state is not a convenience setting; it is a credential that can impersonate its owner. Use a dedicated low-privilege account and isolated profile, separate reading from reversible writes and high-risk transactions, and leave MFA plus final submission to a human.