Skip to content
Fencer Intel
low —

GHSA-5rrq-pxf6-6jx5 json

Prototype Pollution in node-forge debug API.

published 4y ago modified 4y ago

cvss
—
not scored
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

Summary

### 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](https://github.com/digitalbazaar/forge). * Email us at support@digitalbazaar.com.

Patch / fix

  • npm node-forge 1.0.0

Is GHSA-5rrq-pxf6-6jx5 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Affected packages

ecosystem package affected fixed in
npm node-forge
<1.0.0
1.0.0

Classification

Weakness
  • CWE-1321 Improperly Controlled Modification of Object Prototype Attributes

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

The maintainers of digitalbazaar/forge published their own advisory on GitHub. Reviewed sources take precedence over it.