{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2016-9951 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2016-9951 is a medium-severity command injection vulnerability in n/a, published on 17 Dec 2016. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2016-9951 and fix it if it is affected.\n\nWhat it is: CVE-2016-9951 is a medium-severity command injection vulnerability in n/a, published on 17 Dec 2016. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2016-9951 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-2016-9951/ (Markdown: https://insights.sbomify.com/CVE-2016-9951/index.md)","id":"CVE-2016-9951","markdown":"https://insights.sbomify.com/CVE-2016-9951/index.md","name":"CVE-2016-9951","record":{"aliases":["GHSA-666r-6mfg-455c","UBUNTU-CVE-2016-9951"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Ubuntu Apport","requires_auth":"none","summary":"Attackers can execute arbitrary commands via malicious crash files if users click Relaunch, requiring a patch to hide the button for external files.","user_interaction":"required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"apport","vendor":"apport_project"}],"cvss":{"score":6.5,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H","version":"3.0"},"cwes":[{"id":"CWE-284","name":"Improper Access Control"}],"description":"An issue was discovered in Apport before 2.20.4. A malicious Apport crash file can contain a restart command in `RespawnCommand` or `ProcCmdline` fields. This command will be executed if a user clicks the Relaunch button on the Apport prompt from the malicious crash file. The fix is to only show the Relaunch button on Apport crash files generated by local systems. The Relaunch button will be hidden when crash files are opened directly in Apport-GTK.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2016-12-14","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2016-12-14","kind":"exploitdb","ref":"40937","stars":null,"title":"Apport 2.x (Ubuntu Desktop 12.10 \u003c 16.04) - Local Code Execution"}],"tier":"poc_unverified"},"has_fix":true,"headline":"Command injection in n/a","id":"CVE-2016-9951","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"command_injection","year":"2016"},"n_packages":0,"n_references":6,"next":{"headline":"Security feature bypass in n/a","id":"CVE-2016-9952"},"packages":[],"prev":{"headline":"Path traversal in n/a","id":"CVE-2016-9950"},"products":["n/a"],"published":"2016-12-17","related":[{"cvss_score":7.8,"headline":"Denial of service in Apport","id":"CVE-2022-28657","kev_date_added":null,"published":"2024-06-04"},{"cvss_score":7.8,"headline":"Apport treats the container PID as the global PID when /proc/\u003cglobal_pid\u003e/ is missing","id":"CVE-2018-6552","kev_date_added":null,"published":"2018-05-31"},{"cvss_score":7.8,"headline":"Privilege escalation in Apport","id":"CVE-2017-14177","kev_date_added":null,"published":"2018-02-02"},{"cvss_score":7.8,"headline":"Privilege escalation in Apport","id":"CVE-2017-14179","kev_date_added":null,"published":"2018-02-02"},{"cvss_score":7.8,"headline":"Privilege escalation in Apport","id":"CVE-2017-14180","kev_date_added":null,"published":"2018-02-02"},{"cvss_score":7.8,"headline":"Path traversal in n/a","id":"CVE-2017-10708","kev_date_added":null,"published":"2017-07-18"},{"cvss_score":7.8,"headline":"Code injection in n/a","id":"CVE-2016-9949","kev_date_added":null,"published":"2016-12-17"}],"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":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-06","vendors":["n/a"]},"summary":"Attackers can execute arbitrary commands via malicious crash files if users click Relaunch, requiring a patch to hide the button for external files.","url":"https://insights.sbomify.com/CVE-2016-9951/"}