Buffer Overflow in node-weakauras-parser

published 2020-09-03 6y ago modified 2021-10-04 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

Affected versions of `node-weakauras-parser` are vulnerable to a Buffer Overflow. The `encode_weakaura` function fails to properly validate the input size. A buffer of 13835058055282163711 bytes causes an overflow on 64-bit systems.

## Recommendation

Upgrade to versions 1.0.5, 2.0.2, 3.0.1 or later.

Patch / fix

fixed in 1 links 1

npm node-weakauras-parser 1.0.5, 2.0.2, 3.0.1

github.com/Zireael-N/node-weakauras-parser@bc146da commit

Is GHSA-86mr-6m89-vgj3 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-weakauras-parser	>=1.0.4, <1.0.5 >=2.0.0, <2.0.2 >=3.0.0, <3.0.1	1.0.5 2.0.2 3.0.1

Classification

Weakness

CWE-120 Buffer Copy without Checking Size of Input

References

Sources

GitHub Advisory GHSA-86mr-6m89-vgj3

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.