{"vulnerability": "CVE-2024-47082", "sightings": [{"uuid": "e1ff41ff-1790-4781-bc23-812e5d55d7e4", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-47082", "type": "seen", "source": "https://t.me/cvedetector/6358", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-47082 - Strawberry GraphQL CSRF Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-47082 \nPublished : Sept. 25, 2024, 6:15 p.m. | 35\u00a0minutes ago \nDescription : 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. \nSeverity: 4.6 | MEDIUM \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"25 Sep 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-09-25T21:03:43.000000Z"}]}