CSRF in Strawberry-Graphql Strawberry
CVE-2024-47082
- CVSS v3
- 4.6 Medium
- Public exploits
- None known
- EPSS
- 0.002 · 15.7th percentile
- Published
- 2024-09-25
What to do
- Fixed in
0.243.0- Affected
- 2 affected products
Strawberry GraphQL is a library for creating GraphQL APIs. Prior to version 0.243.0, multipart file upload support as defined in the GraphQL multipart request specification was enabled by default in all Strawberry HTTP view integrations. This made all Strawberry HTTP view integrations vulnerable to cross-site request forgery (CSRF) attacks if users did not explicitly enable CSRF preventing security mechanism for their servers. Additionally, the Django HTTP view integration, in particular, had an exemption for Django's built-in CSRF protection (i.e., the `CsrfViewMiddleware` middleware) by default. In affect, all Strawberry integrations were vulnerable to CSRF attacks by default. Version `v0.243.0` is the first `strawberry-graphql` including a patch.
Vulnerability class: CSRF (Cross-Site Request Forgery)
Published · last modified .
CVSS v3 metric
CVSS v3 base score 4.6 (Medium). Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:L.
- Attack Vector
- Network
AV:N - Attack Complexity
- Low
AC:L - Privileges Required
- Low
PR:L - User Interaction
- Required
UI:R - Scope
- Unchanged
S:U - Confidentiality
- None
C:N - Integrity
- Low
I:L - Availability
- Low
A:L
EPSS exploit prediction
EPSS 0.002, 15.7th percentile (last changed ); unchanged over 30 days. About EPSS.
Affected products
- Strawberry-Graphql Strawberry — versions < 0.243.0
- Strawberryrocks Strawberry
Weakness classification (CWE)
Public exploits and proof-of-concept code
Also mentioned in 1 other repository (cellsignal/kedro-graphql). These reference the CVE in a list, notes or a scanner and are not exploit code for it.