Incorrect default cookie name and recommendation
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?
For more information
If you have any questions or comments about this advisory:
- Reach out on the Psifi Solutions Discord in the
#psifi-supportchannel
Affected software
Click a technology to see all vulnerabilities affecting it.
| Platform | Package | Vulnerable versions | Fixed in |
|---|---|---|---|
| npm package | csrf-csrf | < 2.2.1 | 2.2.1 |
References
- Weakness (CWE)
-- Platform
- npm
- Package
csrf-csrf- Disclosed
- 10.10.2022
- Updated
- 11.10.2026 10:22
Sources and licenses
OSV / GitHub Advisory Database - GHSA-jjmg-x456-w976 - CC BY 4.0
Vulnerability history: csrf-csrf
All published vulnerabilities of this package (npm package), newest first. Shows whether this is a one-off slip or a package that needs watching.
This is the only known vulnerability of this package.
Know which vulnerabilities affect your application
With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.