{"answers":{"affected":"3 open source packages ship an affected version, including django-anymail. It affects 2 products.","exploited":"There is no known exploitation of CVE-2018-6596 in the wild and no public exploit code.","fix":"Upgrade django-anymail to 1.2.1 or later.","what":"CVE-2018-6596 is a critical vulnerability in Debian Debian Linux, published on 3 Feb 2018. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-6596 and fix it if it is affected.\n\nWhat it is: CVE-2018-6596 is a critical vulnerability in Debian Debian Linux, published on 3 Feb 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2018-6596 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- django-anymail (PyPI): affected all versions; fixed in 1.2.1\n- django-anymail (PyPI): affected all versions; fixed in 1.2.1\n- django-anymail (PyPI): affected all versions; fixed in 1.2.1\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-2018-6596/ (Markdown: https://insights.sbomify.com/CVE-2018-6596/index.md)","id":"CVE-2018-6596","markdown":"https://insights.sbomify.com/CVE-2018-6596/index.md","name":"CVE-2018-6596","record":{"aliases":["DEBIAN-CVE-2018-6596","DSA-4107-1","GHSA-hxf9-7h4c-f5jv","PYSEC-2018-7"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_modify","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Django email library","requires_auth":"none","summary":"Remote attackers can exploit a timing attack to bypass webhook authorization and post arbitrary email tracking events in Anymail.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"debian_linux","vendor":"debian"},{"product":"django-anymail","vendor":"django-anymail_project"}],"cvss":{"score":9.1,"severity":"critical","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"webhooks/base.py in Anymail (aka django-anymail) before 1.2.1 is prone to a timing attack vulnerability on the WEBHOOK_AUTHORIZATION secret, which allows remote attackers to post arbitrary e-mail tracking events.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Django-Anymail prone to a timing attack","id":"CVE-2018-6596","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":"debian:debian_linux","products":["debian:debian_linux"],"type":"information_disclosure","year":"2018"},"n_packages":3,"n_references":6,"next":{"headline":"Privilege escalation in n/a","id":"CVE-2018-6597"},"packages":[{"ecosystem":"PyPI","fixed":["1.2.1"],"introduced":["0"],"last_affected":[],"package":"django-anymail","purl":null,"source":"GHSA-hxf9-7h4c-f5jv"},{"ecosystem":"PyPI","fixed":["1.2.1"],"introduced":["0"],"last_affected":[],"package":"django-anymail","purl":"pkg:pypi/django-anymail","source":"GHSA-hxf9-7h4c-f5jv"},{"ecosystem":"PyPI","fixed":["1.2.1"],"introduced":["0"],"last_affected":[],"package":"django-anymail","purl":"pkg:pypi/django-anymail","source":"PYSEC-2018-7"}],"prev":{"headline":"Pycrypto generates weak key parameters","id":"CVE-2018-6594"},"products":["n/a"],"published":"2018-02-03","related":[{"cvss_score":10,"headline":"ProFTPD Improper Access Control","id":"CVE-2015-3306","kev_date_added":"2026-10-08","published":"2015-05-18"},{"cvss_score":9.9,"headline":"RoundCube Webmail Deserialization of Untrusted Data","id":"CVE-2025-49113","kev_date_added":"2026-02-20","published":"2025-06-02"},{"cvss_score":9.8,"headline":"GNU InetUtils Argument Injection","id":"CVE-2026-24061","kev_date_added":"2026-01-26","published":"2026-01-21"},{"cvss_score":9.8,"headline":"Linux Kernel Improper Check for Unusual or Exceptional Conditions","id":"CVE-2025-39682","kev_date_added":"2026-09-18","published":"2025-09-05"},{"cvss_score":9.8,"headline":"Mozilla Firefox Use-After-Free","id":"CVE-2024-9680","kev_date_added":"2024-10-15","published":"2024-10-09"},{"cvss_score":9.8,"headline":"RARLAB UnRAR Directory Traversal","id":"CVE-2022-30333","kev_date_added":"2022-08-09","published":"2022-05-09"},{"cvss_score":9.8,"headline":"Roundcube Webmail SQL Injection","id":"CVE-2021-44026","kev_date_added":"2023-06-22","published":"2021-11-19"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Remote attackers can exploit a timing attack to bypass webhook authorization and post arbitrary email tracking events in Anymail.","url":"https://insights.sbomify.com/CVE-2018-6596/"}