{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-9149 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-9149 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-9149 is a medium-severity vulnerability in n/a, published on 9 Jul 2019. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-9149 and fix it if it is affected.\n\nWhat it is: CVE-2019-9149 is a medium-severity vulnerability in n/a, published on 9 Jul 2019. 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-2019-9149 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-9149/ (Markdown: https://insights.sbomify.com/CVE-2019-9149/index.md)","id":"CVE-2019-9149","markdown":"https://insights.sbomify.com/CVE-2019-9149/index.md","name":"CVE-2019-9149","record":{"aliases":["GHSA-hjgw-9xvw-334r"],"analysis":{"component_type":"browser","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Browser extension","requires_auth":"none","summary":"Attackers can bypass user interaction to sign, encrypt, or decrypt messages via the client-API if the private key password is cached.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"mailvelope","vendor":"mailvelope"}],"cvss":{"score":6.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"},{"id":"CWE-347","name":"Improper Verification of Cryptographic Signature"}],"description":"Mailvelope prior to 3.3.0 allows private key operations without user interaction via its client-API. By modifying an URL parameter in Mailvelope, an attacker is able to sign (and encrypt) arbitrary messages with Mailvelope, assuming the private key password is cached. A second vulnerability allows an attacker to decrypt an arbitrary message when the GnuPG backend is used in Mailvelope.","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":"Security feature bypass in n/a","id":"CVE-2019-9149","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2019"},"n_packages":0,"n_references":3,"next":{"headline":"Security feature bypass in n/a","id":"CVE-2019-9150"},"packages":[],"prev":{"headline":"Other in n/a","id":"CVE-2019-9148"},"products":["n/a"],"published":"2019-07-09","related":[{"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"},{"cvss_score":4.3,"headline":"Other in n/a","id":"CVE-2019-9148","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":"Attackers can bypass user interaction to sign, encrypt, or decrypt messages via the client-API if the private key password is cached.","url":"https://insights.sbomify.com/CVE-2019-9149/"}