{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-15310 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-15310 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-15310 is a critical command injection vulnerability in n/a, published on 1 Jul 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-15310 and fix it if it is affected.\n\nWhat it is: CVE-2019-15310 is a critical command injection vulnerability in n/a, published on 1 Jul 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-15310 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-15310/ (Markdown: https://insights.sbomify.com/CVE-2019-15310/index.md)","id":"CVE-2019-15310","markdown":"https://insights.sbomify.com/CVE-2019-15310/index.md","name":"CVE-2019-15310","record":{"aliases":["GHSA-xmvm-x7m2-gg4f"],"analysis":{"component_type":"iot_embedded","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"Linkplay IoT firmware","requires_auth":"none","summary":"Attackers can execute arbitrary code on IoT devices via OS command injection in firmware updates, potentially compromising the entire AWS infrastructure.","user_interaction":"not_required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"linkplay","vendor":"linkplay"}],"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"},{"id":"CWE-639","name":"Authorization Bypass Through User-Controlled Key"}],"description":"An issue was discovered on various devices via the Linkplay firmware. There is WAN remote code execution without user interaction. An attacker could retrieve the AWS key from the firmware and obtain full control over Linkplay's AWS estate, including S3 buckets containing device firmware. When combined with an OS command injection vulnerability within the XML Parsing logic of the firmware update process, an attacker would be able to gain code execution on any device that attempted to update. Note that by default all devices tested had automatic updates enabled.","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-15310","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"command_injection","year":"2019"},"n_packages":0,"n_references":3,"next":{"headline":"Command injection in n/a","id":"CVE-2019-15311"},"packages":[],"prev":{"headline":"Hardcoded credentials in n/a","id":"CVE-2019-15304"},"products":["n/a"],"published":"2020-07-01","related":[{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2019-15311","kev_date_added":null,"published":"2020-07-01"},{"cvss_score":8.8,"headline":"Server-side request forgery in n/a","id":"CVE-2019-15312","kev_date_added":null,"published":"2020-07-01"}],"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":"Attackers can execute arbitrary code on IoT devices via OS command injection in firmware updates, potentially compromising the entire AWS infrastructure.","url":"https://insights.sbomify.com/CVE-2019-15310/"}