{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-12019 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2018-12019 is a high-severity vulnerability in n/a, published on 13 Jun 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-12019 and fix it if it is affected.\n\nWhat it is: CVE-2018-12019 is a high-severity vulnerability in n/a, published on 13 Jun 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-12019 in the wild and no public exploit code.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-12019/ (Markdown: https://insights.sbomify.com/CVE-2018-12019/index.md)","id":"CVE-2018-12019","markdown":"https://insights.sbomify.com/CVE-2018-12019/index.md","name":"CVE-2018-12019","record":{"aliases":["DEBIAN-CVE-2018-12019","GHSA-fc79-j7vw-6xjg","UBUNTU-CVE-2018-12019"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Enigmail email plugin","requires_auth":"none","summary":"Remote attackers can spoof arbitrary email signatures by exploiting flawed signature verification logic in Enigmail, undermining email authenticity.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"enigmail","vendor":"enigmail"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.0"},"cwes":[{"id":"CWE-347","name":"Improper Verification of Cryptographic Signature"}],"description":"The signature verification routine in Enigmail before 2.0.7 interprets user ids as status/control messages and does not correctly keep track of the status of multiple signatures, which allows remote attackers to spoof arbitrary email signatures via public keys containing crafted primary user ids.","ecosystems":[],"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":"Security feature bypass in n/a","id":"CVE-2018-12019","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2018"},"n_packages":0,"n_references":7,"next":{"headline":"Other in n/a","id":"CVE-2018-12020"},"packages":[],"prev":{"headline":"Go Ethereum LES protocol implementation vulnerable to Denial of Service","id":"CVE-2018-12018"},"products":["n/a"],"published":"2018-06-13","related":[{"cvss_score":7.8,"headline":"Denial of service in n/a","id":"CVE-2006-5877","kev_date_added":null,"published":"2007-02-23"},{"cvss_score":7.5,"headline":"Other in n/a","id":"CVE-2019-12269","kev_date_added":null,"published":"2019-05-21"},{"cvss_score":6.5,"headline":"Information disclosure in n/a","id":"CVE-2019-14664","kev_date_added":null,"published":"2019-08-05"},{"cvss_score":6.5,"headline":"Security feature bypass in n/a","id":"CVE-2018-15586","kev_date_added":null,"published":"2019-02-11"},{"cvss_score":5,"headline":"Security feature bypass in n/a","id":"CVE-2007-1264","kev_date_added":null,"published":"2007-03-06"},{"cvss_score":5,"headline":"Security feature bypass in n/a","id":"CVE-2005-3256","kev_date_added":null,"published":"2005-10-18"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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 spoof arbitrary email signatures by exploiting flawed signature verification logic in Enigmail, undermining email authenticity.","url":"https://insights.sbomify.com/CVE-2018-12019/"}