Staging Environment: Content and features may be unstable or change without notice.

Advisory Severity Curation

CVE-2024-47082

Progress 0 / 0

Advisory Summaries

github_osv/GHSA-79gp-q4wv-33fr

Cross-Site Request Forgery (CSRF) in strawberry-graphql ### Impact Multipart file upload support as defined in the GraphQL multipart request specification https://github.com/jaydenseric/graphql-multipart-request-spec 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. ### Patches Version `v0.243.0` is the first `strawberry-graphql` including a patch. Check out our documentation https://strawberry.rocks/docs/breaking-changes/0.243.0 for additional details and upgrade instructions. ### References - Strawberry upgrade guide https://strawberry.rocks/docs/breaking-changes/0.243.0 - Multipart Upload Security Implications https://github.com/jaydenseric/graphql-multipart-request-spec/blob/master/readme.md#security ### Credits - Thomas Grainger https://github.com/graingert - Arthur Bayr https://github.com/speedy1991 - Jonathan Ehwald https://github.com/DoctorJohn

gitlab/pypi/strawberry-graphql/CVE-2024-47082

Cross-Site Request Forgery (CSRF) in strawberry-graphql Multipart file upload support as defined in the GraphQL multipart request specification https://github.com/jaydenseric/graphql-multipart-request-spec 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.

pypa/strawberry-graphql/PYSEC-2024-171

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.

pysec/PYSEC-2024-171

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.