Strawberry
Approved changes feed: RSS · Atom
cpe:2.3:a:strawberryrocks:strawberry:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Strawberryrocks (c791d744-2492-5f7c-87fe-e4033dfc7632) |
|---|---|
| Product | Strawberry (4d3b71bb-5ae0-57f0-a441-1b4d074b49fd) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from gcve-enriched-dumps CVE data
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2024-47082 |
vulnerable | 2026-06-08 06:48:11.257393 |
Strawberry GraphQL Cross-Site Request Forgery (CSRF) vulnerability
MEDIUM (4.6)
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.
Published: 2024-09-25T17:48:24.065Z
Updated: 2024-09-25T18:05:24.810Z |
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.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.