Out-of-bounds Read in byte

published 2019-06-04 7y ago modified 2020-08-31 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

Versions of `byte` before 1.4.1 allocate uninitialized buffers and read data from them past the initialized length

## Recommendation

Update to version 1.4.1 or later.

Patch / fix

fixed in 1 links 1

npm byte 1.4.1

github.com/node-modules/byte#3 pull request

Is GHSA-xm7f-x4wx-wmgv 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	byte	<1.4.1	1.4.1

Classification

Weakness

CWE-125 Out-of-bounds Read

References

github.com /node-modules/byte/pull/3
web
hackerone.com /reports/330351
web
npmjs.com /advisories/657
web

Sources

GitHub Advisory GHSA-xm7f-x4wx-wmgv

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.