diff --git a/package.json b/package.json index 67cab9b9..e3ce8f77 100644 --- a/package.json +++ b/package.json @@ -111,9 +111,7 @@ "on-headers": "^1.1.0", "systeminformation": "^5.33.19", "@asyncapi/specs": "6.11.1", - "gaxios@7.1.3": "^7.3.1", - "follow-redirects": "^1.16.2", - "body-parser": "^1.20.9" + "gaxios@7.1.3": "^7.3.1" }, "resolutionsNotes": { "@stryker-mutator/core/minimatch": "Dev tooling, not a CVE override. Added when a blanket `brace-expansion` pin forced v2 (CJS) while minimatch v10 needs v5's named exports. That blanket pin is gone — it broke `nx affected` the same way — so brace-expansion now resolves per consumer and Stryker would most likely work on minimatch v10. The pin stays because no CI job runs `yarn dev:mutation`, so nothing would catch it if that guess is wrong. Drop it once someone has run the mutation suite on v10. See CONTRIBUTING.md#mutation-tests." diff --git a/security/overrides.yaml b/security/overrides.yaml index e96022c3..663f3ba8 100644 --- a/security/overrides.yaml +++ b/security/overrides.yaml @@ -40,43 +40,7 @@ # `--check` tells you when. Delete the entry, delete the resolutions line, # run `yarn install` to re-resolve, done. -overrides: - - package: follow-redirects - range: '^1.16.2' - advisory: GHSA-mrwp-f3q8-3g9p - severity: high - vector: >- - No live vector. It is pinned because the vulnerable copy ships and the fix - is one generated line. packages/api/package.json:32 declares - @slack/webhook, whose axios 1.20.0 resolves follow-redirects into the - production focus. GHSA-mrwp-f3q8-3g9p (a cross-realm sensitiveHeaders - array is discarded), GHSA-q3jh-wrc6-jgq8 (array-form headers) and - GHSA-8r9p-f939-6h3c (sensitiveHeaders escaping) all need follow-redirects - to follow a cross-origin redirect. @slack/webhook's IncomingWebhook.js:26 - sets maxRedirects to 0, so axios takes the native http transport - (lib/adapters/http.js:1051) and follow-redirects follows nothing. Nothing - in packages/*/src sets sensitiveHeaders. nx's exact 1.16.0 pin, dev only, - moves with it. - upstream: none - added: 2026-10-21 - - package: body-parser - range: '^1.20.9' - advisory: GHSA-27r3-jxmh-p828 - severity: high - vector: >- - express 4.22.1 declares body-parser ~1.20.3 and resolves 1.20.6. On a - request carrying Content-Encoding, body-parser pipes the body into a - decompression stream and leaves it piped with no error listener once the - body is read, so trailing bytes after a valid frame reach the finished - decoder and its error ends the process (body-parser lib/read.js:151-188). - The three parsers at packages/api/src/api-app.ts:78-80 run before routing - and before the engine token check, so any caller that reaches the API can - do it unauthenticated. 1.20.9 detaches and destroys the stream and adds an - error listener. The pin also covers the OpAMP raw parser (opamp/app.ts:15) - and the PromQL urlencoded parser (routers/api/prometheus.ts:56), which - stay inflating. - upstream: none - added: 2026-10-28 +overrides: [] # Example of the shape (keep commented - an empty register is the goal state): # # - package: some-parser diff --git a/yarn.lock b/yarn.lock index aaeb0d05..b486c238 100644 --- a/yarn.lock +++ b/yarn.lock @@ -12760,7 +12760,7 @@ __metadata: languageName: node linkType: hard -"body-parser@npm:^1.20.9": +"body-parser@npm:~1.20.5": version: 1.20.9 resolution: "body-parser@npm:1.20.9" dependencies: