Authenticated local denial of service via buffer overflow
Published Mar 12, 2020 · Updated Aug 4, 2024
A buffer overflow in Intel Graphics Drivers before 26.20.100.6912 allows local users to cause denial of service via local access. Intel identifies the locus only as a buffer in the graphics driver and does not publish the specific function or input path. An authenticated local user must reach the affected driver interface; the reported consequence is service interruption without stated confidentiality or integrity impact.
Summary
What happened
A buffer overflow in Intel Graphics Drivers before 26.20.100.6912 allows local users to cause denial of service via local access. Intel identifies the locus only as a buffer in the graphics driver and does not publish the specific function or input path. An authenticated local user must reach the affected driver interface; the reported consequence is service interruption without stated confidentiality or integrity impact.
The record
- CVE
- CVE-2020-0501
- Published
- Mar 12, 2020
- Updated
- Aug 4, 2024
- Vendor
- Topcon Positioning Systems, Inc.
- Product
- Intel Graphics Drivers
- Classifications
- CWE-120, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 12, 2020CVE 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 26.20.100.691
- Affected versionversion=See advisory https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-00315.html
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