Service interruption via out-of-bounds write
Published Feb 17, 2021 · Updated Aug 4, 2024
Out-of-bounds write in Intel Graphics Drivers before 15.36.39.5143 allows local users to cause a service interrupt via local access. Intel has not published the affected driver component, the attacker-controlled input, or the missing bounds check that permits the write. Low-privileged local access is required, and the advisory does not specify whether the interruption is a crash, hang, or reset.
Summary
What happened
Out-of-bounds write in Intel Graphics Drivers before 15.36.39.5143 allows local users to cause a service interrupt via local access. Intel has not published the affected driver component, the attacker-controlled input, or the missing bounds check that permits the write. Low-privileged local access is required, and the advisory does not specify whether the interruption is a crash, hang, or reset.
The record
- CVE
- CVE-2020-12386
- Published
- Feb 17, 2021
- Updated
- Aug 4, 2024
- Vendor
- Topcon Positioning Systems, Inc.
- Product
- Intel Graphics Drivers
- Classifications
- CWE-787, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 17, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=before version 15.36.39.5143
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo