{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-16398 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-16398 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-16398 is a medium-severity code injection vulnerability in n/a, published on 19 Sep 2019. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-16398 and fix it if it is affected.\n\nWhat it is: CVE-2019-16398 is a medium-severity code injection vulnerability in n/a, published on 19 Sep 2019. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2019-16398 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-16398/ (Markdown: https://insights.sbomify.com/CVE-2019-16398/index.md)","id":"CVE-2019-16398","markdown":"https://insights.sbomify.com/CVE-2019-16398/index.md","name":"CVE-2019-16398","record":{"aliases":["GHSA-qqf3-72cc-jc99"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Keeper K5 device","requires_auth":"none","summary":"Attackers can execute arbitrary code on Keeper K5 devices by inserting a malicious SD card, requiring physical access to the device.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"k5_firmware","vendor":"keeper"}],"cvss":{"score":6.8,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-345","name":"Insufficient Verification of Data Authenticity"}],"description":"On Keeper K5 20.1.0.25 and 20.1.0.63 devices, remote code execution can occur by inserting an SD card containing a file named zskj_script_run.sh that executes a reverse shell.","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":"Code injection in n/a","id":"CVE-2019-16398","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"Auth bypass in n/a","id":"CVE-2019-16399"},"packages":[],"prev":{"headline":"Use after free in n/a","id":"CVE-2019-16396"},"products":["n/a"],"published":"2019-09-19","related":[],"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 Keeper K5 devices by inserting a malicious SD card, requiring physical access to the device.","url":"https://insights.sbomify.com/CVE-2019-16398/"}