Skip to content
Fencer Intel
high 8.6

GHSA-mxfr-qhmh-pcx4 json

Prototype pollution in set-cookie-parser via Set-Cookie name/value attribute override

published 15d ago modified 15d ago

Unreviewed: the maintainers' own advisory

Published by the maintainers on their GitHub repository nfriedly/set-cookie-parser. GitHub has not reviewed it into the GitHub Advisory Database and no CVE record has reached us yet, so everything here comes from the maintainers alone. Read the full advisory on GitHub.

cvss
8.6
version 3.1, the maintainers
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

Summary

Security advisory published by the maintainers of nfriedly/set-cookie-parser for set-cookie-parser: the maintainers' own advisory, not a reviewed GitHub Advisory Database entry. The full advisory is on GitHub.

Patch / fix

  • npm set-cookie-parser 2.7.3, 3.2.0

Is GHSA-mxfr-qhmh-pcx4 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
the maintainers 3.1 8.6 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:L

Affected packages

ecosystem package affected fixed in
npm set-cookie-parser
<=2.7.2, 3.0.0-3.1.4
2.7.3
3.2.0

Classification

Weakness
  • CWE-1321 Improperly Controlled Modification of Object Prototype Attributes

References

Sources

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.

The maintainers of nfriedly/set-cookie-parser published their own advisory on GitHub. Its facts and headline are shown here; the description stays on GitHub.