Prototype Pollution in node-forge debug API.
Published 8 Jan 2022 · Updated 7 Jan 2022
Affected package
- Affected
- <1.0.0
- Fixed in
- 1.0.0
npm install node-forge@1.0.0Details
Impact
The forge.debug API had a potential prototype pollution issue if called with untrusted input. The API was only used for internal debug purposes in a safe way and never documented or advertised. It is suspected that uses of this API, if any exist, would likely not have used untrusted inputs in a vulnerable way.
Patches
The forge.debug API and related functions were removed in 1.0.0.
Workarounds
Don't use the forge.debug API directly or indirectly with untrusted input.
References
- https://www.huntr.dev/bounties/1-npm-node-forge/
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-5rrq-pxf6-6jx5 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.
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.