Prototype Pollution in lutils-merge

published 2019-06-13 7y ago modified 2021-08-16 5y ago

cvss: 7.3; 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

All versions of `lutils-merge` are vulnerable to Prototype Pollution. The merge() function fails to prevent user input to alter an Object's prototype, allowing attackers to modify override properties of all objects in the application. This may lead to Denial of Service or may be chained with other vulnerabilities leading to Remote Code Execution.

## Recommendation

The package is deprecated and no fixes are available. Consider using an alternative package.

Is GHSA-f7qw-5pvg-mmwp 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	7.3	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

Affected packages

ecosystem	package	affected	fixed in
npm	lutils-merge	<=0.2.6	no fix listed

Classification

Weakness

CWE-400 Uncontrolled Resource Consumption

References

Sources

GitHub Advisory GHSA-f7qw-5pvg-mmwp

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.