Skip to content

ONI-Ops v0.4.7-beta

Pre-release
Pre-release

Choose a tag to compare

@ares-369 ares-369 released this 11 Nov 19:44
· 73 commits to 4b356a7dea28399c7a406adb04bcea890b6f4bc0 since this release

ONI-Ops v0.4.7-beta — pre-release (beta)

Security, assessment quality and deployment improvements. Beta software for
authorized security testing only; see DISCLAIMER.md and NOTICE.

Added

  • oni benchmark --demo-evaluation: a labeled, loopback-only fixture evaluation
    with precision/recall/F1, negative checks, one-to-one matching and stated
    fixture-only limits. Unverified detections do not count as true positives;
    duplicate alerts count as false positives.
  • Optional Playwright browser discovery (oni crawl) with bounded page/time
    budgets, in-scope request routing, read-only navigation and start-origin-only
    credential forwarding. It reports observed XHR/fetch status, content type and
    value-free form metadata.
  • Disposable Docker scanner workers with a non-root user, read-only filesystem,
    dropped capabilities, resource limits, timeouts and a fail-closed egress
    firewall. CI exercises allowed and denied egress and verifies Nmap/Nuclei
    startup. See Dockerfile.worker.
  • Offline Trivy scanning of images on the attack host (oni container-scan) and
    optional read-only AWS account, IAM, security group, EKS and S3 checks
    (oni cloud-audit aws).
  • Versioned network playbooks and AI probe packs with nested discovery and source
    hashes. See docs/SECURITY_PACKS.md.
  • Expanded OpenAPI BOPLA analysis for nested local references, compositions,
    arrays, OpenAPI 2 body/form parameters and OpenAPI 3 vendor schemas.

Fixed and hardened

  • Horizontal BOLA now requires evidence of object ownership; a user's own object
    read is not reported as a second verified cross-user finding.
  • Agent finding replay and zero-token retests enforce supported proof rules,
    reject malformed or out-of-origin paths, cap responses, disable redirects,
    and report 5xx outcomes as inconclusive.
  • Scope checks now validate full IPv4 CIDRs and ranges, including exclusions.
  • Network playbook steps are limited to supported scanner commands and must use
    the assessed {target}. Intrusive sqlmap and hydra packs require explicit
    safety: intrusive scope configuration.
  • AWS security-group rules without TCP/UDP ports, such as ICMP, are no longer
    treated as exposing all ports.

Upgrade note

  • The Docker worker requires a user-defined bridge network. IPv4-only kernels
    are supported; IPv6 scopes fail closed when IPv6 is unavailable.