Skip to content

armgit / AiSOC

Public Imported from GitHub
0

Open-source AI Security Operations Center: alert fusion, LLM-agent triage, MITRE ATT&CK investigation, and a replayable decision ledger for every agent step. Self-hostable, runs with no API keys, MIT licensed. Ships an MCP server for Claude, Cursor and Continue.

chore(release): v12.3.2 (#1051)

Beenu Arora5e882dd58e2d
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 5d5a1ad51..2f6b1f676 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -7,6 +7,24 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
## [Unreleased]
+## [12.3.2] - 2026-09-29
+
+### Security
+
+- **Eleven routes carried a permission FastAPI never called.** Closing GHSA-wj5c-88hg-5926 in v12.3.1 left the obvious question: where else does a write surface authenticate and not authorize? Sweeping the sibling modules found it eleven more times, in a shape that is harder to see because the permission is present and correctly spelled — `current_user: Annotated[Any, require_permission("users:write")]`, with no `Depends()`. FastAPI honours only `Annotated` metadata that is a `Depends` or a `FieldInfo` and silently drops everything else, so the permission was never checked and `current_user` degraded into a required query parameter. `POST /api-keys`, `PATCH` and `DELETE /api-keys/{id}`, `PUT /branding`, `POST` and `DELETE /branding/assets/*`, `POST /scim-tokens`, `POST /scim-tokens/{id}/rotate`, `DELETE /scim-tokens/{id}`, `GET /usage/reconciliation` and `GET /usage/export.csv` answered 422 to a `viewer` token rather than 403, and 500 if the caller supplied the principal the URL was asking for — so these routes were both unauthorized and unusable, minting API keys and rotating SCIM tokens among them. All eleven now use the idiom the rest of the service uses and refuse a `viewer` with 403.
+
+- **The published API contract had been saying so all along.** Because FastAPI could not see the dependency it documented `current_user` as a required query parameter on all eleven routes, and that was in the committed `docs/openapi.yaml` — the contract integrators build against was asking callers to supply their own principal in the URL. The regenerated spec drops exactly eleven of them with the 422 responses that existed only to reject a request that omitted it. `scripts/openapi_diff.py` reports no breaking change: removing a required query parameter relaxes the contract, and no client could have been sending one usefully.
+
+### Changed
+
+- **`scripts/check_route_authz.py` no longer credits a permission it cannot see.** The gate added in v12.3.1 counted eight of the nine broken write routes among those that authorize, because it matched the `require_permission` call and not its wiring — the same one-directional blindness that let `check_route_auth.py` report OK on `remediation.py`, one level up. A `require_permission` left in `Annotated` metadata is now reported with **no ceiling and no exemptions**, since there is no correct reason to write it, and it no longer counts as authorization. The alias form is covered too: `WriteUser = Annotated[CurrentUser, Depends(require_permission(_WRITE))]` is one line gating three routes, so unwrapping it disarms all three at once, and the self-test now performs that exact edit and asserts it is reported once *and* that all three `remediation.py` write routes stop being credited.
+
+- `MAX_UNAUTHORIZED` stays at **103** and is untouched by this release. It read 103 before only because the gate was crediting the nine broken write routes; with the crediting removed the true figure on v12.3.1 is 112, and wiring them returns it to 103 honestly. The ceiling did not move, but it now means what it says.
+
+### Fixed
+
+- Measured against v12.3.1 and this release: discarded permissions **11 → 0**, identity-only write routes **112 → 103**, and the new regression suite `services/api/tests/test_discarded_permission_dependencies.py` **23 failed / 2 passed → 25 passed**. Every pre-fix failure is an assertion about the defect — the permission absent from the resolved dependency tree, the principal arriving as a query parameter, a `viewer` reaching a handler — and none is an `ImportError`. The two that pass on both trees are the controls that stop the rest passing for the wrong reason: that `viewer` holds none of the permissions under test, and that `tenant_admin` is still not refused.
+
## [12.3.1] - 2026-09-29
### Security
diff --git a/README.md b/README.md
index 26f9bc321..10b8d8702 100644
--- a/README.md
+++ b/README.md
@@ -7,7 +7,7 @@
**An open-source, self-hostable AI Security Operations Center.** It ingests your security telemetry, detects and correlates threats, investigates them with AI agents whose reasoning is fully auditable, and proposes responses a human approves.
[![License: MIT](https://img.shields.io/badge/License-MIT-22c55e.svg?style=flat-square)](https://opensource.org/licenses/MIT)
-[![Version](https://img.shields.io/badge/version-12.3.1-f59e0b?style=flat-square)](CHANGELOG.md)
+[![Version](https://img.shields.io/badge/version-12.3.2-f59e0b?style=flat-square)](CHANGELOG.md)
[![CI](https://img.shields.io/github/actions/workflow/status/beenuar/AiSOC/ci.yml?branch=main&label=CI&style=flat-square)](https://github.com/beenuar/AiSOC/actions/workflows/ci.yml)
[![CodeQL](https://img.shields.io/github/actions/workflow/status/beenuar/AiSOC/codeql.yml?branch=main&label=CodeQL&style=flat-square)](https://github.com/beenuar/AiSOC/actions/workflows/codeql.yml)
[![OpenSSF Scorecard](https://api.securityscorecards.dev/projects/github.com/beenuar/AiSOC/badge)](https://securityscorecards.dev/viewer/?uri=github.com/beenuar/AiSOC)
diff --git a/RELEASES.md b/RELEASES.md
index bbbbb622c..db2cc9854 100644
--- a/RELEASES.md
+++ b/RELEASES.md
@@ -2,14 +2,17 @@
This file mirrors what used to live in the "What's new" section of [`README.md`](README.md). The complete, machine-readable inventory (with file paths, env-var diffs, and per-release test counts) lives in [`CHANGELOG.md`](CHANGELOG.md).
-> **TL;DR for first-time visitors:** AiSOC is on `v12.3.1`, released 2026-09-29 — a security patch on top of v12.3.0, and the reason it exists separately is that a fix living on `main` is not a fix anyone has. Two reported advisories: a **critical** SQL injection in the osquery allowlist, where a denylist scanning rendered SQL for `--`, `/*` and `;` had never listed `'`, so a value could close a quoted literal and replace the WHERE clause — and reproducing it showed all six query templates were injectable, not the one reported, because the numeric parameters were never coerced either. Each parameter now declares what it is and anything else is refused rather than escaped, because an escaped path still reaches the endpoint, matches nothing, and reads to an operator as a clean host. The second is a **high** missing-authorization hole where every remediation write route authenticated and none authorized, so a `viewer` could raise the tenant to autonomy L4 and pre-approve a high blast-radius verb; the permission it needed already existed and was simply never enforced, which is the third time on this repository. The gate that should have caught it passed throughout, because it asks whether a route authenticates — so a second gate now asks whether it authorizes, and measures 103 of 246 state-changing routes making no authorization decision, as a ceiling that can only fall. Upgrading is `make up`. v12.3.0 (same day) closed six lettered sub-phases; its notes are below. None of the eight first-party npm/PyPI packages has been uploaded — the registries return 404 for all eight — and that remains credential-blocked rather than done. The latest GitHub release with notes and downloads: <https://github.com/beenuar/AiSOC/releases/latest>.
+> **TL;DR for first-time visitors:** AiSOC is on `v12.3.2`, released 2026-09-29 — a second security patch the same day, and the reason is the same one v12.3.1 existed for: eleven more write routes were found declaring a permission that never ran. `Annotated[Any, require_permission("users:write")]` carries no `Depends()`, and FastAPI honours only `Annotated` metadata that is a `Depends` or a `FieldInfo` — everything else is silently dropped, so the check never happened and `current_user` degraded into a required query parameter. The tell was the status code: a `viewer` hitting these routes got **422, not 403**, which reads as a malformed request rather than a refusal. v12.3.1 was a security patch on top of v12.3.0, and the reason it exists separately is that a fix living on `main` is not a fix anyone has. Two reported advisories: a **critical** SQL injection in the osquery allowlist, where a denylist scanning rendered SQL for `--`, `/*` and `;` had never listed `'`, so a value could close a quoted literal and replace the WHERE clause — and reproducing it showed all six query templates were injectable, not the one reported, because the numeric parameters were never coerced either. Each parameter now declares what it is and anything else is refused rather than escaped, because an escaped path still reaches the endpoint, matches nothing, and reads to an operator as a clean host. The second is a **high** missing-authorization hole where every remediation write route authenticated and none authorized, so a `viewer` could raise the tenant to autonomy L4 and pre-approve a high blast-radius verb; the permission it needed already existed and was simply never enforced, which is the third time on this repository. The gate that should have caught it passed throughout, because it asks whether a route authenticates — so a second gate now asks whether it authorizes, and measures 103 of 246 state-changing routes making no authorization decision, as a ceiling that can only fall. Upgrading is `make up`. v12.3.0 (same day) closed six lettered sub-phases; its notes are below. None of the eight first-party npm/PyPI packages has been uploaded — the registries return 404 for all eight — and that remains credential-blocked rather than done. The latest GitHub release with notes and downloads: <https://github.com/beenuar/AiSOC/releases/latest>.
---
## What's new
-`VERSION` is `12.3.1`. The **v12.3.1** release (2026-09-29) is a security
-patch: two reported advisories fixed, no feature change and nothing breaking.
+`VERSION` is `12.3.2`. The **v12.3.2** release (2026-09-29) wires eleven
+`require_permission` dependencies that FastAPI had been discarding, found
+by sweeping the sibling modules for the omission behind
+GHSA-wj5c-88hg-5926. The **v12.3.1** release earlier the same day is a
+security patch: two reported advisories fixed, no feature change and nothing breaking.
It follows v12.3.0 the same day because a fix that sits on `main` is not a fix
anyone running the published images has.
diff --git a/VERSION b/VERSION
index 9c028e25d..1701b30e1 100644
--- a/VERSION
+++ b/VERSION
@@ -1 +1 @@
-12.3.1
+12.3.2
diff --git a/apps/docs/static/data/scoreboard.json b/apps/docs/static/data/scoreboard.json
index 1bdad2406..61fcbd106 100644
--- a/apps/docs/static/data/scoreboard.json
+++ b/apps/docs/static/data/scoreboard.json
@@ -4,8 +4,8 @@
"rows": [
{
"date": "2026-09-29",
- "agent_version": "v12.3.1",
- "commit_sha": "0e3a3866",
+ "agent_version": "v12.3.2",
+ "commit_sha": "2eaebcbc",
"substrate": true,
"eval_mode": "substrate-only",
"mitre_accuracy": 0.97,
diff --git a/apps/docs/static/llms-full.txt b/apps/docs/static/llms-full.txt
index 6f9b456a4..372424178 100644
--- a/apps/docs/static/llms-full.txt
+++ b/apps/docs/static/llms-full.txt
@@ -3,7 +3,7 @@
<!-- Generated by scripts/generate_llms_txt.py. Do not edit by hand; run the script and commit the result. -->
> AiSOC is an open-source, self-hostable AI Security Operations Center, MIT
-> licensed and maintained by the AiSOC community. Version 12.3.1.
+> licensed and maintained by the AiSOC community. Version 12.3.2.
> Repository: https://github.com/beenuar/AiSOC. Documentation: https://beenuar.github.io/AiSOC/.
This file exists so an automated reader can answer questions about AiSOC
diff --git a/apps/docs/static/llms.txt b/apps/docs/static/llms.txt
index f375201bb..4ca27b115 100644
--- a/apps/docs/static/llms.txt
+++ b/apps/docs/static/llms.txt
@@ -6,7 +6,7 @@
> security telemetry from 84 first-party connectors, normalises it to OCSF,
> correlates it into alerts, and runs LLM agents that triage and investigate them.
> Every agent decision is written to an investigation ledger, so the reasoning
-> behind a verdict can be replayed step by step. MIT licensed. Current version 12.3.1.
+> behind a verdict can be replayed step by step. MIT licensed. Current version 12.3.2.
AiSOC is built and maintained by the AiSOC community. It is a complete SOC
platform rather than a single tool: ingestion, detection, correlation, agent
diff --git a/apps/web/package.json b/apps/web/package.json
index d0dafb23a..9268bbead 100644
--- a/apps/web/package.json
+++ b/apps/web/package.json
@@ -1,6 +1,6 @@
{
"name": "@aisoc/web",
- "version": "12.3.1",
+ "version": "12.3.2",
"private": true,
"description": "AiSOC SOC Console - Next.js 14 Frontend",
"license": "MIT",
diff --git a/infra/helm/aisoc/Chart.yaml b/infra/helm/aisoc/Chart.yaml
index 873a76221..78cae779f 100644
--- a/infra/helm/aisoc/Chart.yaml
+++ b/infra/helm/aisoc/Chart.yaml
@@ -2,13 +2,13 @@ apiVersion: v2
name: aisoc
description: AiSOC - the open-source, AI-native Security Operations Center
type: application
-version: 5.9.1
+version: 5.9.2
# Used as the image tag wherever a `tag:` in values.yaml is left empty, so
# it has to be a tag the registry actually holds — it read "5.2.0", which
# exists for no image, so every pod of a default install would have gone to
# ImagePullBackOff. scripts/check_published_images.py resolves it the same
# way the templates do and fails when it names nothing.
-appVersion: "v12.3.1"
+appVersion: "v12.3.2"
keywords:
- security