Denial of Service in mem

published 2019-07-05 7y ago modified 2021-08-17 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 `mem` prior to 4.0.0 are vulnerable to Denial of Service (DoS). The package fails to remove old values from the cache even after a value passes its `maxAge` property. This may allow attackers to exhaust the system's memory if they are able to abuse the application logging.

## Recommendation

Upgrade to version 4.0.0 or later.

Patch / fix

fixed in 1 links 1

npm mem 4.0.0

github.com/sindresorhus/mem@da4e439 commit

Is GHSA-4xcv-9jjx-gfj3 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	mem	<4.0.0	4.0.0

Classification

Weakness

CWE-400 Uncontrolled Resource Consumption

References

Sources

GitHub Advisory GHSA-4xcv-9jjx-gfj3

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.