{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-14514 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-14514 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-14514 is a critical command injection vulnerability in n/a, published on 10 Feb 2020. 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-14514 and fix it if it is affected.\n\nWhat it is: CVE-2019-14514 is a critical command injection vulnerability in n/a, published on 10 Feb 2020. 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-14514 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-14514/ (Markdown: https://insights.sbomify.com/CVE-2019-14514/index.md)","id":"CVE-2019-14514","markdown":"https://insights.sbomify.com/CVE-2019-14514/index.md","name":"CVE-2019-14514","record":{"aliases":["GHSA-8wfj-rf7c-w472"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Android emulator","requires_auth":"none","summary":"Attackers can execute arbitrary commands with root privileges on the host by sending malicious input to the emulator's TCP port.","user_interaction":"not_required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"memu","vendor":"microvirt"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-78","name":"Improper Neutralization of Special Elements used in an OS Command"}],"description":"An issue was discovered in Microvirt MEmu all versions prior to 7.0.2. A guest Android operating system inside the MEmu emulator contains a /system/bin/systemd binary that is run with root privileges on startup (this is unrelated to Red Hat's systemd init program, and is a closed-source proprietary tool that seems to be developed by Microvirt). This program opens TCP port 21509, presumably to receive installation-related commands from the host OS. Because everything after the installer:uninstall command is concatenated directly into a system() call, it is possible to execute arbitrary commands by supplying shell metacharacters.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2020-02-06","github_poc":1,"max_poc_stars":3,"metasploit":0,"nuclei":0,"refs":[{"date":"2020-02-06T08:54:45Z","kind":"github_poc","ref":"https://github.com/seqred-s-a/cve-2019-14514","stars":3,"title":"Remote code execution in Microvirt MEmu"}],"tier":"poc_unverified"},"has_fix":null,"headline":"Command injection in n/a","id":"CVE-2019-14514","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"command_injection","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"Security feature bypass in n/a","id":"CVE-2019-14516"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2019-14513"},"products":["n/a"],"published":"2020-02-10","related":[{"cvss_score":9.3,"headline":"Memu Play 6.0.7 Privilege Escalation via Insecure File Permissions","id":"CVE-2019-25568","kev_date_added":null,"published":"2026-03-21"},{"cvss_score":7.8,"headline":"Privilege escalation in n/a","id":"CVE-2018-20621","kev_date_added":null,"published":"2019-03-13"}],"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)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Attackers can execute arbitrary commands with root privileges on the host by sending malicious input to the emulator's TCP port.","url":"https://insights.sbomify.com/CVE-2019-14514/"}