Skip to content

ReproCase 1.1.0-beta.4

Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 14 Nov 16:14
· 20 commits to main since this release

Important

Newer versions are available. See the latest releases for the current download.

Prove an IDOR in four steps, on an API ReproCase has never seen.

Until now, a real target meant describing its mechanism by hand: about 25 fields, a dozen of them JSON Pointers. Quick proof learns the mechanism by watching instead. You give it the target, two test accounts and two pasted requests.

New: Quick proof

  1. Accounts. Paste a session for two test accounts you control: any auth header (Authorization, X-Auth-Token, …), a Bearer token, or a cookie.
  2. Identity. ReproCase calls common "who am I" endpoints with both accounts and finds the account ID and organization fields by comparing the answers. Wrong guess? Click the right field.
  3. Requests. Paste the request that creates an object and the vulnerable request that reads it by ID, straight from Burp or DevTools. Headers are ignored, so captured cookies are never stored.
  4. Result. ReproCase creates one object as account A and learns where the new ID, the owner and a marker field are. It detects CSRF tokens if needed, previews account B's access, deletes the object and saves the case.

You then review the policy, approve and run. The verdict comes from the normal run: a fresh object, a unique marker, verified accounts.

Quick proof result

New for triagers: Verify on my site

Import the reporter's .reprocase.json, enter your API origin and one credential per test account. If your identity endpoint or fields differ from the reporter's, ReproCase finds them and saves a new case revision, so there's no JSON to edit. The reporter's policy acknowledgement is not imported: you read the claim and approve it yourself.

Also

  • Any custom auth header for account sessions, not only Bearer tokens and cookies.
  • A read witness can now check that the response contains the run marker anywhere, so no response field location is needed.
  • Imported and recon drafts no longer require a /role field.
  • Target-facing verification runs one at a time per case.

How it was tested: on a second lab deliberately shaped unlike the demo: /api/v1/profile, wrapped UUID objects, an X-Auth-Token header, x-xsrf-token CSRF and 401 denials. Results: reproduced, not reproduced, cross-user and same-person inconclusive all came out correctly, both through the API and by clicking through the UI. 159 unit/integration tests and 8 browser tests pass.

Current limits: Quick proof covers read IDORs with the object ID in the URL path. Use Advanced case for write IDORs or role checks.

Download

File For
ReproCase-1.1.0-beta.4-Windows-x64.zip Windows portable app. Extract the whole archive and open ReproCase.exe.
reprocase-burp-0.1.0.jar Burp Suite extension (Java 17+)
ReproCase-1.1.0-beta.4-source.zip Source archive
ReproCase-1.1.0-beta.4-SHA256SUMS.txt Checksums

Docker: docker run --rm -p 127.0.0.1:4317:4317 ghcr.io/theasbug/reprocase:1.1.0-beta.4

Verify: gh attestation verify ReproCase-1.1.0-beta.4-Windows-x64.zip --repo theasbug/reprocase. The Windows executable is not code-signed yet. When upgrading, extract into a new folder and keep your ReproCase-data.

Full changelog: v1.1.0-beta.3...v1.1.0-beta.4