{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-6552 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2018-6552 is a high-severity vulnerability in Apport, published on 31 May 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-2018-6552 and fix it if it is affected.\n\nWhat it is: CVE-2018-6552 is a high-severity vulnerability in Apport, published on 31 May 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-2018-6552 in the wild and no public exploit code.\n\nAffected product: Apport. 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-2018-6552/ (Markdown: https://insights.sbomify.com/CVE-2018-6552/index.md)","id":"CVE-2018-6552","markdown":"https://insights.sbomify.com/CVE-2018-6552/index.md","name":"CVE-2018-6552","record":{"aliases":["GHSA-4pgc-f487-53cr","UBUNTU-CVE-2018-6552","USN-3664-1","USN-3664-2"],"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 Apport","requires_auth":"low_privilege","summary":"Local attackers can exploit Apport's PID namespace handling to create root-owned files, leading to privilege escalation or container escape.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"canonical","cpe":[{"product":"apport","vendor":"apport_project"}],"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":[],"description":"Apport 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, possibly gain root privileges, or escape from containers. The is_same_ns() function returns True when /proc/\u003cglobal pid\u003e/ does not exist in order to indicate that the crash should be handled in the global namespace rather than inside of a container. However, the portion of the data/apport code that decides whether or not to forward a crash to a container does not always replace sys.argv[1] with the value stored in the host_pid variable when /proc/\u003cglobal pid\u003e/ does not exist which results in the container pid being used in the global namespace. This flaw affects versions 2.20.8-0ubuntu4 through 2.20.9-0ubuntu7, 2.20.7-0ubuntu3.7, 2.20.7-0ubuntu3.8, 2.20.1-0ubuntu2.15 through 2.20.1-0ubuntu2.17, and 2.14.1-0ubuntu3.28.","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":"Apport treats the container PID as the global PID when /proc/\u003cglobal_pid\u003e/ is missing","id":"CVE-2018-6552","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2018"},"n_packages":0,"n_references":2,"next":{"headline":"AppArmor cupsd Sandbox Bypass Due to Use of Hard Links","id":"CVE-2018-6553"},"packages":[],"prev":{"headline":"Integer overflow in n/a","id":"CVE-2018-6551"},"products":["Apport"],"published":"2018-05-31","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":"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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-17","vendors":["n/a"]},"summary":"Local attackers can exploit Apport's PID namespace handling to create root-owned files, leading to privilege escalation or container escape.","url":"https://insights.sbomify.com/CVE-2018-6552/"}