{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2020-11933 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-11933 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-11933 is a high-severity vulnerability in Canonical Ubuntu Linux, published on 29 Jul 2020. 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-11933 and fix it if it is affected.\n\nWhat it is: CVE-2020-11933 is a high-severity vulnerability in Canonical Ubuntu Linux, published on 29 Jul 2020. 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-11933 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-11933/ (Markdown: https://insights.sbomify.com/CVE-2020-11933/index.md)","id":"CVE-2020-11933","markdown":"https://insights.sbomify.com/CVE-2020-11933/index.md","name":"CVE-2020-11933","record":{"aliases":["GHSA-v343-8p34-76p3"],"analysis":{"component_type":"operating_system","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Ubuntu Core OS","requires_auth":"none","summary":"A physical attacker can bypass full disk encryption on Ubuntu Core devices by exploiting unrestricted cloud-init execution during boot via external media.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"canonical","cpe":[{"product":"snapd","vendor":"canonical"},{"product":"ubuntu_linux","vendor":"canonical"}],"cvss":{"score":7.3,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-264","name":null}],"description":"cloud-init as managed by snapd on Ubuntu Core 16 and Ubuntu Core 18 devices was run without restrictions on every boot, which a physical attacker could exploit by crafting cloud-init user-data/meta-data via external media to perform arbitrary changes on the device to bypass intended security mechanisms such as full disk encryption. This issue did not affect traditional Ubuntu systems. Fixed in snapd version 2.45.2, revision 8539 and core version 2.45.2, revision 9659.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"local snapd exploit through cloud-init","id":"CVE-2020-11933","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"canonical:ubuntu_linux","products":["canonical:ubuntu_linux"],"type":"security_feature_bypass","year":"2020"},"n_packages":0,"n_references":2,"next":{"headline":"Sandbox escape vulnerability via snapctl user-open (xdg-open)","id":"CVE-2020-11934"},"packages":[],"prev":{"headline":"Subiquity server installer logged LUKS full disk encryption password","id":"CVE-2020-11932"},"products":["core","snapd"],"published":"2020-07-29","related":[{"cvss_score":10,"headline":"Command injection in snapd","id":"CVE-2023-1523","kev_date_added":null,"published":"2023-09-01"},{"cvss_score":9.3,"headline":"Privilege escalation in snapd","id":"CVE-2020-27352","kev_date_added":null,"published":"2024-06-21"},{"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-17","vendors":["Canonical"]},"summary":"A physical attacker can bypass full disk encryption on Ubuntu Core devices by exploiting unrestricted cloud-init execution during boot via external media.","url":"https://insights.sbomify.com/CVE-2020-11933/"}