Prototype Pollution in mixme

published 2021-09-20 5y ago modified 2021-09-16 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

### Impact When copying properties from a source object to a target object, the target object can gain access to certain properties of the source object and modify their content.

### Patches The problem was patch with a more agressive discovery of secured properties to filter out.

Patch / fix

fixed in 1 links 1

npm mixme 0.5.2

github.com/adaltas/node-mixme@db70fe9 commit

Is GHSA-84p7-fh9c-6g8h 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	mixme	<0.5.2	0.5.2

Classification

Weakness

CWE-1321 Improperly Controlled Modification of Object Prototype Attributes

References

Sources

GitHub Advisory GHSA-84p7-fh9c-6g8h

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.