{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-11480 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-11480 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-11480 is a high-severity vulnerability in Canonical pc-kernel, published on 14 Apr 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-2019-11480 and fix it if it is affected.\n\nWhat it is: CVE-2019-11480 is a high-severity vulnerability in Canonical pc-kernel, published on 14 Apr 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-2019-11480 in the wild and no public exploit code.\n\nAffected product: Canonical pc-kernel. 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-2019-11480/ (Markdown: https://insights.sbomify.com/CVE-2019-11480/index.md)","id":"CVE-2019-11480","markdown":"https://insights.sbomify.com/CVE-2019-11480/index.md","name":"CVE-2019-11480","record":{"aliases":["GHSA-vj59-q97j-4hgq"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Ubuntu kernel snap","requires_auth":"high_privilege","summary":"Attackers can inject malicious packages into the Ubuntu kernel snap build process via MITM due to insecure apt options, compromising the resulting kernel image.","user_interaction":"not_required","vuln_class":"supply_chain"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"canonical","cpe":[{"product":"c-kernel","vendor":"canonical"}],"cvss":{"score":8.4,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-345","name":"Insufficient Verification of Data Authenticity"},{"id":"CWE-353","name":"Missing Support for Integrity Check"}],"description":"The pc-kernel snap build process hardcoded the --allow-insecure-repositories and --allow-unauthenticated apt options when creating the build chroot environment. This could allow an attacker who is able to perform a MITM attack between the build environment and the Ubuntu archive to install a malicious package within the build chroot. This issue affects pc-kernel versions prior to and including 2019-07-16","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Ubuntu kernel snap build process could use unauthenticated sources","id":"CVE-2019-11480","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"supply_chain","year":"2019"},"n_packages":0,"n_references":2,"next":{"headline":"Apport reads arbitrary files if ~/.config/apport/settings is a symlink","id":"CVE-2019-11481"},"packages":[],"prev":{"headline":"Denial of service in Linux kernel","id":"CVE-2019-11479"},"products":["pc-kernel"],"published":"2020-04-14","related":[],"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-16","vendors":["Canonical"]},"summary":"Attackers can inject malicious packages into the Ubuntu kernel snap build process via MITM due to insecure apt options, compromising the resulting kernel image.","url":"https://insights.sbomify.com/CVE-2019-11480/"}