Advisory Database
  • Advisories
  • Dependency Scanning
  1. npm
  2. ›
  3. node-forge
  4. ›
  5. GMS-2022-66

GMS-2022-66: Prototype Pollution in node-forge debug API.

January 8, 2022

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.

References

  • github.com/advisories/GHSA-5rrq-pxf6-6jx5
  • github.com/digitalbazaar/forge/security/advisories/GHSA-5rrq-pxf6-6jx5

Code Behaviors & Features

Detect and mitigate GMS-2022-66 with GitLab Dependency Scanning

Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Dependency Scanning using SBOM also detects vulnerabilities from proprietary advisories that this site does not include. Learn more about Dependency Scanning using SBOM →

Affected versions

All versions before 1.0.0

Fixed versions

  • 1.0.0

Solution

Upgrade to version 1.0.0 or above.

Source file

npm/node-forge/GMS-2022-66.yml

Spotted a mistake? Edit the file on GitLab.

  • Site Repo
  • About GitLab
  • Terms
  • Privacy Statement
  • Contact

Page generated Sun, 08 Nov 2026 00:15:52 +0000.