UnratednpmAmendedPublished
Incorrect default cookie name and recommendation
GHSA-jjmg-x456-w976
- Affected
- npm csrf-csrf < 2.2.1
- Fixed in
- 2.2.1· Vendor fix available
- Issue
- Impact What kind of vulnerability is it? Who is impacted? The default cookie name (and documentation recommendation) was prefixed with Host instead of Host-. The point of this prefix is for additional security, to ensure that, when no domain option is provided in the cookie options, we can guarantee the cookie came from the correct domain. Patches Has the problem been patched? What versions should users upgrade to? Yes, the problem is patched from version 2.2.1, this will not be back ported, but you can use the workaround described below. Workarounds Is there a way for users to fix or remediate the vulnerability without upgrading? You can work around this by providing a custom cookieName as part of the options, which is correctly prefixed with Host-. References Are there any links users can visit to find out more? https://cheatsheetseries.owasp.org/cheatsheets/Cross-SiteRequestForgeryPreventionCheatSheet.html#cookie-with-host-prefix For more information If you have any questions or…
Recommended action: Upgrade to 2.2.1 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.