Out-of-bounds Read in base64url

published 2020-09-01 6y ago modified 2021-09-24 5y 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

Versions of `base64url` before 3.0.0 are vulnerable to to out-of-bounds reads as it allocates uninitialized Buffers when number is passed in input on Node.js 4.x and below.

## Recommendation

Update to version 3.0.0 or later.

Patch / fix

fixed in 1 links 2

npm base64url 3.0.0

github.com/brianloveswords/base64url@4fbd954 commit
github.com/brianloveswords/base64url#25 pull request

Is GHSA-rvg8-pwq2-xj7q 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	base64url	<3.0.0	3.0.0

Classification

Weakness

CWE-125 Out-of-bounds Read

References

Sources

GitHub Advisory GHSA-rvg8-pwq2-xj7q

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.