Change one number, read another customer’s data

Hands on a keyboard under a network graph on a dark screen, a security key on the desk

Broken object-level checks are simple to test by hand, and scanners still miss most of them. The request looks valid, so the tool has nothing to flag.

The routine needs two ordinary accounts and a proxy. Nothing else. We ran it on a freight payments platform this year and read any customer’s invoices by changing one number.

The routine

  1. Sign in as customer A and record every request that carries an ID.
  2. Sign in as customer B and replay those requests with B’s session.
  3. Note each one that returns A’s data.
  4. Repeat with the read, change and delete versions of the same call.

Being signed in tells the server who you are. It says nothing about what you may read.

The fix

Check ownership on the server, on every object, in one shared place. Long random IDs make guessing harder, but they do not fix the check. We test the check again on the retest, and we use new IDs when we do.

About the author

Adaeze leads web and API testing at Wardline and does most of her best work by hand. Fictional author, demo content.

Related field notes