oniops 0.4.9b0__tar.gz
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- oniops-0.4.9b0/CHANGELOG.md +429 -0
- oniops-0.4.9b0/DISCLAIMER.md +49 -0
- oniops-0.4.9b0/LICENSE +202 -0
- oniops-0.4.9b0/MANIFEST.in +6 -0
- oniops-0.4.9b0/NOTICE +43 -0
- oniops-0.4.9b0/PKG-INFO +637 -0
- oniops-0.4.9b0/README.md +585 -0
- oniops-0.4.9b0/config.example.yaml +173 -0
- oniops-0.4.9b0/oniops/__init__.py +6 -0
- oniops-0.4.9b0/oniops/__main__.py +6 -0
- oniops-0.4.9b0/oniops/agent.py +567 -0
- oniops-0.4.9b0/oniops/aisec.py +597 -0
- oniops-0.4.9b0/oniops/artifact_scan.py +57 -0
- oniops-0.4.9b0/oniops/auth.py +293 -0
- oniops-0.4.9b0/oniops/bench_harness.py +265 -0
- oniops-0.4.9b0/oniops/bench_suites/crapi.yaml +85 -0
- oniops-0.4.9b0/oniops/bench_suites/juice_shop.yaml +65 -0
- oniops-0.4.9b0/oniops/bench_suites/vampi.yaml +52 -0
- oniops-0.4.9b0/oniops/benchmark.py +242 -0
- oniops-0.4.9b0/oniops/browser.py +243 -0
- oniops-0.4.9b0/oniops/cli.py +595 -0
- oniops-0.4.9b0/oniops/cloud_audit.py +332 -0
- oniops-0.4.9b0/oniops/config.py +421 -0
- oniops-0.4.9b0/oniops/cve.py +266 -0
- oniops-0.4.9b0/oniops/demo.py +235 -0
- oniops-0.4.9b0/oniops/demo_target.py +407 -0
- oniops-0.4.9b0/oniops/evaluation.py +143 -0
- oniops-0.4.9b0/oniops/findings.py +1080 -0
- oniops-0.4.9b0/oniops/graph.py +222 -0
- oniops-0.4.9b0/oniops/greybox.py +916 -0
- oniops-0.4.9b0/oniops/jobs.py +214 -0
- oniops-0.4.9b0/oniops/kali.py +197 -0
- oniops-0.4.9b0/oniops/local_runner.py +126 -0
- oniops-0.4.9b0/oniops/paths.py +43 -0
- oniops-0.4.9b0/oniops/pdf.py +166 -0
- oniops-0.4.9b0/oniops/playbooks.py +133 -0
- oniops-0.4.9b0/oniops/providers/__init__.py +96 -0
- oniops-0.4.9b0/oniops/providers/anthropic.py +46 -0
- oniops-0.4.9b0/oniops/providers/base.py +66 -0
- oniops-0.4.9b0/oniops/providers/gemini.py +52 -0
- oniops-0.4.9b0/oniops/providers/ollama.py +55 -0
- oniops-0.4.9b0/oniops/providers/openai_compat.py +61 -0
- oniops-0.4.9b0/oniops/ratelimit.py +214 -0
- oniops-0.4.9b0/oniops/scope.py +275 -0
- oniops-0.4.9b0/oniops/server.py +97 -0
- oniops-0.4.9b0/oniops/target_auth.py +348 -0
- oniops-0.4.9b0/oniops/targets.py +37 -0
- oniops-0.4.9b0/oniops/terms.py +98 -0
- oniops-0.4.9b0/oniops.egg-info/PKG-INFO +637 -0
- oniops-0.4.9b0/oniops.egg-info/SOURCES.txt +97 -0
- oniops-0.4.9b0/oniops.egg-info/dependency_links.txt +1 -0
- oniops-0.4.9b0/oniops.egg-info/entry_points.txt +2 -0
- oniops-0.4.9b0/oniops.egg-info/requires.txt +32 -0
- oniops-0.4.9b0/oniops.egg-info/top_level.txt +1 -0
- oniops-0.4.9b0/playbooks/ad_internal_enum.yaml +24 -0
- oniops-0.4.9b0/playbooks/ai_probes/agentic_mcp_pack.yaml +33 -0
- oniops-0.4.9b0/playbooks/api_access_control.yaml +20 -0
- oniops-0.4.9b0/playbooks/tls_crypto_audit.yaml +20 -0
- oniops-0.4.9b0/pyproject.toml +82 -0
- oniops-0.4.9b0/setup.cfg +4 -0
- oniops-0.4.9b0/setup.py +33 -0
- oniops-0.4.9b0/static/mdi/LICENSE +20 -0
- oniops-0.4.9b0/static/mdi/README.md +25 -0
- oniops-0.4.9b0/static/mdi/css/materialdesignicons.min.css +3 -0
- oniops-0.4.9b0/static/mdi/fonts/materialdesignicons-webfont.eot +0 -0
- oniops-0.4.9b0/static/mdi/fonts/materialdesignicons-webfont.ttf +0 -0
- oniops-0.4.9b0/static/mdi/fonts/materialdesignicons-webfont.woff +0 -0
- oniops-0.4.9b0/static/mdi/fonts/materialdesignicons-webfont.woff2 +0 -0
- oniops-0.4.9b0/templates/index.html +3115 -0
- oniops-0.4.9b0/templates/login.html +45 -0
- oniops-0.4.9b0/tests/test_agent.py +163 -0
- oniops-0.4.9b0/tests/test_aisec.py +38 -0
- oniops-0.4.9b0/tests/test_bench_harness.py +95 -0
- oniops-0.4.9b0/tests/test_bola_resolution.py +213 -0
- oniops-0.4.9b0/tests/test_browser_runtime.py +70 -0
- oniops-0.4.9b0/tests/test_cli.py +94 -0
- oniops-0.4.9b0/tests/test_competitive_workstreams.py +364 -0
- oniops-0.4.9b0/tests/test_config.py +129 -0
- oniops-0.4.9b0/tests/test_cve.py +104 -0
- oniops-0.4.9b0/tests/test_demo.py +96 -0
- oniops-0.4.9b0/tests/test_deploy_security.py +77 -0
- oniops-0.4.9b0/tests/test_e2e_demo_target.py +379 -0
- oniops-0.4.9b0/tests/test_findings.py +317 -0
- oniops-0.4.9b0/tests/test_greybox.py +258 -0
- oniops-0.4.9b0/tests/test_install_and_cli_ux.py +122 -0
- oniops-0.4.9b0/tests/test_manifest_signing.py +190 -0
- oniops-0.4.9b0/tests/test_paths_and_init.py +46 -0
- oniops-0.4.9b0/tests/test_pdf.py +30 -0
- oniops-0.4.9b0/tests/test_playbooks.py +46 -0
- oniops-0.4.9b0/tests/test_prompt_injection.py +129 -0
- oniops-0.4.9b0/tests/test_ratelimit.py +309 -0
- oniops-0.4.9b0/tests/test_retest_fixes.py +245 -0
- oniops-0.4.9b0/tests/test_scope.py +161 -0
- oniops-0.4.9b0/tests/test_security_fixes.py +120 -0
- oniops-0.4.9b0/tests/test_security_regression.py +192 -0
- oniops-0.4.9b0/tests/test_target_auth.py +350 -0
- oniops-0.4.9b0/tests/test_terms.py +58 -0
- oniops-0.4.9b0/tests/test_webui_routes.py +183 -0
- oniops-0.4.9b0/webui.py +1439 -0
|
@@ -0,0 +1,429 @@
|
|
|
1
|
+
# Changelog
|
|
2
|
+
|
|
3
|
+
All notable changes to OniOps are listed here. The format follows
|
|
4
|
+
[Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and versions follow
|
|
5
|
+
[Semantic Versioning](https://semver.org/). OniOps is pre-1.0 beta software, so
|
|
6
|
+
behaviour may still change between releases.
|
|
7
|
+
|
|
8
|
+
## [Unreleased]
|
|
9
|
+
|
|
10
|
+
## [0.4.9-beta] — 2026-11-12
|
|
11
|
+
|
|
12
|
+
### Added
|
|
13
|
+
- **`pip install oniops` / `pipx install oniops` now gives a working install**, including the web UI.
|
|
14
|
+
The wheel bundles `webui.py`, `templates/`, `static/`, `playbooks/` and `config.example.yaml`
|
|
15
|
+
under `oniops/_app/` (copied at build time by `setup.py`; the checkout layout is unchanged).
|
|
16
|
+
- **`oniops init`** creates `config.yaml`, `.env` (with a random `ONIOPS_SECRET_KEY`, mode 600) and
|
|
17
|
+
`data/` in the OniOps home folder. It never overwrites existing files and never prints the key.
|
|
18
|
+
- **`ONIOPS_HOME`** sets where an installed OniOps keeps `config.yaml`, `.env` and `data/`
|
|
19
|
+
(default `~/.oniops`). In a source checkout nothing moves: they stay in the checkout root.
|
|
20
|
+
- CI job that builds the wheel, installs it outside the checkout, and runs `init`, `demo` and the
|
|
21
|
+
web UI.
|
|
22
|
+
- Release workflow that publishes to PyPI with trusted publishing (no stored API token).
|
|
23
|
+
|
|
24
|
+
### Changed
|
|
25
|
+
- README: plainer description, a "Where OniOps fits" section that points to more mature tools, and a
|
|
26
|
+
"Known limitations" section. All links now use `github.com/ares-369/oniops`.
|
|
27
|
+
- Packaging metadata: SPDX license string, more keywords and classifiers, Changelog URL.
|
|
28
|
+
|
|
29
|
+
## [0.4.8-beta] — 2026-11-12
|
|
30
|
+
|
|
31
|
+
### Security
|
|
32
|
+
- **Reverse-proxy identity header could be forged.** The web UI runs behind
|
|
33
|
+
Werkzeug's `ProxyFix`, which rewrites `REMOTE_ADDR` from `X-Forwarded-For`.
|
|
34
|
+
In `auth.mode: proxy` the trusted-proxy check compared that rewritten value,
|
|
35
|
+
so a client able to reach the port directly could send
|
|
36
|
+
`X-Forwarded-For: <trusted proxy>` plus the identity header and authenticate
|
|
37
|
+
as any user. The check now validates the real socket peer
|
|
38
|
+
(`werkzeug.proxy_fix.orig`), not the forgeable header.
|
|
39
|
+
- **`python webui.py` ran the unhardened Flask dev server** and skipped the
|
|
40
|
+
startup security check. The entry point now routes through `oniops.server.main()`
|
|
41
|
+
(Waitress + the exposure/auth checks), the same as `python -m oniops`.
|
|
42
|
+
|
|
43
|
+
### Added
|
|
44
|
+
- **Authenticated target sessions with refresh.** A `target_auth` config block
|
|
45
|
+
logs in to a target per role (`primary`/`low_priv`/`peer`): `json_login`
|
|
46
|
+
(token APIs such as VAmPI and Juice Shop) or `form_login` (form logins such as
|
|
47
|
+
DVWA). A role's session is re-minted and the request retried once on a 401/403,
|
|
48
|
+
so short-lived tokens (for example VAmPI's ~60s JWTs) no longer collapse the
|
|
49
|
+
access-control differential into anonymous requests. Credentials are referenced
|
|
50
|
+
only as `${ENV_VAR}` and never reach findings, logs or reports. See
|
|
51
|
+
`docs/TARGET_AUTH.md`.
|
|
52
|
+
- **One-command install** (`scripts/install.sh`): creates a virtualenv, installs
|
|
53
|
+
OniOps, seeds `config.yaml`/`.env` from the examples without overwriting them,
|
|
54
|
+
and generates a random `ONIOPS_SECRET_KEY` when missing. Idempotent.
|
|
55
|
+
- Public-app benchmark harness: `oniops benchmark --suite <crapi|juice_shop|vampi> --target <ip>`
|
|
56
|
+
scores an assessment's findings against labeled known bugs. Only verified findings
|
|
57
|
+
count, matching is one-to-one, and verified findings outside the labels are listed for triage, so
|
|
58
|
+
precision is reported as a range until they are classified with `--triage`. See `docs/BENCHMARKS.md`.
|
|
59
|
+
|
|
60
|
+
### Fixed
|
|
61
|
+
- The web UI now honours `ONIOPS_DB_PATH`, so it reads and writes the same ledger
|
|
62
|
+
as the CLI instead of always using `<checkout>/data/oniops.sqlite`.
|
|
63
|
+
- Browser discovery redacts bare `jwt`/`bearer`/`credential` query values (not
|
|
64
|
+
only `*token*`-style keys) and pins the start host to its scope-validated IP at
|
|
65
|
+
launch, closing the DNS re-resolution window between the scope check and
|
|
66
|
+
navigation for that host.
|
|
67
|
+
- The labeled-benchmark scorer only lets a VERIFIED finding satisfy a label; an
|
|
68
|
+
unverified match is no longer consumed, so it stays visible for triage and
|
|
69
|
+
false-positive accounting.
|
|
70
|
+
- AWS region validation accepts GovCloud, China and ISO partition names
|
|
71
|
+
(`us-gov-east-1`, `cn-north-1`, `us-iso-east-1`), not only commercial regions.
|
|
72
|
+
|
|
73
|
+
### Changed
|
|
74
|
+
- **Easier, safer install and deploy.** The Docker image now ships `playbooks/`
|
|
75
|
+
and `curl`; the worker image ships `katana` and a wordlist; the `.dockerignore`
|
|
76
|
+
no longer excludes files the controller image needs; Docker Compose requires a
|
|
77
|
+
login (the unauthenticated-network opt-in is a commented, clearly labelled
|
|
78
|
+
block). The systemd unit runs as a dedicated non-root user from `/opt/oniops`, and
|
|
79
|
+
the README and `docs/INSTALL.md` document that path. The Proxmox LXC script
|
|
80
|
+
points at the real repository. `known_hosts` defaults to the writable `./data`
|
|
81
|
+
directory so trust-on-first-use host keys persist.
|
|
82
|
+
- CLI hardening: `oniops assess` rejects an unknown `--profile` instead of silently
|
|
83
|
+
starting the autonomous LLM loop; `assess`, `diff`, `backup`, `restore`, `doctor`
|
|
84
|
+
and others print a clean error and a nonzero exit instead of a traceback;
|
|
85
|
+
`oniops doctor --check-runner` fails when the runner is unreachable; `oniops serve` is
|
|
86
|
+
listed in `--help`. The README gains a Quick start, a naming-and-layout note and
|
|
87
|
+
a configuration/environment table.
|
|
88
|
+
|
|
89
|
+
## [0.4.7-beta] — 2026-11-12
|
|
90
|
+
|
|
91
|
+
### Added
|
|
92
|
+
- A labeled, loopback-only live fixture benchmark: `oniops benchmark --demo-evaluation`. It reports
|
|
93
|
+
precision, recall, F1, negative checks, one-to-one finding matching and its explicit fixture-only
|
|
94
|
+
limitations. Unverified detections do not count as true positives; duplicate alerts count as FPs.
|
|
95
|
+
- Optional Playwright browser discovery (`oniops crawl`) with bounded page/time budgets, in-scope
|
|
96
|
+
request routing, read-only navigation and start-origin-only credential forwarding.
|
|
97
|
+
- Browser discovery now reports observed XHR/fetch status and content type plus value-free form
|
|
98
|
+
metadata, and flags credential-like fields on GET or cleartext forms as observations.
|
|
99
|
+
- AWS password-policy findings now use an explicitly selected baseline. The AWS CIS-style profile
|
|
100
|
+
checks composition and rotation; the NIST 800-63B-4 profile checks its single-factor length rule
|
|
101
|
+
without requiring composition or periodic rotation.
|
|
102
|
+
- Disposable Docker worker mode for scanner commands with a non-root user, read-only filesystem,
|
|
103
|
+
dropped Linux capabilities, resource limits and command timeouts; sample image in `Dockerfile.worker`.
|
|
104
|
+
- Docker workers now apply a fail-closed egress firewall using effective scope CIDRs, drop bootstrap
|
|
105
|
+
capabilities before scanner execution, and reject built-in Docker network modes. They require a
|
|
106
|
+
user-defined bridge so DNS stays on Docker's embedded resolver; IPv4-only kernels are handled
|
|
107
|
+
explicitly while IPv6 scopes fail closed if IPv6 is unavailable. The bootstrap receives only the
|
|
108
|
+
temporary network, UID/GID, and capability-management permissions needed before dropping them all.
|
|
109
|
+
- CI builds the worker image, exercises the firewall against allowed and denied container targets,
|
|
110
|
+
and runs Nmap/Nuclei as a non-root user with a read-only filesystem; `.dockerignore` prevents
|
|
111
|
+
unrelated workspace files from entering its build context.
|
|
112
|
+
- Offline Trivy scan of images already loaded on the attack host (`oniops container-scan`) and optional
|
|
113
|
+
read-only AWS account/IAM, security-group, EKS endpoint and S3 policy/ACL/encryption checks
|
|
114
|
+
(`oniops cloud-audit aws`).
|
|
115
|
+
- Semantic versions, pack metadata, nested discovery and SHA-256 source hashes for network playbooks
|
|
116
|
+
and AI probe packs. See `docs/SECURITY_PACKS.md`.
|
|
117
|
+
- OpenAPI BOPLA analysis now follows nested local references, composition and arrays, and reads
|
|
118
|
+
OpenAPI 2 body/form parameters plus OpenAPI 3 vendor JSON schemas without fetching external refs.
|
|
119
|
+
- Playbook tool requirements now include every executed binary. `sqlmap` and `hydra` packs require
|
|
120
|
+
`safety: intrusive`, which remains disabled at assessment endpoints unless explicitly enabled in
|
|
121
|
+
scope configuration.
|
|
122
|
+
- Scope enforcement now checks the full IPv4 CIDR and address range in nmap target arguments,
|
|
123
|
+
including explicit exclusions, rather than checking only the first address.
|
|
124
|
+
- Network playbook steps are restricted to supported scanner commands and must include the assessed
|
|
125
|
+
`{target}`, preventing a custom YAML pack from invoking arbitrary commands on the attack host.
|
|
126
|
+
|
|
127
|
+
### Fixed
|
|
128
|
+
- A low-privilege user's own object read no longer creates a second verified BOLA finding. Object
|
|
129
|
+
ownership must be established; a peer-owned object read remains the verified horizontal BOLA proof.
|
|
130
|
+
- Agent finding replay now rejects non-origin-relative paths and malformed indicators, caps response
|
|
131
|
+
size, disables redirects and only verifies successful command executions. Ledger write failures are
|
|
132
|
+
surfaced instead of silently discarded.
|
|
133
|
+
- Agent-proposed findings and zero-token retests now require a supported category-specific proof rule
|
|
134
|
+
and a matching claim title. A model-supplied expected string alone remains UNCONFIRMED; 5xx retests
|
|
135
|
+
are also inconclusive rather than being called fixed.
|
|
136
|
+
- AWS security-group rules without TCP/UDP ports (such as ICMP) are no longer classified as exposing
|
|
137
|
+
all ports; all-protocol and administrative-port rules retain their higher severity.
|
|
138
|
+
|
|
139
|
+
## [0.4.6-beta] — 2026-11-11
|
|
140
|
+
|
|
141
|
+
### Fixed
|
|
142
|
+
- **Horizontal (cross-user) BOLA on parameterised object routes was silently
|
|
143
|
+
missed.** The grey-box OpenAPI probe filled every path parameter with the
|
|
144
|
+
literal `1`, so a route like `/users/v1/{username}` became `/users/v1/1` — a
|
|
145
|
+
non-existent object that returns 404 — and the cross-user check (which needs a
|
|
146
|
+
real object) never ran. The probe now resolves a real identifier for a
|
|
147
|
+
parameterised object route by mining its sibling collection endpoint
|
|
148
|
+
(`/users/v1`), per identity, and falls back to the old placeholder only when
|
|
149
|
+
nothing can be mined. For the horizontal cross-user check it selects an object
|
|
150
|
+
the peer identity can see but the low-privilege identity does not own, then has
|
|
151
|
+
the low-privilege identity request it; a 200 with the peer's object content is
|
|
152
|
+
reported VERIFIED/HIGH, the replay stored as that identity (credential masked
|
|
153
|
+
on display). When ownership cannot be established — for example an API that
|
|
154
|
+
returns the full collection to every caller — the result is reported
|
|
155
|
+
UNCONFIRMED for manual review rather than as a false positive. The zero-token
|
|
156
|
+
retest treats such a finding as FIXED only when the peer-owned object is now
|
|
157
|
+
denied (HTTP 403 or 404).
|
|
158
|
+
|
|
159
|
+
## [0.4.5-beta] — 2026-11-11
|
|
160
|
+
|
|
161
|
+
### Security
|
|
162
|
+
- **Forgeable signatures removed.** Earlier releases fell back to a built-in
|
|
163
|
+
constant key (`oniops-default-manifest-key` / `oniops-webhook-key`) when no signing
|
|
164
|
+
key was set, so anyone with the source could forge an assessment manifest or
|
|
165
|
+
webhook signature. There is no fallback key any more. With no operator key
|
|
166
|
+
configured, a manifest still carries its SHA-256 integrity hash but is marked
|
|
167
|
+
`signed: false` with an `unsigned_reason`, and webhook alerts are sent with no
|
|
168
|
+
signature header rather than a worthless one. `verify_assessment_manifest`
|
|
169
|
+
now returns false for unsigned manifests, empty keys and the old constants;
|
|
170
|
+
`manifest_verification_status` reports the reason. The web UI also no longer
|
|
171
|
+
signs with Flask's per-process session key, which could never be verified
|
|
172
|
+
after a restart. Set `ONIOPS_SECRET_KEY` (or `auth.secret_key`) to sign; `oniops
|
|
173
|
+
doctor` now warns when no persistent key is set.
|
|
174
|
+
- **Retest could report a still-exploitable finding as FIXED.** Access-control
|
|
175
|
+
findings (BOLA/BFLA and cross-user horizontal BOLA) are proven with a
|
|
176
|
+
low-privilege or peer identity, but the zero-token retest replayed the stored
|
|
177
|
+
request anonymously, got a 401, and wrongly concluded the issue was fixed. The
|
|
178
|
+
retest now replays as the identity that proved the finding, and reports FIXED
|
|
179
|
+
only on positive evidence that access is now denied (HTTP 403) or that the
|
|
180
|
+
proof signature is gone. A credential that is simply rejected (401) yields
|
|
181
|
+
UNCONFIRMED, never FIXED. Findings stored by 0.4.1–0.4.2 without their
|
|
182
|
+
credential are not replayed at all; they ask for a fresh assessment. Replayed
|
|
183
|
+
credentials are stored raw (a retest needs them) but masked in every display,
|
|
184
|
+
export and webhook payload. SQLi/XSS/LFI/SSRF/RCE/GraphQL retests now re-run
|
|
185
|
+
the proof check instead of trusting a clean exit code, and `cve`/`exploitdb`
|
|
186
|
+
retests report UNCONFIRMED rather than VERIFIED on any output.
|
|
187
|
+
- **Scan rate limit is now enforced.** `scope.rate_limit_per_min` was shown in
|
|
188
|
+
the settings screen but never applied. It now paces every command or request
|
|
189
|
+
sent to a target, per target, at both the attack-host runner and the AI-probe
|
|
190
|
+
HTTP path. The limit bounds launched commands/requests, not packets: one
|
|
191
|
+
`nmap` or `nikto` run still sends many. On an HTTP 429 or 503 the AI-probe
|
|
192
|
+
path backs off using `Retry-After` (capped at 60 seconds) or jittered
|
|
193
|
+
exponential backoff, then records the probe as throttled — never as a pass —
|
|
194
|
+
and the attack-host path puts a throttling target on a short cool-down.
|
|
195
|
+
|
|
196
|
+
### Added
|
|
197
|
+
- **`oniops demo` — a zero-setup first run.** `oniops demo` needs no config, no attack
|
|
198
|
+
host, no SSH keys and no LLM. It starts a small, deliberately flawed practice
|
|
199
|
+
target bound to loopback inside the process, runs the real probes and
|
|
200
|
+
validators against it through a loopback-only local runner, and prints what it
|
|
201
|
+
found with proof snippets, the fix-first score and a zero-token retest, then
|
|
202
|
+
stops the target and deletes its temporary ledger. Everything is labelled
|
|
203
|
+
DEMO and nothing is written to a real ledger or recorded as terms acceptance.
|
|
204
|
+
Inspired by how projects like OWASP Juice Shop lower the barrier to a first
|
|
205
|
+
run.
|
|
206
|
+
- **GraphQL introspection check in Web App PT.** The existing GraphQL
|
|
207
|
+
introspection probe is now part of a `web_app_pt` assessment, and its finding
|
|
208
|
+
can be retested.
|
|
209
|
+
|
|
210
|
+
### Fixed
|
|
211
|
+
- The AI security posture score no longer counts errored or throttled probes as
|
|
212
|
+
passes; a run with no real answers is rated Inconclusive instead of Strong.
|
|
213
|
+
|
|
214
|
+
### Changed
|
|
215
|
+
- **Project renamed to OniOps.** The product and its documentation, web UI,
|
|
216
|
+
generated reports and CLI help now use the name *OniOps*. The Python package,
|
|
217
|
+
the `oniops` command, install paths and the systemd unit are unchanged, so
|
|
218
|
+
existing deployments keep working. The repository moved to
|
|
219
|
+
`github.com/ares-369/oni-ops` (the old URL redirects).
|
|
220
|
+
|
|
221
|
+
## [0.4.4-beta] — 2026-11-10
|
|
222
|
+
|
|
223
|
+
### Security
|
|
224
|
+
- **Reverse-proxy login could be forged.** With `auth.mode: proxy` and an empty
|
|
225
|
+
`proxy_trusted_ips` (the example config's default), any client could send the
|
|
226
|
+
identity header and log in as any user. Proxy mode now fails closed: OniOps
|
|
227
|
+
refuses to start without a trusted-proxy list, and the request handler also
|
|
228
|
+
rejects the header when no list is set.
|
|
229
|
+
- **Secure defaults.** The web UI now listens on `127.0.0.1` by default, and OniOps
|
|
230
|
+
**refuses to start** when exposed on a network address without a login,
|
|
231
|
+
unless you explicitly set `oniops.allow_unauthenticated_network: true` (or
|
|
232
|
+
`ONIOPS_ALLOW_UNAUTHENTICATED_NETWORK=1`). Docker Compose now publishes the port
|
|
233
|
+
on `127.0.0.1` only. New `ONIOPS_BIND_HOST` environment override.
|
|
234
|
+
- **Prompt-injection filter strengthened.** Tool output is now Unicode-normalised
|
|
235
|
+
and stripped of invisible characters before scanning, base64-encoded
|
|
236
|
+
instructions are decoded and checked, and many more phrasings and fake role
|
|
237
|
+
tags are caught (17 of 17 adversarial cases, up from 6). A new test suite also
|
|
238
|
+
verifies that a model which fully obeys an injection still cannot scan out of
|
|
239
|
+
scope or run arbitrary or destructive commands.
|
|
240
|
+
|
|
241
|
+
### Upgrade notes
|
|
242
|
+
- If you reach OniOps from other machines, make sure `oniops.bind_host` is set
|
|
243
|
+
(e.g. `"0.0.0.0"`) **and** a login is enabled (`auth.mode`), or OniOps will not
|
|
244
|
+
start. If you use `auth.mode: proxy`, set `auth.proxy_trusted_ips` to your
|
|
245
|
+
reverse proxy's IP.
|
|
246
|
+
|
|
247
|
+
## [0.4.3-beta] — 2026-11-10
|
|
248
|
+
|
|
249
|
+
### Fixed
|
|
250
|
+
- **Retest could mark a still-present vulnerability as FIXED.** Since
|
|
251
|
+
0.4.1-beta, credentials in replay commands were masked *in the database*, so
|
|
252
|
+
a retest of an authenticated finding sent `[REDACTED-TOKEN]`, got a 401, and
|
|
253
|
+
reported the issue as fixed. Replay commands are stored intact again and
|
|
254
|
+
secrets are masked wherever a finding leaves the server (UI, API, CLI, retest
|
|
255
|
+
responses). Findings saved by 0.4.1-0.4.2 with a masked credential now refuse
|
|
256
|
+
to retest, with a clear message, instead of guessing.
|
|
257
|
+
- A 401 on an *authenticated* retest now reports UNCONFIRMED ("credential
|
|
258
|
+
rejected, it may have expired") instead of FIXED. Unauthenticated findings
|
|
259
|
+
that start returning 401/403/404 are still reported as FIXED.
|
|
260
|
+
- If a retest cannot run at all (attack host unreachable, timeout, scope
|
|
261
|
+
refusal), the finding's status is left unchanged instead of becoming FIXED.
|
|
262
|
+
- **Access control:** the full database backup (`/api/backup/download`) and the
|
|
263
|
+
attack-host SSH check (`/api/doctor?runner=1`) are now admin-only. Previously
|
|
264
|
+
the read-only `viewer` role could download the whole database.
|
|
265
|
+
|
|
266
|
+
### Changed
|
|
267
|
+
- The "benchmark" from 0.4.1-beta is renamed to **validator self-test**
|
|
268
|
+
(`oniops selftest`, `GET /api/selftest`; the old names still work). It checks
|
|
269
|
+
OniOps's own validators against built-in example inputs and reports pass/fail
|
|
270
|
+
per check. It no longer reports precision / recall / F1, because those
|
|
271
|
+
numbers described the examples, not detection accuracy on real targets.
|
|
272
|
+
|
|
273
|
+
## [0.4.2-beta] — 2026-11-09
|
|
274
|
+
|
|
275
|
+
### Fixed
|
|
276
|
+
- Workbench Recent Jobs bar was always empty (read `params` instead of job `meta`); it now also refreshes when the Workbench opens.
|
|
277
|
+
- Replay commands could expose bearer tokens/cookies in the Finding Detail Drawer; repro commands are now secret-redacted on storage and on display. *(Correction: masking in storage broke authenticated retests; fixed in 0.4.3-beta.)*
|
|
278
|
+
- Zero-token retest now treats 401/403/404 as FIXED for BOLA/BFLA findings. *(Correction: for authenticated findings a 401 now reports UNCONFIRMED; see 0.4.3-beta.)*
|
|
279
|
+
- Clicking a findings row now opens the Finding Detail Drawer reliably; long SHA-256 hashes wrap on mobile.
|
|
280
|
+
|
|
281
|
+
## [0.4.1-beta] — 2026-11-09
|
|
282
|
+
|
|
283
|
+
### Added
|
|
284
|
+
- **Finding Detail Drawer & Fix-First Priority Score**: Clicking any finding in
|
|
285
|
+
the ledger opens a slide-over drawer showing the full captured evidence,
|
|
286
|
+
SHA-256 provenance hash, deterministic replay command (with one-click copy and
|
|
287
|
+
zero-token retest), CWE / OWASP / ATT&CK tags, step-by-step engineering
|
|
288
|
+
remediation guidance (`get_remediation_guide`), and a `0-100` Fix-First
|
|
289
|
+
Priority Score (`compute_priority_score`). Added `GET /api/findings/<id>`.
|
|
290
|
+
- **Validator self-test (`oniops benchmark`)**: 17 built-in checks
|
|
291
|
+
(`oniops/benchmark.py`, `python -m oniops benchmark`, `GET /api/benchmark`) for the
|
|
292
|
+
Web/API proof validators, BOLA/BOPLA analyzers, SAST sink detection, and
|
|
293
|
+
prompt-injection quarantine. *(Correction: this was originally described as
|
|
294
|
+
measuring recall, false-positive rate, precision and F1. It only checks OniOps's
|
|
295
|
+
validators against built-in examples and does not measure detection accuracy
|
|
296
|
+
on real targets. Renamed to `oniops selftest` in 0.4.3-beta.)*
|
|
297
|
+
- **Authenticated Assessment Enhancements**: `whatweb` and PoC service
|
|
298
|
+
validation now honor the grey-box `auth_header` when testing behind login
|
|
299
|
+
gates, and agent-reported findings persist secret-redacted `-H` replay
|
|
300
|
+
commands and vulnerability categories.
|
|
301
|
+
- **Full Backend-to-Frontend Parity**: Wired Assessment Baseline Drift Diff
|
|
302
|
+
(`/api/assessments/<id>/diff`), AI YAML Probe Packs & Crescendo toggles
|
|
303
|
+
(`/api/aisec/probes`), White-Box SARIF v2.1.0 download & Semgrep/Gitleaks
|
|
304
|
+
toggle (`/api/whitebox/scan`), Settings Self-Diagnostics (`GET /api/doctor`),
|
|
305
|
+
in-browser Verification Benchmark runner, online SQLite `.sqlite` backup
|
|
306
|
+
download (`GET /api/backup/download`), Horizontal BOLA Peer Header
|
|
307
|
+
(`peer_auth_header`), and Background Job History / Re-attach (`/api/jobs`)
|
|
308
|
+
directly into the web UI.
|
|
309
|
+
|
|
310
|
+
## [0.4.0-beta] — 2026-11-09
|
|
311
|
+
|
|
312
|
+
### Added
|
|
313
|
+
- **Confidence column** on findings (Certain / Firm / Tentative, inspired by
|
|
314
|
+
Burp Suite), with filter chips and sorting by severity then confidence.
|
|
315
|
+
- **Step-by-step job timeline** in the Workbench (inspired by GitHub Actions):
|
|
316
|
+
one row per stage with live status, duration and an expandable log.
|
|
317
|
+
Progress events are now tagged with the job that produced them.
|
|
318
|
+
- **"Get OniOps ready" setup checklist** on the dashboard for new installs
|
|
319
|
+
(inspired by Grafana and Tailscale onboarding): terms, attack host, AI model,
|
|
320
|
+
scope, discovery, first assessment. Hides itself when complete.
|
|
321
|
+
- **Helpful empty states** (inspired by Stripe and Notion) for assessments,
|
|
322
|
+
reports, findings, targets, the attack graph and CVE intel, each with a
|
|
323
|
+
next-step button.
|
|
324
|
+
|
|
325
|
+
### Changed
|
|
326
|
+
- Progress messages say "attack host" instead of "Kali".
|
|
327
|
+
|
|
328
|
+
## [0.3.3-beta] — 2026-11-09
|
|
329
|
+
|
|
330
|
+
### Added
|
|
331
|
+
- `DISCLAIMER.md` responsible-use statement, also summarised in `NOTICE` and the
|
|
332
|
+
README: OniOps is for authorized testing, is provided as-is, and the author is
|
|
333
|
+
not responsible for misuse or for modified versions made by others.
|
|
334
|
+
- First-run "Authorized use only" dialog in the web UI. Each user must confirm
|
|
335
|
+
authorized use and accept the terms before any scan, agent, AI test or
|
|
336
|
+
retest can start; the server enforces this and records who accepted which
|
|
337
|
+
version and when (shown in Settings -> About).
|
|
338
|
+
|
|
339
|
+
### Changed
|
|
340
|
+
- CONTRIBUTING and README rewritten to be friendlier for new contributors; the
|
|
341
|
+
README now credits the tools and projects OniOps builds on.
|
|
342
|
+
|
|
343
|
+
### Fixed
|
|
344
|
+
- Page load no longer waits ~6s on SSH when the attack host is down: host and
|
|
345
|
+
LLM health are checked in the background and shown as Checking / Online /
|
|
346
|
+
Offline (load time 7.2s -> 1.1s).
|
|
347
|
+
- The sidebar card and AI operator greeting show the real host state instead
|
|
348
|
+
of always saying "connected".
|
|
349
|
+
- Failed, stopped or timed-out Workbench runs no longer leave "Running..." on
|
|
350
|
+
screen; an empty target is caught before anything is sent.
|
|
351
|
+
- Target pickers have a "Select a target" option and an empty state, and keep
|
|
352
|
+
the user's choice across refreshes.
|
|
353
|
+
- An unknown `scope.mode` falls back to `active` with a warning, so Settings
|
|
354
|
+
always shows the mode actually in effect.
|
|
355
|
+
- Phone: host/LLM status dots in the header and 44px touch targets.
|
|
356
|
+
- Accessibility labels for icon buttons and form fields; generic "attack host"
|
|
357
|
+
wording instead of lab-specific names.
|
|
358
|
+
- The CLI version test now follows the package version, so release bumps no
|
|
359
|
+
longer break CI.
|
|
360
|
+
|
|
361
|
+
## [0.3.2-beta] — 2026-11-09
|
|
362
|
+
|
|
363
|
+
### Fixed
|
|
364
|
+
- Finding validation no longer marks a finding VERIFIED just because a target
|
|
365
|
+
returned output or a bare HTTP 2xx; a real indicator or a vulnerability-class
|
|
366
|
+
proof pattern is now required (service exposure excepted).
|
|
367
|
+
- BOLA checks: an empty 200 response is only treated as confirmable when the
|
|
368
|
+
server declares an API content type; a 401/403 -> 200 privilege difference
|
|
369
|
+
is reported as a probable (unconfirmed) finding instead of being dropped.
|
|
370
|
+
- The agent's `report_finding` tool now captures the response body, so
|
|
371
|
+
body-based indicators can match.
|
|
372
|
+
|
|
373
|
+
### Added
|
|
374
|
+
- Gitleaks allowlist for the fake credentials used as test fixtures.
|
|
375
|
+
|
|
376
|
+
## [0.3.1-beta] — 2026-11-09
|
|
377
|
+
|
|
378
|
+
### Added
|
|
379
|
+
- `oniops doctor` self-diagnostics, online SQLite backup/restore, CLI `assess` and
|
|
380
|
+
`retest`, per-category confidence calibration, threat-model docs.
|
|
381
|
+
- Vulnerability-specific proof validators, horizontal BOLA / BOPLA / GraphQL
|
|
382
|
+
checks, identity-aware attack graph, OWASP / ATT&CK coverage mapping, a
|
|
383
|
+
verified-only CI gate and job de-duplication.
|
|
384
|
+
|
|
385
|
+
### Security
|
|
386
|
+
- Stronger DNS and command scope guards, login rate limiting, CSRF origin
|
|
387
|
+
checks, PBKDF2 (600k iterations), 3-tier RBAC, SQLite WAL, signed execution
|
|
388
|
+
manifests, and adversarial regression tests.
|
|
389
|
+
|
|
390
|
+
## [0.3.0-beta] — 2026-11-09
|
|
391
|
+
|
|
392
|
+
### Added
|
|
393
|
+
- CLI and CI/CD security gate with SARIF output, EPSS exploit-probability
|
|
394
|
+
intel, SHA-256 evidence provenance, and a Semgrep / Gitleaks SAST adapter.
|
|
395
|
+
|
|
396
|
+
## [0.2.0-beta] — 2026-11-09
|
|
397
|
+
|
|
398
|
+
### Added
|
|
399
|
+
- Evidence ledger with zero-token retest, grey-box and white-box analysis,
|
|
400
|
+
agent output quarantine and graph memory, AI red-team converters and
|
|
401
|
+
multi-turn probes, YAML playbooks.
|
|
402
|
+
- Independent finding validator, BOLA / BFLA and JS route discovery,
|
|
403
|
+
attack-path blast radius, drift diff and batch retest, YAML AI probe packs.
|
|
404
|
+
- Real browser screenshots in the README and end-to-end route tests.
|
|
405
|
+
|
|
406
|
+
## [0.1.0] — 2026-11-09
|
|
407
|
+
|
|
408
|
+
### Added
|
|
409
|
+
- Config-driven core, multi-provider LLM layer (Ollama, Anthropic, Gemini,
|
|
410
|
+
OpenAI, OpenAI-compatible) and cross-platform packaging.
|
|
411
|
+
- Background job engine, web-app pentest track, attack-surface graph and
|
|
412
|
+
autonomous tool-calling agent.
|
|
413
|
+
- Pluggable authentication (none / basic / local / OIDC / proxy), multi
|
|
414
|
+
attack-host support and an editable Settings page.
|
|
415
|
+
- AI / LLM red-team and GRC module, PoC service validation, report export,
|
|
416
|
+
offline CVE intelligence, PDF export, tests and CI.
|
|
417
|
+
|
|
418
|
+
[Unreleased]: https://github.com/ares-369/oniops/compare/v0.4.9-beta...HEAD
|
|
419
|
+
[0.4.9-beta]: https://github.com/ares-369/oniops/releases/tag/v0.4.9-beta
|
|
420
|
+
[0.4.8-beta]: https://github.com/ares-369/oniops/releases/tag/v0.4.8-beta
|
|
421
|
+
[0.4.7-beta]: https://github.com/ares-369/oniops/releases/tag/v0.4.7-beta
|
|
422
|
+
[0.4.6-beta]: https://github.com/ares-369/oniops/releases/tag/v0.4.6-beta
|
|
423
|
+
[0.4.4-beta]: https://github.com/ares-369/oniops/releases/tag/v0.4.4-beta
|
|
424
|
+
[0.4.3-beta]: https://github.com/ares-369/oniops/releases/tag/v0.4.3-beta
|
|
425
|
+
[0.4.2-beta]: https://github.com/ares-369/oniops/releases/tag/v0.4.2-beta
|
|
426
|
+
[0.4.1-beta]: https://github.com/ares-369/oniops/releases/tag/v0.4.1-beta
|
|
427
|
+
[0.4.0-beta]: https://github.com/ares-369/oniops/releases/tag/v0.4.0-beta
|
|
428
|
+
[0.3.3-beta]: https://github.com/ares-369/oniops/releases/tag/v0.3.3-beta
|
|
429
|
+
[0.3.2-beta]: https://github.com/ares-369/oniops/releases/tag/v0.3.2-beta
|
|
@@ -0,0 +1,49 @@
|
|
|
1
|
+
# Responsible Use and Disclaimer
|
|
2
|
+
|
|
3
|
+
OniOps is a security testing tool. I built it to help people learn offensive
|
|
4
|
+
security, test their own labs, and run assessments they are authorized to
|
|
5
|
+
perform. Please read this before using it.
|
|
6
|
+
|
|
7
|
+
## Use it legally and with permission
|
|
8
|
+
|
|
9
|
+
Only run OniOps against systems that **you own**, or that you have **explicit
|
|
10
|
+
written permission** to test (for example, a signed scope or rules of
|
|
11
|
+
engagement from the system owner). Scanning or attacking systems without
|
|
12
|
+
permission is illegal in most countries, even if no damage is done.
|
|
13
|
+
|
|
14
|
+
If you are not sure whether you are allowed to test something, do not test it.
|
|
15
|
+
|
|
16
|
+
## You are responsible for how you use it
|
|
17
|
+
|
|
18
|
+
OniOps is provided **"as is", without warranty of any kind**. Under sections 7
|
|
19
|
+
and 8 of the [Apache-2.0 license](LICENSE), the author is not liable for any
|
|
20
|
+
damages arising from its use.
|
|
21
|
+
|
|
22
|
+
By using, copying, modifying, or distributing OniOps, you agree that:
|
|
23
|
+
|
|
24
|
+
- **You alone are responsible** for your actions with OniOps, for obtaining
|
|
25
|
+
proper authorization, and for following all laws and regulations that apply
|
|
26
|
+
to you.
|
|
27
|
+
- **The author does not condone, and is not responsible or liable for, any
|
|
28
|
+
misuse of OniOps.** This includes unauthorized access, attacks against any
|
|
29
|
+
person, company, or organization, disruption of services, loss or damage of
|
|
30
|
+
data, and any other harm or legal consequence resulting from its use.
|
|
31
|
+
- **The author is not responsible for modified versions, forks, or
|
|
32
|
+
redistributions** made by anyone else — including versions that remove,
|
|
33
|
+
weaken, or bypass OniOps's safety controls. Whoever changes or redistributes
|
|
34
|
+
OniOps is responsible for those changes and for how they are used. The
|
|
35
|
+
[Apache-2.0 license](LICENSE) also requires modified files to carry a notice
|
|
36
|
+
that they were changed (section 4(b)), and the [`NOTICE`](NOTICE) file,
|
|
37
|
+
which includes this disclaimer, must be kept with every copy (section 4(d)).
|
|
38
|
+
|
|
39
|
+
## Safety features are aids, not guarantees
|
|
40
|
+
|
|
41
|
+
OniOps ships with a scope allow-list, a non-destructive guard, and authentication
|
|
42
|
+
options that are on by default. They help prevent mistakes, but they are not a
|
|
43
|
+
guarantee that nothing can go wrong, and they are not a substitute for having
|
|
44
|
+
permission.
|
|
45
|
+
|
|
46
|
+
## Reporting problems
|
|
47
|
+
|
|
48
|
+
If you find a security issue in OniOps itself, please report it privately — see
|
|
49
|
+
[`SECURITY.md`](SECURITY.md).
|