Skip to content

fix(deps): patch-bump 9 transitive deps for published CVEs - #344

Open
Svector-anu wants to merge 1 commit into
fireblocks:masterfrom
Svector-anu:security/bump-transitive-deps-multi-cve
Open

Svector-anu wants to merge 1 commit into
fireblocks:masterfrom
Svector-anu:security/bump-transitive-deps-multi-cve

Conversation

@Svector-anu

Copy link
Copy Markdown

Lockfile-only dependency patch bump addressing several published CVEs in transitive dependencies, generated via npm audit fix --package-lock-only (no --force, no package.json changes, no breaking changes).

Bumped

Package From To Advisory
qs 6.11.1 6.16.0 GHSA-4mjr-xmp4-gh2g, GHSA-6rw7-vpxm-498p, GHSA-q8mj-m7cp-5q26, GHSA-w7fw-mjwx-w883
lodash 4.17.21 4.18.1 GHSA-f23m-r3pf-42rh, GHSA-r5fr-rjxr-66jc, GHSA-xxjr-mmjv-4gpg
form-data 4.0.5 4.0.6 GHSA-hmw2-7cc7-3qxx (CVE-2026-12143, CRLF injection)
base-x 4.0.0 4.0.1 GHSA-xq7p-g2vc-g82p (homograph/Unicode-lookalike bypass) — closes #333
jws 3.2.2 3.2.3 GHSA-869p-cjfg-cm3x (improper HMAC signature verification)
js-yaml 3.14.1 3.15.2 dev-only, transitive of tslint
minimatch 3.1.2 3.1.5 dev-only, transitive of tslint
brace-expansion 1.1.11 1.1.18 dev-only, transitive of tslint
diff 4.0.2 4.0.4 dev-only, transitive of tslint

Detected by osv-scanner and cross-checked against npm audit.

Not included — no non-breaking fix available

  • @stablelib/ed25519 (transitive via @notabene/pii-sdk) — GHSA-x3ff-w252-2g7j (Ed25519 signature malleability, missing S < L check) has no patched release yet; it still affects the package's latest version (2.0.2). Bumping wouldn't help. Flagging for awareness since @notabene/pii-sdk ships this transitively.
  • uuid 8.3.2 — GHSA-w5hq-g745-h8pq (missing buffer bounds check in v3/v5/v6) needs a major bump, which is out of scope for a lockfile-only patch.
  • decode-uri-component 0.2.2 (transitive via query-string) — GHSA-vcc3-ghjq-m6fr fix requires bumping query-string past a breaking change (5.0.0–9.4.1 → 9.5.1).

Verification

  • Reproduced locally: yes
  • Command: npm audit fix --package-lock-only then osv-scanner scan source --recursive --no-ignore . before/after
  • Before: 28 known-vulnerable transitive packages flagged by osv-scanner
  • After: 4 remain (the three listed above as "not included", uuid appearing under two nested resolutions)
  • Environment: npm 10.9.8, node 22.23.2, osv-scanner 2.5.1

No code changes outside the lockfile.

…only)

Regenerated via `npm audit fix --package-lock-only` (no --force, no
package.json changes, no breaking changes):

- qs 6.11.1 -> 6.16.0 (GHSA-4mjr-xmp4-gh2g, GHSA-6rw7-vpxm-498p,
  GHSA-q8mj-m7cp-5q26, GHSA-w7fw-mjwx-w883)
- lodash 4.17.21 -> 4.18.1 (GHSA-f23m-r3pf-42rh, GHSA-r5fr-rjxr-66jc,
  GHSA-xxjr-mmjv-4gpg)
- form-data 4.0.5 -> 4.0.6 (GHSA-hmw2-7cc7-3qxx, CVE-2026-12143)
- base-x 4.0.0 -> 4.0.1 (GHSA-xq7p-g2vc-g82p) - closes fireblocks#333
- jws 3.2.2 -> 3.2.3 (GHSA-869p-cjfg-cm3x)
- js-yaml, minimatch, brace-expansion, diff - dev-only transitive bumps

Not included (no non-breaking fix available, left for manual review):
- @stablelib/ed25519 - GHSA-x3ff-w252-2g7j has no patched release yet
  (still affects latest 2.0.2)
- uuid 8.3.2 - GHSA-w5hq-g745-h8pq fix requires a major bump
- decode-uri-component 0.2.2 - fix requires query-string major bump
  (5.0.0-9.4.1 -> 9.5.1)
@socket-security

Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Updated@​notabene/​pii-sdk@​1.17.1 ⏵ 1.17.292 -610010090 +6100
Updatedqs@​6.11.1 ⏵ 6.16.0100100 +510093 -2100

View full report

@semgrep-code-fireblocks

Copy link
Copy Markdown

Semgrep found 19 block-public-registry-refs-in-package-lock findings:

package-lock.json contains a reference to a public package registry or CDN (https://registry.npmjs.org/side-channel-weakmap/-/side-channel-weakmap-1.0.2.tgz). Dependencies must be resolved through the approved internal JFrog/Artifactory registry. Update your .npmrc to point at the approved registry, delete node_modules and package-lock.json, then re-run npm install and commit the regenerated lockfile.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug] base-x >= 4.0.1

1 participant