Know every vulnerabilitybefore it knows you.
DevGuard continuously monitors your dependencies and alerts you when CVEs like this one affect your stack — with real-time threat intelligence built for developers.
GHSA-jjmg-x456-w976
No affected components available
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-Site_Request_Forgery_Prevention_Cheat_Sheet.html#cookie-with-__host-prefix
For more information
If you have any questions or comments about this advisory:
- Reach out on the Psifi Solutions Discord in the
#psifi-supportchannel
Measures severity based on intrinsic characteristics of the vulnerability, independent of environment.
No exploitation activity has been observed at this time. Continue routine monitoring.
Probability that this vulnerability will be exploited in the wild within the next 30 days.
We did not find any exploit available. Neither in GitHub repositories nor in the Exploit-Database.
Continuously monitor your dependencies and get alerted when vulnerabilities like this one affect your stack.
Checkout DevGuard