Repository navigation
chore(deps): exempt GHSA-xcx6-jx8p-x3h5 (@azure/msal-node via tedious) until 2026-11-26 - #26486
Conversation
…) until 2026-11-26 The scheduled OSV scan has been red on main every day since 2026-10-21. The one finding is GHSA-xcx6-jx8p-x3h5 (High): @azure/msal-node 5.4.1, patched only in 7.1.0. It arrives through tedious 18.6.2, driver-sql's optional mssql peer (dev tree only), then @azure/identity 4.13.1. No published @azure/identity accepts msal-node 7 yet; 4.14.0, the latest, requires ^6. The flaw is in the authorization-code flow (acquireTokenByCode), which tedious never calls. A 30-day exemption, per the ledger's conventions. Fixes #26428 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01ADHkmPhbmyqwyDkSjg13F7
席位核对 · ACCEPT · devx seat 2 · 2026-10-27T04:56ZSeat
Landing: auto-merge on green CI. The card closes on |
|
devx seat 2 · landing correction: auto-merge, armed with the ACCEPT above, has been disabled again. The PR was never queued. Accepting a known High advisory waits for the maintainer's explicit approval. The seat enables auto-merge after that approval, not before. Generated by Claude Code |
Requested by Steve · project thread
Fixes #26428
维护者速读
osv-scanner.toml加一条豁免,GHSA-xcx6-jx8p-x3h5,ignoreUntil = 2026-11-26(30 天)。只改这一个文件。@azure/msal-node5.4.1,High。修复版是 7.1.0,但目前没有任何已发布的@azure/identity接受 msal-node 7(最新的 4.14.0 仍要求^6),所以拿不到修复版。@azure/identity→ msal-node,不进任何发布包。漏洞在授权码流程(acquireTokenByCode),tedious 不调用它。What changes
One
[[IgnoredVulns]]entry inosv-scanner.toml. This PR carries no other change, per convention 3 (an exemption lands in its own PR, labelledosv-exemption).Why
What the scan shows. Scheduled run 40442115529 (2026-10-27 03:05Z), OSV-Scanner v2.5.0 on
pnpm-lock.yaml:The advisory (osv.dev): "MSAL Node authorization code flow may disclose parameters to an attacker-controlled endpoint", CWE-346. Affected from
5.0.0-beta.0to before7.1.0. The workaround it names is passing only the auth code toacquireTokenByCode.Why no fix can be taken today.
tedious@18.6.2→@azure/identity@4.13.1→@azure/msal-node@5.4.1. tedious isdriver-sql's optionalpeerDependency, so this repo installs it for its own tree and no published package carries it.npm view @azure/identity@4.14.0 dependencies.@azure/msal-nodegives^6.0.0, and every 6.x is inside the affected range. tedious 20.3.8, its latest, needs@azure/identity ^4.13.1.@azure/identitydeclares. This PR does not do that.When to remove it. Once a published
@azure/identityaccepts msal-node>=7.1.0and tedious resolves to it, bump instead and delete this entry. The 30-dayignoreUntilforces this decision to be looked at again.Also reported by the same scan, not changed here
The scanner reports the existing
GHSA-hp3w-g68c-fv3centry (sprintf-js,ignoreUntil = 2026-11-05) as an unused ignore. osv.dev shows that advisory withdrawn on 2026-10-22, so the entry no longer matches anything, thoughsprintf-js1.0.3 and 1.1.3 are still in the lockfile. It is left alone here: one exemption change per PR. It can be removed in its own PR, or it will drop out on its own date.Verification
node scripts/check-osv-exemptions.mjs --self-test: passes.node scripts/check-osv-exemptions.mjs:✓ 2 OSV exemption(s) in osv-scanner.toml: all carry an unexpired ignoreUntil within 90 days and a reason with an advisory link.Validate Dependenciesrun (triggered byosv-scanner.toml) is the measurement.Clause-②: no
Metadata-protocol: none
Human Minimum
packages/specholds no runtime logic. (not touched)pnpm lintpasses.main, one pull request.skip-changeset.packages/spectouched: n/a.content/docs/references/,packages/*/CHANGELOG.mdorcontent/docs/releases/.Generated by Claude Code