Remote Memory Exposure in floody

published 2019-06-04 7y ago modified 2021-08-04 5y ago

cvss: 5.1; version 3.1, GitHub
cisa kev: Not listed; not in CISA's catalog
epss: —; no score, EPSS covers CVEs only
public exploits: 0; none known

Versions of `floody` before 0.1.1 are vulnerable to remote memory exposure.

.write(number)` in the affected `floody` versions passes a number to Buffer constructor, appending a chunk of uninitialized memory.

Proof of Concept:

``` var f = require('floody')(process.stdout); f.write(USERSUPPLIEDINPUT); 'f.stop();

## Recommendation

Update to version 0.1.1 or later.

Patch / fix

fixed in 1 links 1

npm floody 0.1.1

github.com/soldair/node-floody@6c44722 commit

Is GHSA-3p92-886g-qxpq 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

CVSS scores

assigned by	version	score	vector
GitHub	3.1	5.1	CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

Affected packages

ecosystem	package	affected	fixed in
npm	floody	<0.1.1	0.1.1

Classification

Weakness

CWE-201 Insertion of Sensitive Information Into Sent Data

References

Sources

GitHub Advisory GHSA-3p92-886g-qxpq

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.