Skip to main content

Over 150 LLM Providers · Over 5,300 Models The most extensible AI-powered pentesting platform. Open source. Star on GitHub

CVE-2023-31999

8.8 · HIGH
Published Jul 4, 2023 fastify CWE-352 EPSS 0.70% (51th pctl)

Overview

CVE-2023-31999 is a high-severity vulnerability affecting fastify oauth2. It was published on July 4, 2023 and has a CVSS 3.1 base score of 8.8 (HIGH).

This vulnerability has a CVSS 3.1 base score of 8.8, rated HIGH. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

Technical 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.

Remediation

Check the references section for vendor advisories and patches from fastify. Update oauth2 to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Affected Products

Vendor Product Versions Status
fastify oauth2 >= 0, < 7.2.0 Affected

Frequently Asked Questions

What is CVE-2023-31999?

CVE-2023-31999 is a high-severity vulnerability affecting fastify oauth2. It was published on July 4, 2023 and has a CVSS 3.1 base score of 8.8 (HIGH).

How severe is CVE-2023-31999?

This vulnerability has a CVSS 3.1 base score of 8.8, rated HIGH. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

How do I fix or remediate CVE-2023-31999?

Check the references section for vendor advisories and patches from fastify. Update oauth2 to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2023-31999?

CyberStrike's AI-powered security agents can automatically detect CVE-2023-31999 across your infrastructure using autonomous pentesting, DAST scanning, and HackBrowser. The platform continuously monitors for known vulnerabilities and provides actionable remediation guidance prioritized by real-world exploitability.