Repository navigation
ReproCase 1.1.0-beta.2
Pre-releaseImportant
Newer versions are available. See the latest releases for the current download.
HTTP 200 is not proof of an IDOR. ReproCase checks whether the boundary was actually crossed.
This beta takes ReproCase beyond Windows and into Burp Suite, adds ready-made case templates, and makes every download verifiable.
New
- Docker (Linux, macOS, Windows). Run the workbench, case runner and demo lab with headless Chromium:
Open the
docker run --rm -p 127.0.0.1:4317:4317 ghcr.io/theasbug/reprocase:1.1.0-beta.2
http://localhost:4317/#token=...URL from the logs. Usedocker compose upfrom a checkout to keep data in a volume. - Burp Suite extension. Install
reprocase-burp-0.1.0.jar(Extensions → Add → Java), point it at ReproCase'sruntime.json, then right-click requests → Send to ReproCase. The selection becomes a case draft. Nothing is sent to the target, and captured session credentials are not copied into the case. Guide - Case templates. Schema-valid starting points for horizontal IDOR (read and write) and vertical privilege / BFLA in
templates/. - Verifiable builds. The Windows archive, source archive, Burp jar and container image are built by GitHub Actions from this tag, with signed build-provenance attestations:
gh attestation verify ReproCase-1.1.0-beta.2-Windows-x64.zip --repo theasbug/reprocase
Changed
- The README is rewritten around reproducible IDOR/BOLA proofs. The AI assistant and recon utilities are still included, as optional extras.
- Moderate
minimatch/globadvisories are resolved in the packaging dependencies (npm audit: 0).
Download
| File | For |
|---|---|
ReproCase-1.1.0-beta.2-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.2-source.zip |
Source archive |
ReproCase-1.1.0-beta.2-SHA256SUMS.txt |
Checksums |
The Windows executable is not code-signed yet. Verify it with the checksum file or gh attestation verify. Keep ReproCase-data when upgrading: extract the new version into a separate folder and copy your data across (desktop notes).
Try it in two minutes: load the built-in demo, run it (Reproduced), refresh the identities and run again (Reproduced), then switch to the secure target (Not reproduced). No API key needed. Found something confusing? Five-minute beta test.
Full changelog: v1.1.0-beta.1...v1.1.0-beta.2