CVE-2024-47082

References

• Strawberry upgrade guide
• Multipart Upload Security Implications

Credits

• Thomas Grainger
• Arthur Bayr
• Jonathan Ehwald

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

A victim's authenticated browser session is used to submit forged requests to an application that cannot distinguish them from legitimate ones. Typical impact: state-changing actions performed as the victim without their consent.

CVE-2024-47082 has a CVSS score of 4.6 (Medium). The vector is network-reachable, low privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.243.0); upgrading removes the vulnerable code path.

Kodem intelligence

Version v0.243.0 is the first strawberry-graphql including a patch. Check out our documentation for additional details and upgrade instructions.

1. What is CVE-2024-47082? CVE-2024-47082 is a medium-severity cross-site request forgery (CSRF) vulnerability in strawberry-graphql (pip), affecting versions < 0.243.0. It is fixed in 0.243.0. A victim's authenticated browser session is used to submit forged requests to an application that cannot distinguish them from legitimate ones.
2. How severe is CVE-2024-47082? CVE-2024-47082 has a CVSS score of 4.6 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of strawberry-graphql are affected by CVE-2024-47082? strawberry-graphql (pip) versions < 0.243.0 is affected.
4. Is there a fix for CVE-2024-47082? Yes. CVE-2024-47082 is fixed in 0.243.0. Upgrade to this version or later.
5. Is CVE-2024-47082 exploitable, and should I be worried? Whether CVE-2024-47082 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2024-47082 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2024-47082? Upgrade strawberry-graphql to 0.243.0 or later.