CVE-2023-31999 @fastify/oauth2 vulnerable to Cross Site Request Forgery due to reused Oauth2 state
An attacker can bypass CSRF protections in the @fastify/oauth2 library due to a static state parameter, potentially allowing unauthorized actions.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- Available
What is CVE-2023-31999?
CVE-2023-31999 is a high-severity vulnerability in npm @fastify/oauth2, published on 4 Jul 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Official description
All versions of @fastify/oauth2 used a statically generated state parameter at startup time and were used across all requests for all users. The purpose of the Oauth2 state parameter is to prevent Cross-Site-Request-Forgery attacks. As such, it should be unique per user and should be connected to the user's session in some way that will allow the server to validate it. v7.2.0 changes the default behavior to store the state in a cookie with the http-only and same-site=lax attributes set. The state is now by default generated for every user. Note that this contains a breaking change in the checkStateFunction function, which now accepts the full Request object.
Weakness: CWE-352
Which versions are affected by CVE-2023-31999?
2 open source packages ship an affected version, including @fastify/oauth2. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
@fastify/oauth2 npm | All versions | 7.2.0 |
@fastify/oauth2 npm | All versions | 7.2.0 |
Products include Fastify Oauth2.
How do I fix CVE-2023-31999?
Upgrade @fastify/oauth2 to 7.2.0 or later.
Is CVE-2023-31999 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-31999 exists.
Sources
Also known as CVE-2023-35935, GHSA-g8x5-p9qc-cf95.