Approved changes feed: RSS · Atom
cpe:2.3:a:fastify:oauth2:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Fastify (51747187-798b-5030-972d-b19db43759b4) |
|---|---|
| Product | Oauth2 (7003ad99-b27e-5850-a3b2-27247935c583) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from purl2cpe mapping |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/fastify/fastify-oauth2 |
purl2cpe | 2026-06-01 10:16:32.868118 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2023-31999 |
vulnerable | 2026-06-03 14:51:57.151982 |
Details available
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.
Published: 2023-07-04T16:29:20.281Z
Updated: 2024-11-26T18:47:25.202Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.