Remote Memory Exposure in mongoose

published 2020-09-01 6y ago modified 2023-12-07 2y 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 `mongoose` before 4.3.6, 3.8.39 are vulnerable to remote memory exposure.

Trying to save a number to a field of type Buffer on the affected mongoose versions allocates a chunk of uninitialized memory and stores it in the database.

## Recommendation

Update to version 4.3.6, 3.8.39 or later.

Patch / fix

fixed in 1

npm mongoose 3.8.39, 4.3.6

Is GHSA-r5xw-q988-826m 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	mongoose	>=3.5.5, <3.8.39 >=4.0.0, <4.3.6	3.8.39 4.3.6

Classification

Weakness

CWE-201 Insertion of Sensitive Information Into Sent Data

References

Sources

GitHub Advisory GHSA-r5xw-q988-826m

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.