{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2017-14180 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2017-14180 is a high-severity vulnerability in Canonical Ubuntu Linux, published on 2 Feb 2018. 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-2017-14180 and fix it if it is affected.\n\nWhat it is: CVE-2017-14180 is a high-severity vulnerability in Canonical Ubuntu Linux, published on 2 Feb 2018. 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-2017-14180 in the wild and no public exploit code.\n\nAffected product: Canonical Ubuntu Linux. 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-2017-14180/ (Markdown: https://insights.sbomify.com/CVE-2017-14180/index.md)","id":"CVE-2017-14180","markdown":"https://insights.sbomify.com/CVE-2017-14180/index.md","name":"CVE-2017-14180","record":{"aliases":["GHSA-q2pm-6838-p3jm","UBUNTU-CVE-2017-14180"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["privilege_escalation","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Ubuntu crash handler","requires_auth":"low_privilege","summary":"Local attackers can exploit Apport's PID namespace handling to create root-owned files, leading to privilege escalation or denial of service.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"canonical","cpe":[{"product":"apport","vendor":"apport_project"},{"product":"ubuntu_linux","vendor":"canonical"}],"cvss":{"score":7.8,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-400","name":"Uncontrolled Resource Consumption"}],"description":"Apport 2.13 through 2.20.7 does not properly handle crashes originating from a PID namespace allowing local users to create certain files as root which an attacker could leverage to perform a denial of service via resource exhaustion or possibly gain root privileges, a different vulnerability than CVE-2017-14179.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Privilege escalation in Apport","id":"CVE-2017-14180","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"canonical:ubuntu_linux","products":["canonical:ubuntu_linux"],"type":"privilege_escalation","year":"2017"},"n_packages":0,"n_references":4,"next":{"headline":"Null dereference in n/a","id":"CVE-2017-14181"},"packages":[],"prev":{"headline":"Privilege escalation in Apport","id":"CVE-2017-14179"},"products":["Apport"],"published":"2018-02-02","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":"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)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2025-11-03","vendors":["na/"]},"summary":"Local attackers can exploit Apport's PID namespace handling to create root-owned files, leading to privilege escalation or denial of service.","url":"https://insights.sbomify.com/CVE-2017-14180/"}