{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2020-14979 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-14979 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-14979 is a high-severity vulnerability in n/a, published on 11 Aug 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-14979 and fix it if it is affected.\n\nWhat it is: CVE-2020-14979 is a high-severity vulnerability in n/a, published on 11 Aug 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-14979 in the wild and no public exploit code.\n\nAffected product: n/a. 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-14979/ (Markdown: https://insights.sbomify.com/CVE-2020-14979/index.md)","id":"CVE-2020-14979","markdown":"https://insights.sbomify.com/CVE-2020-14979/index.md","name":"CVE-2020-14979","record":{"aliases":[],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["privilege_escalation","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Windows kernel driver","requires_auth":"low_privilege","summary":"Local attackers can exploit the WinRing0 driver to read and write arbitrary memory, gaining SYSTEM privileges on Windows systems.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"precision_x1","vendor":"evga"},{"product":"winring0","vendor":"winring0_project"}],"cvss":{"score":7.8,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"The WinRing0.sys and WinRing0x64.sys drivers 1.2.0 in EVGA Precision X1 through 1.0.6 allow local users, including low integrity processes, to read and write to arbitrary memory locations. This allows any user to gain NT AUTHORITY\\SYSTEM privileges by mapping \\Device\\PhysicalMemory into the calling process.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2026-01-17","github_poc":1,"max_poc_stars":6,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-01-17T19:39:43Z","kind":"github_poc","ref":"https://github.com/hexatriene/nuc-winring0-fix","stars":6,"title":"Permanent fix for Intel NUC WinRing0 vulnerable driver (CVE-2020-14979) reinstallation via Windows Update"}],"tier":"poc_unverified"},"has_fix":null,"headline":"Privilege escalation in n/a","id":"CVE-2020-14979","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2020"},"n_packages":0,"n_references":2,"next":{"headline":"Security feature bypass in n/a","id":"CVE-2020-14980"},"packages":[],"prev":{"headline":"Privilege escalation in n/a","id":"CVE-2020-14978"},"products":["n/a"],"published":"2020-08-11","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":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"Local attackers can exploit the WinRing0 driver to read and write arbitrary memory, gaining SYSTEM privileges on Windows systems.","url":"https://insights.sbomify.com/CVE-2020-14979/"}