{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-13513 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-13513 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-13513 is a high-severity vulnerability in NZXT, published on 18 Dec 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-13513 and fix it if it is affected.\n\nWhat it is: CVE-2020-13513 is a high-severity vulnerability in NZXT, published on 18 Dec 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-13513 in the wild and no public exploit code.\n\nAffected product: NZXT. 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-13513/ (Markdown: https://insights.sbomify.com/CVE-2020-13513/index.md)","id":"CVE-2020-13513","markdown":"https://insights.sbomify.com/CVE-2020-13513/index.md","name":"CVE-2020-13513","record":{"aliases":["GHSA-cxgj-mmp6-3j54"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"NZXT CAM","requires_auth":"low_privilege","summary":"A local attacker can exploit a vulnerable driver in NZXT CAM to gain elevated privileges via a crafted I/O request packet.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"talos","cpe":[{"product":"cam","vendor":"nzxt"}],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"},{"id":"CWE-269","name":"Improper Privilege Management"}],"description":"A privilege escalation vulnerability exists in the WinRing0x64 Driver Privileged I/O Write IRPs functionality of NZXT CAM 4.8.0. A specially crafted I/O request packet (IRP) can cause increased privileges. Using the IRP 0x9c40a0dc gives a low privilege user direct access to the OUT instruction that is completely unrestrained at an elevated privilege level. An attacker can send a malicious IRP to trigger this vulnerability.","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":"Privilege escalation in NZXT","id":"CVE-2020-13513","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2020"},"n_packages":0,"n_references":1,"next":{"headline":"Privilege escalation in NZXT","id":"CVE-2020-13514"},"packages":[],"prev":{"headline":"Privilege escalation in NZXT","id":"CVE-2020-13512"},"products":["NZXT"],"published":"2020-12-18","related":[{"cvss_score":8.8,"headline":"Privilege escalation in NZXT","id":"CVE-2020-13512","kev_date_added":null,"published":"2020-12-18"},{"cvss_score":8.8,"headline":"Privilege escalation in NZXT","id":"CVE-2020-13514","kev_date_added":null,"published":"2020-12-18"},{"cvss_score":8.8,"headline":"Privilege escalation in NZXT","id":"CVE-2020-13515","kev_date_added":null,"published":"2020-12-18"},{"cvss_score":8.8,"headline":"Privilege escalation in NZXT\"","id":"CVE-2020-13519","kev_date_added":null,"published":"2020-12-18"},{"cvss_score":6.5,"headline":"Information disclosure in NZXT","id":"CVE-2020-13509","kev_date_added":null,"published":"2020-12-17"},{"cvss_score":6.5,"headline":"Privilege escalation in NZXT","id":"CVE-2020-13510","kev_date_added":null,"published":"2020-12-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-08-04","vendors":["n/a"]},"summary":"A local attacker can exploit a vulnerable driver in NZXT CAM to gain elevated privileges via a crafted I/O request packet.","url":"https://insights.sbomify.com/CVE-2020-13513/"}