Local system crash via unchecked zero-length IRP
Published Feb 12, 2020 · Updated Aug 4, 2024
Denial of service in Realtek NDIS driver rt640x64.sys 10.1.505.2015 allows local users to crash the host via a zero-length IRP. The driver performs no size check on the IRP system buffer and assumes that the user-supplied buffer contains at least one byte. Low-privilege local access is required to submit the crafted request; the resulting null-address dereference interrupts the host.
Summary
What happened
Denial of service in Realtek NDIS driver rt640x64.sys 10.1.505.2015 allows local users to crash the host via a zero-length IRP. The driver performs no size check on the IRP system buffer and assumes that the user-supplied buffer contains at least one byte. Low-privilege local access is required to submit the crafted request; the resulting null-address dereference interrupts the host.
The record
- CVE
- CVE-2019-11867
- Published
- Feb 12, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-476, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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