Repository navigation
AiSOC v20.0.0 — four published advisories, SSRF guard on every connector egress path, dependency queue at zero #1439
beenuar
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
AiSOC v20.0.0 is out: release notes · full changelog.
This release is the close-out of a maintenance cycle that worked the queue to zero: every open pull request reviewed and merged or closed with its reason, every open issue resolved, the Dependabot queue emptied, and four vulnerability reports taken from reproduction to published advisory.
Four advisories, reproduced before fixed
Each report was reproduced against a production-mode stack before any patch was written, fixed, and published with credit to its reporter:
GETroutes enforced nocases:read, so an API key minted with onlyalerts:readcould list cases and read their comments, timeline and evidence chain. Reported by @antigravitysoham-eng.cases:writeholder could author a comment the console renders as an unattributed "System note". Reported by @antigravitysoham-eng. Closing it is the release's one breaking change: the create route no longer acceptsis_system(ignored, not refused — existing clients keep succeeding).base_urlcould reach cloud metadata, loopback and internal services. Reported by @tal2k9dev-star.The SSRF guard now sits on every connector egress path
The stateless test route, resource reads and scheduled polls all validate through the same guard the playbook engine uses; the API refuses the same destinations at connector create/update, before anything is encrypted and stored. The relax knobs are delivered to every service that runs the guard from one
.envvalue:AISOC_SSRF_ALLOW_PRIVATEfor on-prem systems on private ranges,AISOC_SSRF_ALLOW_HOSTSfor exact named hosts. The cloud-metadata blocklist holds regardless of either. Documentation: operations/security.Supply-chain pinning, in both directions
certifi,aiohttp,pillow, the MCP SDK, and the npm floors. One recorded, expiring exception:services/threatintelgenuinely embeds throughfastembed, whose every release capspillowbelow the fixed version, so its lock stays on 12.3.0 under nine suppressions with stated reasons (text-only embedding input, no PIL import) and a 2027-01-15 re-check date.Also in this release
high; Datadog'semergencyandalertlevels map tocriticaltoo. All contributed by @meshreyy.Defect count
23 distinct defects were addressed across this release and the one before it: 12 in v20.0.0 and 11 in v19.0.0, counting each distinct defect described under the Fixed and Security headings of those two CHANGELOG sections (dependency-advisory clears are listed above separately, not double-counted).
Upgraders: read the BREAKING section at the top of the v20.0.0 notes first. It is one request-schema change with a compatibility path.
All reactions