~/deadhead.blog web · api · mobile · bug bounty
All posts

What a report has to prove

Most rejected reports aren't wrong. They stop one step short.

Process · 2 min read

A report isn't a description of odd behaviour. It's an argument that someone can do something they shouldn't. Most of my unpaid hours have gone into that gap.

Name the actor#

One sentence: who can do what, to whose thing, by doing what. If you can't fill all four slots you have an observation.

Observation Finding
The server reflects any Origin with credentials. An attacker-controlled page can read any logged-in user's address book via a credentialed request to /api/contacts.
The endpoint accepts arbitrary JSON fields. A standard user can make themselves org admin by adding "role":"admin" to their own profile update.
/api/invoices/1042 returns a document. A user in tenant B can read tenant A's invoices by changing the id, which isn't scoped to the session.

Left column is true and unpaid.

Writing the sentence first also tells you what evidence you're missing. If it says "any logged-in user", you need a second account.

A precondition isn't a vulnerability#

Dangling DNS at an unclaimed bucket is a precondition; claiming it is the finding. A reachable use-after-free is a precondition; executing it is the finding. Cross-tenant access you inferred from a 200 is a precondition; the other tenant's object in your hands is the finding.

If you didn't execute it, put "primitive only" in the first paragraph. Vendors close these with some version of "try to claim it and let us know", which means the work was one step away and you filed early.

Read your own impact paragraph and ask whether you did that or concluded it.

Baselines#

Two controls before the interesting request. One that must fail, one that must succeed.

GET /api/invoices/9999999 HTTP/1.1      # must fail: no such object
GET /api/invoices/1042 HTTP/1.1         # must succeed: mine
GET /api/invoices/1043 HTTP/1.1         # the question: someone else's
404  {"error":"not_found"}
200  {"id":1042,"total":"81.40","tenant":"b"}
200  {"id":1043,"total":"2140.00","tenant":"a"}

Without the first two lines the third proves nothing. With them the 404 shows the API distinguishes absent from present, and the 200 on 1042 shows what a legitimate read looks like.

Read the whole error

A 400 can be schema validation running before the authz check, so a non-403 doesn't mean auth passed. "Not found" can mean "denied". Get an object you know exists and don't own before calling an unauthenticated 404 a missing check.

What triage is doing#

Deciding in a few minutes whether to spend engineering time, by trying to reproduce you. Anything that slows that down reads as noise, and noise correlates with reports that don't hold up. A setup step that fails by design. Three alternative payloads. A video where a transcript would do.

Re-pull the known-issues list before you send, and put the URL and pull date in the report. A dedup check against a three-month-old list isn't one.