Skip to content
Fencer Intel
low —

GHSA-wxgw-qj99-44c2 json

Prototype Pollution in node-forge util.setPath 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 `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](https://github.com/digitalbazaar/forge). * Email us at support@digitalbazaar.com.

Patch / fix

  • npm node-forge 0.10.0

Is GHSA-wxgw-qj99-44c2 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
<0.10.0
0.10.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.