LowGHSA-wxgw-qj99-44c2

Prototype Pollution in node-forge util.setPath API

Published 8 Jan 2022 · Updated 7 Jan 2022

Affected package

Affected: <0.10.0
Fixed in: 0.10.0

Update to the fixed version for your release line, for example:npm install node-forge@0.10.0

Details

Impact

forge.util.setPath had a potential prototype pollution issue if called with untrusted keys. This API was not used by forge itself.

Patches

The forge.util.setPath API and related functions were removed in 0.10.0.

Workarounds

Don't call forge.util.setPath directly or indirectly with untrusted keys.

References

https://security.snyk.io/vuln/SNYK-JS-NODEFORGE-598677
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-7720

For more information

If you have any questions or comments about this advisory:

Open an issue in forge.
Email us at support@digitalbazaar.com.

Is GHSA-wxgw-qj99-44c2 in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected node-forge, and gives you the command that fixes it.

Scan a project free, no signup Or connect GitHub to scan every repo

References

Linkgithub.com/digitalbazaar/forge/security/advisories/GHSA-wxgw-qj99-44c2

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.