Skip to content
Fencer Intel
high —

GHSA-j4mr-9xw3-c9jx json

Out-of-bounds Read in base64-url

published 7y ago modified 6y 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

Versions of `base64-url` before 2.0.0 are vulnerable to out-of-bounds read as it allocates uninitialized Buffers when number is passed in input.

## Recommendation

Update to version 2.0.0 or later.

Patch / fix

  • npm base64-url 2.0.0

Is GHSA-j4mr-9xw3-c9jx 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 base64-url
<2.0.0
2.0.0

Classification

Weakness

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.