Repository navigation
ONI v0.4.3-beta
Pre-release
Pre-release
ONI v0.4.3-beta is a correctness and security fix release. If you run 0.4.1-beta or 0.4.2-beta, please upgrade.
Fixed
- Retests could report a still-present vulnerability as FIXED. Since 0.4.1-beta, credentials inside replay commands were masked in the database itself. Retesting an authenticated finding (for example an authenticated BOLA) therefore sent
[REDACTED-TOKEN], received a 401, and marked the issue as fixed. Replay commands are now stored intact, and secrets are masked wherever a finding leaves the server (UI, API, CLI and retest responses).- Findings saved by 0.4.1–0.4.2 whose credential was already masked will refuse to retest, with a clear message, instead of guessing. Re-run the assessment with the auth header to retest them.
- No more "FIXED" from failed retests. A 401 on an authenticated retest now reports UNCONFIRMED (the credential may have expired). If a retest cannot run at all (attack host unreachable, timeout, scope refusal), the finding is left unchanged.
- Access control. The full database backup (
/api/backup/download) and the attack-host SSH check (/api/doctor?runner=1) are now admin-only. Previously the read-onlyviewerrole could download the entire database.
Changed
- The "benchmark" added in 0.4.1-beta is renamed to validator self-test (
oni selftest,GET /api/selftest; the old names still work). It checks ONI's own validators against built-in example inputs and reports pass/fail per check. It no longer reports precision, recall or F1: those figures described the built-in examples, not how well ONI finds real vulnerabilities. A benchmark against real vulnerable applications is planned.
The 0.4.1-beta and 0.4.2-beta changelog entries have been annotated with these corrections. Full details: CHANGELOG.md.
Please note
ONI is beta software. Treat findings as leads to verify, and open an issue if something looks wrong. ONI is for testing systems you own or are explicitly authorized to test; see DISCLAIMER.md.