{"answers":{"affected":"3 open source packages ship an affected version, including django-anymail. It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-1000089 in the wild and no public exploit code.","fix":"Upgrade django-anymail to 1.4 or later.","what":"CVE-2018-1000089 is a high-severity vulnerability in n/a, published on 13 Mar 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-1000089 and fix it if it is affected.\n\nWhat it is: CVE-2018-1000089 is a high-severity vulnerability in n/a, published on 13 Mar 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-1000089 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- django-anymail (PyPI): affected from 0.2; fixed in 1.4\n- django-anymail (PyPI): affected from 0.2; fixed in 1.4\n- django-anymail (PyPI): affected from 0.2; fixed in 1.4\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-1000089/ (Markdown: https://insights.sbomify.com/CVE-2018-1000089/index.md)","id":"CVE-2018-1000089","markdown":"https://insights.sbomify.com/CVE-2018-1000089/index.md","name":"CVE-2018-1000089","record":{"aliases":["DEBIAN-CVE-2018-1000089","GHSA-qh9x-mc42-vg4g","PYSEC-2018-46"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":true,"product_category":"Django email library","requires_auth":"none","summary":"Attackers with access to error logs can discover webhook secrets to fabricate email tracking events in Django applications using Anymail.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"django-anymail","vendor":"django-anymail_project"}],"cvss":{"score":7.4,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.0"},"cwes":[{"id":"CWE-532","name":"Insertion of Sensitive Information into Log File"}],"description":"Anymail django-anymail version version 0.2 through 1.3 contains a CWE-532, CWE-209 vulnerability in WEBHOOK_AUTHORIZATION setting value that can result in An attacker with access to error logs could fabricate email tracking events. This attack appear to be exploitable via If you have exposed your Django error reports, an attacker could discover your ANYMAIL_WEBHOOK setting and use this to post fabricated or malicious Anymail tracking/inbound events to your app. This vulnerability appears to have been fixed in v1.4.","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 Includes Sensitive Information in Log Files","id":"CVE-2018-1000089","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"information_disclosure","year":"2018"},"n_packages":3,"n_references":2,"next":{"headline":"XML external entity in n/a","id":"CVE-2018-1000090"},"packages":[{"ecosystem":"PyPI","fixed":["1.4"],"introduced":["0.2"],"last_affected":[],"package":"django-anymail","purl":null,"source":"GHSA-qh9x-mc42-vg4g"},{"ecosystem":"PyPI","fixed":["1.4"],"introduced":["0.2"],"last_affected":[],"package":"django-anymail","purl":"pkg:pypi/django-anymail","source":"GHSA-qh9x-mc42-vg4g"},{"ecosystem":"PyPI","fixed":["1.4"],"introduced":["0.2"],"last_affected":[],"package":"django-anymail","purl":"pkg:pypi/django-anymail","source":"PYSEC-2018-46"}],"prev":{"headline":"Doorkeeper is vulnerable to stored XSS and code execution","id":"CVE-2018-1000088"},"products":["n/a"],"published":"2018-03-13","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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Attackers with access to error logs can discover webhook secrets to fabricate email tracking events in Django applications using Anymail.","url":"https://insights.sbomify.com/CVE-2018-1000089/"}