OSV Scanner (steg 6 i security-gaten) fällde jobbet efter att Trivy blivit grönt: 43 advisory-poster över 10 paket. Samma skanning mot origin/main ger 9 av 10 paket — posterna publicerades mot versioner vi redan kör, så main hade blivit röd vid nästa nattliga skanning oavsett denna PR. Bumpat (alla verifierade med osv-scanner och hela unit-sviten): nodemailer 10.0.6/10.0.10 -> 10.1.4 (direkt + override för mailparser) zod 4.4.3 -> 4.6.7 (^4.6.6) vite 8.1.3 -> 8.3.8 (override ^8.1.6, dev via vitest) vitest 4.1.11 -> 4.1.12 (^4.1.12, tar @vitest/mocker 4.1.12) @babel/core 7.28.6 -> 7.29.13 (override, dev via eslint-plugin-react-hooks) fast-xml-parser 5.7.2 -> 5.12.1 (override, via @aws-sdk/xml-builder) minimatch 9.0.9 -> 11.0.8 (override, dev via typescript-eslint) postcss-selector-parser 6.0.10 -> 6.1.6 (override, via @tailwindcss/typography) python-multipart -> >=0.0.31 (explicit floor i mcp-builder-skillens requirements.txt; OSV kan inte lösa en otransitiv, opinnad requirement) xlsx 0.20.3 undantas i osv-scanner.toml med effectiveUntil 2027-05-15: GHSA-4r6h-8v6p-xvw6 och GHSA-5pgg-2g8v-p4x9 har introduced:0 och INGET fixed-event (kontrollerat mot api.osv.dev), eftersom SheetJS slutade publicera till npm efter 0.18.5. Vi pinnar 0.20.3 från cdn.sheetjs.com, som redan innehåller båda fixarna (0.19.3 / 0.20.2). Skanningen rapporterar alltså en versionsupplösningsartefakt. Filen varnar uttryckligen om att lib/import/* parsar användaruppladdade arbetsböcker, så undantaget får inte läsas som tillstånd att acceptera ofixade parser-CVE:er. Verifiering: osv-scanner --config=osv-scanner.toml -> "No issues found" rc=0; 1687 filer / 22 400 tester gröna; check:types 533/533; check:lint 0 fel; check:guards passed; Trivy 0 fynd. Revert: git revert <sha>. Enda beteendepåverkande posten är osv-scanner.toml (utan den blir gaten röd igen på xlsx); minimatch 9 -> 11 används bara av lint-kedjan och verifieras av check:lint + sviten.
35 lines
1.9 KiB
TOML
35 lines
1.9 KiB
TOML
# osv-scanner configuration. Read by .gitea/workflows/security.yml, which passes
|
|
# --config when this file exists.
|
|
#
|
|
# The two entries below are the SheetJS advisories. They are ignored because the
|
|
# fix is not obtainable from npm at any version: SheetJS stopped publishing to
|
|
# the npm registry after 0.18.5 and ships 0.19+ from cdn.sheetjs.com, so both
|
|
# GHSA records have `introduced: 0` and no `fixed` event (verified against
|
|
# api.osv.dev 2026-11-15). This repo consumes `xlsx` as a URL dependency,
|
|
# https://cdn.sheetjs.com/xlsx-0.20.3/xlsx-0.20.3.tgz, and 0.20.3 already
|
|
# contains both fixes:
|
|
#
|
|
# GHSA-4r6h-8v6p-xvw6 (CVE-2023-30533, prototype pollution) — fixed upstream in 0.19.3
|
|
# GHSA-5pgg-2g8v-p4x9 (CVE-2024-22363, ReDoS) — fixed upstream in 0.20.2
|
|
#
|
|
# So the scanner is reporting a version-resolution artefact, not a live defect.
|
|
# The entries still expire: if we ever pin an older tarball, or migrate to a
|
|
# maintained parser, this file must be revisited rather than inherited. Owner:
|
|
# admin/accounted maintainers. Expiry is deliberate; the nightly scan re-reports
|
|
# both advisories the day it passes.
|
|
#
|
|
# Deliberately NOT in scope here: the prototype-pollution and ReDoS classes are
|
|
# about parsing untrusted workbooks, and lib/import/* does exactly that. The
|
|
# mitigations are upstream (both fixed in our pinned version) — do not treat
|
|
# this file as permission to accept unfixed parser CVEs.
|
|
|
|
[[IgnoredVulns]]
|
|
id = "GHSA-4r6h-8v6p-xvw6"
|
|
effectiveUntil = 2027-05-15
|
|
reason = "CVE-2023-30533 fixed upstream in SheetJS 0.19.3; we pin 0.20.3 from cdn.sheetjs.com. No npm release carries the fix, so no version can satisfy the advisory."
|
|
|
|
[[IgnoredVulns]]
|
|
id = "GHSA-5pgg-2g8v-p4x9"
|
|
effectiveUntil = 2027-05-15
|
|
reason = "CVE-2024-22363 fixed upstream in SheetJS 0.20.2; we pin 0.20.3 from cdn.sheetjs.com. No npm release carries the fix, so no version can satisfy the advisory."
|