{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2019-11319 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-11319 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-11319 is a critical command injection vulnerability in n/a, published on 18 Apr 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-11319 and fix it if it is affected.\n\nWhat it is: CVE-2019-11319 is a critical command injection vulnerability in n/a, published on 18 Apr 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-11319 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-11319/ (Markdown: https://insights.sbomify.com/CVE-2019-11319/index.md)","id":"CVE-2019-11319","markdown":"https://insights.sbomify.com/CVE-2019-11319/index.md","name":"CVE-2019-11319","record":{"aliases":["GHSA-56rf-q4xp-9h6w"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Motorola CX2/M2","requires_auth":"none","summary":"Remote attackers can execute arbitrary code on Motorola CX2 and M2 devices via command injection in the firmware download function.","user_interaction":"not_required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"cx2_firmware","vendor":"motorola"},{"product":"m2_firmware","vendor":"motorola"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-78","name":"Improper Neutralization of Special Elements used in an OS Command"}],"description":"An issue was discovered in Motorola CX2 1.01 and M2 1.01. There is a command injection in the function downloadFirmware in hnap, which leads to remote code execution via shell metacharacters in a JSON value.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Command injection in n/a","id":"CVE-2019-11319","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":"Missing authorization in n/a","id":"CVE-2019-11320"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2019-11318"},"products":["n/a"],"published":"2019-04-18","related":[{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2020-21935","kev_date_added":null,"published":"2021-07-21"},{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2020-21937","kev_date_added":null,"published":"2021-07-21"},{"cvss_score":9.8,"headline":"Other in n/a","id":"CVE-2019-12297","kev_date_added":null,"published":"2019-05-23"},{"cvss_score":9.8,"headline":"Missing authorization in n/a","id":"CVE-2019-11320","kev_date_added":null,"published":"2019-04-18"},{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2019-11322","kev_date_added":null,"published":"2019-04-18"},{"cvss_score":7.5,"headline":"Information disclosure in n/a","id":"CVE-2020-21933","kev_date_added":null,"published":"2021-07-21"}],"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":"Remote attackers can execute arbitrary code on Motorola CX2 and M2 devices via command injection in the firmware download function.","url":"https://insights.sbomify.com/CVE-2019-11319/"}