{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-9148 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-9148 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-9148 is a medium-severity vulnerability in n/a, published on 9 Jul 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2019-9148 and fix it if it is affected.\n\nWhat it is: CVE-2019-9148 is a medium-severity vulnerability in n/a, published on 9 Jul 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2019-9148 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-2019-9148/ (Markdown: https://insights.sbomify.com/CVE-2019-9148/index.md)","id":"CVE-2019-9148","markdown":"https://insights.sbomify.com/CVE-2019-9148/index.md","name":"CVE-2019-9148","record":{"aliases":["GHSA-7jh7-fp3w-72g5"],"analysis":{"component_type":"browser","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Browser extension","requires_auth":"none","summary":"Mailvelope accepts invalid PGP keys, allowing attackers to forge signatures and impersonate other users if victims import manipulated keys.","user_interaction":"required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"mailvelope","vendor":"mailvelope"}],"cvss":{"score":4.3,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-295","name":"Improper Certificate Validation"}],"description":"Mailvelope prior to 3.3.0 accepts or operates with invalid PGP public keys: Mailvelope allows importing keys that contain users without a valid self-certification. Keys that are obviously invalid are not rejected during import. An attacker that is able to get a victim to import a manipulated key could claim to have signed a message that originates from another person.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Other in n/a","id":"CVE-2019-9148","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2019"},"n_packages":0,"n_references":3,"next":{"headline":"Security feature bypass in n/a","id":"CVE-2019-9149"},"packages":[],"prev":{"headline":"Mailvelope prior to 3.1.0 is vulnerable to a clickjacking attack against the settings page.","id":"CVE-2019-9147"},"products":["n/a"],"published":"2019-07-09","related":[{"cvss_score":6.5,"headline":"Security feature bypass in n/a","id":"CVE-2019-9149","kev_date_added":null,"published":"2019-07-09"},{"cvss_score":5.3,"headline":"Security feature bypass in n/a","id":"CVE-2019-9150","kev_date_added":null,"published":"2019-07-09"},{"cvss_score":4.3,"headline":"Mailvelope prior to 3.1.0 is vulnerable to a clickjacking attack against the settings page.","id":"CVE-2019-9147","kev_date_added":null,"published":"2019-07-09"}],"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-04","vendors":["n/a"]},"summary":"Mailvelope accepts invalid PGP keys, allowing attackers to forge signatures and impersonate other users if victims import manipulated keys.","url":"https://insights.sbomify.com/CVE-2019-9148/"}