{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2014-3180 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2014-3180 is a critical vulnerability in Google Chrome Os, published on 6 Nov 2019. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2014-3180 and fix it if it is affected.\n\nWhat it is: CVE-2014-3180 is a critical vulnerability in Google Chrome Os, published on 6 Nov 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2014-3180 in the wild and no public exploit code.\n\nAffected product: Google Chrome Os. 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-2014-3180/ (Markdown: https://insights.sbomify.com/CVE-2014-3180/index.md)","id":"CVE-2014-3180","markdown":"https://insights.sbomify.com/CVE-2014-3180/index.md","name":"CVE-2014-3180","record":{"aliases":["DEBIAN-CVE-2014-3180","GHSA-97v5-ggfx-g9wc","UBUNTU-CVE-2014-3180"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Linux kernel","requires_auth":"none","summary":"An out-of-bounds read in the Linux kernel's restart_syscall could allow local attackers to read uninitialized memory, though the code path is disputed as unreachable.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Chrome","cpe":[{"product":"chrome_os","vendor":"google"},{"product":"linux_kernel","vendor":"linux"}],"cvss":{"score":9.1,"severity":"critical","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-125","name":"Out-of-bounds Read"}],"description":"In kernel/compat.c in the Linux kernel before 3.17, as used in Google Chrome OS and other products, there is a possible out-of-bounds read. restart_syscall uses uninitialized data when restarting compat_sys_nanosleep. NOTE: this is disputed because the code path is unreachable","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":"Information disclosure in kernel","id":"CVE-2014-3180","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"google:chrome_os","products":["google:chrome_os","linux:linux_kernel"],"type":"information_disclosure","year":"2014"},"n_packages":0,"n_references":2,"next":{"headline":"Memory corruption in n/a","id":"CVE-2014-3181"},"packages":[],"prev":{"headline":"Denial of service in n/a","id":"CVE-2014-3179"},"products":["kernel"],"published":"2019-11-06","related":[{"cvss_score":10,"headline":"Code injection in n/a","id":"CVE-2014-1708","kev_date_added":null,"published":"2014-03-16"},{"cvss_score":10,"headline":"Use after free in n/a","id":"CVE-2013-2833","kev_date_added":null,"published":"2013-04-16"},{"cvss_score":10,"headline":"Integer overflow in n/a","id":"CVE-2013-0915","kev_date_added":null,"published":"2013-03-18"},{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2012-2864","kev_date_added":null,"published":"2012-08-22"},{"cvss_score":10,"headline":"Other in n/a","id":"CVE-2012-4050","kev_date_added":null,"published":"2012-07-24"},{"cvss_score":10,"headline":"Other in n/a","id":"CVE-2011-2171","kev_date_added":null,"published":"2011-05-24"},{"cvss_score":10,"headline":"Other in n/a","id":"CVE-2011-1306","kev_date_added":null,"published":"2011-03-08"}],"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-08-06","vendors":["Linux"]},"summary":"An out-of-bounds read in the Linux kernel's restart_syscall could allow local attackers to read uninitialized memory, though the code path is disputed as unreachable.","url":"https://insights.sbomify.com/CVE-2014-3180/"}