{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2020-27352 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2020-27352 is a critical vulnerability in Canonical Ubuntu Linux, published on 21 Jun 2024. 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-2020-27352 and fix it if it is affected.\n\nWhat it is: CVE-2020-27352 is a critical vulnerability in Canonical Ubuntu Linux, published on 21 Jun 2024. 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-2020-27352 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-2020-27352/ (Markdown: https://insights.sbomify.com/CVE-2020-27352/index.md)","id":"CVE-2020-27352","markdown":"https://insights.sbomify.com/CVE-2020-27352/index.md","name":"CVE-2020-27352","record":{"aliases":["DEBIAN-CVE-2020-27352","GHSA-3hqj-7v65-62fj","UBUNTU-CVE-2020-27352","USN-4728-1"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"snapd container manager","requires_auth":"none","summary":"Attackers can gain unintended privileges in snapd-managed containers due to missing systemd delegation settings during unit reloads.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"canonical","cpe":[{"product":"snapd","vendor":"canonical"},{"product":"ubuntu_linux","vendor":"canonical"}],"cvss":{"score":9.3,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-269","name":"Improper Privilege Management"}],"description":"When generating the systemd service units for the docker snap (and other similar snaps), snapd does not specify Delegate=yes - as a result systemd will move processes from the containers created and managed by these snaps into the cgroup of the main daemon within the snap itself when reloading system units. This may grant additional privileges to a container within the snap that were not originally intended.","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 snapd","id":"CVE-2020-27352","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"canonical:ubuntu_linux","products":["canonical:ubuntu_linux"],"type":"privilege_escalation","year":"2020"},"n_packages":0,"n_references":3,"next":{"headline":"CVE ID was once reserved, but never used.","id":"CVE-2020-27353"},"packages":[],"prev":{"headline":"Various memory and file descriptor leaks in apt-python","id":"CVE-2020-27351"},"products":["snapd"],"published":"2024-06-21","related":[{"cvss_score":10,"headline":"Command injection in snapd","id":"CVE-2023-1523","kev_date_added":null,"published":"2023-09-01"},{"cvss_score":8.8,"headline":"Local privilege escalation via snapd socket","id":"CVE-2019-7304","kev_date_added":null,"published":"2019-04-23"},{"cvss_score":8.2,"headline":"snapd could be made to bypass intended access restrictions through snap content interfaces and layout paths","id":"CVE-2021-4120","kev_date_added":null,"published":"2022-02-17"},{"cvss_score":8.1,"headline":"CVE-2024-5138: snapd snapctl auth bypass","id":"CVE-2024-5138","kev_date_added":null,"published":"2024-05-31"},{"cvss_score":7.8,"headline":"snapd Race Condition vulnerability","id":"CVE-2022-3328","kev_date_added":null,"published":"2024-01-08"},{"cvss_score":7.8,"headline":"snapd could be made to escalate privileges and run programs as administrator","id":"CVE-2021-44730","kev_date_added":null,"published":"2022-02-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":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2024-08-04","vendors":["Canonical Ltd."]},"summary":"Attackers can gain unintended privileges in snapd-managed containers due to missing systemd delegation settings during unit reloads.","url":"https://insights.sbomify.com/CVE-2020-27352/"}