{"answers":{"affected":"3 open source packages ship an affected version, including django-ses. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-33185 exists.","fix":"Upgrade django-ses to 3.5.0 or later.","what":"CVE-2023-33185 is a medium-severity vulnerability in django-ses, published on 26 May 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2023-33185 and fix it if it is affected.\n\nWhat it is: CVE-2023-33185 is a medium-severity vulnerability in django-ses, published on 26 May 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-33185 exists.\n\nAffected packages and fixed versions:\n- django-ses (PyPI): affected all versions; fixed in 3.5.0\n- django-ses (PyPI): affected all versions; fixed in 3.5.0\n- django-ses (PyPI): affected all versions; fixed in 3.5.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2023-33185/ (Markdown: https://insights.sbomify.com/CVE-2023-33185/index.md)","id":"CVE-2023-33185","markdown":"https://insights.sbomify.com/CVE-2023-33185/index.md","name":"CVE-2023-33185","record":{"aliases":["GHSA-qg36-9jxh-fj25","PYSEC-2023-82"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Django SES backend","requires_auth":"low_privilege","summary":"Attackers can bypass AWS signature verification in django-ses by specifying arbitrary public certificates, allowing unauthorized webhook requests.","user_interaction":"required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"django-ses","vendor":"django-ses_project"}],"cvss":{"score":4.6,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-347","name":"Improper Verification of Cryptographic Signature"}],"description":"Django-SES is a drop-in mail backend for Django. The django_ses library implements a mail backend for Django using AWS Simple Email Service. The library exports the `SESEventWebhookView class` intended to receive signed requests from AWS to handle email bounces, subscriptions, etc. These requests are signed by AWS and are verified by django_ses, however the verification of this signature was found to be flawed as it allowed users to specify arbitrary public certificates. This issue was patched in version 3.5.0.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Incorrect signature verification in django-ses","id":"CVE-2023-33185","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"security_feature_bypass","year":"2023"},"n_packages":3,"n_references":3,"next":{"headline":"Cross-site scripting vulnerability in Zulip Server development branch via topic tooltip","id":"CVE-2023-33186"},"packages":[{"ecosystem":"PyPI","fixed":["3.5.0"],"introduced":["0"],"last_affected":[],"package":"django-ses","purl":null,"source":"GHSA-qg36-9jxh-fj25"},{"ecosystem":"PyPI","fixed":["3.5.0"],"introduced":["0"],"last_affected":[],"package":"django-ses","purl":"pkg:pypi/django-ses","source":"GHSA-qg36-9jxh-fj25"},{"ecosystem":"PyPI","fixed":["3.5.0"],"introduced":["0"],"last_affected":[],"package":"django-ses","purl":"pkg:pypi/django-ses","source":"PYSEC-2023-82"}],"prev":{"headline":"Blind SSRF in the Nextcloud Mail app on avatar endpoint","id":"CVE-2023-33184"},"products":["django-ses"],"published":"2023-05-26","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-01-14","vendors":["django-ses"]},"summary":"Attackers can bypass AWS signature verification in django-ses by specifying arbitrary public certificates, allowing unauthorized webhook requests.","url":"https://insights.sbomify.com/CVE-2023-33185/"}