{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-15302 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-15302 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-15302 is a high-severity missing authorization 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-15302 and fix it if it is affected.\n\nWhat it is: CVE-2017-15302 is a high-severity missing authorization 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-15302 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-15302/ (Markdown: https://insights.sbomify.com/CVE-2017-15302/index.md)","id":"CVE-2017-15302","markdown":"https://insights.sbomify.com/CVE-2017-15302/index.md","name":"CVE-2017-15302","record":{"aliases":["GHSA-mjvx-c375-3xj2"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["data_read","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Windows kernel driver","requires_auth":"low_privilege","summary":"Local attackers can read arbitrary physical memory and escalate privileges via an insecure kernel driver in CPU-Z due to missing access controls.","user_interaction":"not_required","vuln_class":"missing_authorization"},"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":[],"description":"In CPUID CPU-Z through 1.81, there are improper access rights to a kernel-mode driver (e.g., cpuz143_x64.sys for version 1.43) that can result in information disclosure or elevation of privileges, because of an arbitrary read of any physical address via ioctl 0x9C402604. Any application running on the system (Windows), including sandboxed users, can issue an ioctl to this driver without any validation. Furthermore, the driver can map any physical page on the system and returns the allocated map page address to the user: that results in an information leak and EoP. NOTE: the vendor indicates that the arbitrary read itself is intentional behavior (for ACPI scan functionality); the security issue is the lack of an ACL.","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":"Missing authorization in n/a","id":"CVE-2017-15302","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2017"},"n_packages":0,"n_references":1,"next":{"headline":"Memory corruption in n/a","id":"CVE-2017-15303"},"packages":[],"prev":{"headline":"Denial of service in n/a","id":"CVE-2017-15300"},"products":["n/a"],"published":"2017-10-16","related":[{"cvss_score":7.8,"headline":"Memory corruption in n/a","id":"CVE-2017-15303","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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Local attackers can read arbitrary physical memory and escalate privileges via an insecure kernel driver in CPU-Z due to missing access controls.","url":"https://insights.sbomify.com/CVE-2017-15302/"}