{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-15303 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-15303 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-15303 is a high-severity memory corruption vulnerability in n/a, published on 16 Oct 2017. 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-2017-15303 and fix it if it is affected.\n\nWhat it is: CVE-2017-15303 is a high-severity memory corruption vulnerability in n/a, published on 16 Oct 2017. 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-2017-15303 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-2017-15303/ (Markdown: https://insights.sbomify.com/CVE-2017-15303/index.md)","id":"CVE-2017-15303","markdown":"https://insights.sbomify.com/CVE-2017-15303/index.md","name":"CVE-2017-15303","record":{"aliases":["GHSA-92jj-g6qw-xrrw"],"analysis":{"component_type":"operating_system","fix_type":"upgrade","impacts":["privilege_escalation","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"CPU-Z kernel driver","requires_auth":"low_privilege","summary":"Local attackers can exploit an arbitrary memory write in the CPU-Z kernel driver to escalate privileges and execute code.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"cpu-z","vendor":"cpuid"}],"cvss":{"score":7.8,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"}],"description":"In CPUID CPU-Z before 1.43, there is an arbitrary memory write that results directly in elevation of privileges, because any program running on the local machine (while CPU-Z is running) can issue an ioctl 0x9C402430 call to the kernel-mode driver (e.g., cpuz141_x64.sys for version 1.41).","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2018-02-22","github_poc":1,"max_poc_stars":113,"metasploit":0,"nuclei":0,"refs":[{"date":"2018-02-22T05:31:13Z","kind":"github_poc","ref":"https://github.com/hfiref0x/Stryker","stars":113,"title":"Multi-purpose proof-of-concept tool based on CPU-Z CVE-2017-15303"}],"tier":"poc_unverified"},"has_fix":null,"headline":"Memory corruption in n/a","id":"CVE-2017-15303","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2017"},"n_packages":0,"n_references":1,"next":{"headline":"Auth bypass in n/a","id":"CVE-2017-15304"},"packages":[],"prev":{"headline":"Missing authorization in n/a","id":"CVE-2017-15302"},"products":["n/a"],"published":"2017-10-16","related":[{"cvss_score":7.8,"headline":"Missing authorization in n/a","id":"CVE-2017-15302","kev_date_added":null,"published":"2017-10-16"},{"cvss_score":5.5,"headline":"Information disclosure in n/a","id":"CVE-2025-65264","kev_date_added":null,"published":"2026-01-27"}],"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)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Local attackers can exploit an arbitrary memory write in the CPU-Z kernel driver to escalate privileges and execute code.","url":"https://insights.sbomify.com/CVE-2017-15303/"}