Server panic via unchecked lock count
Published Jan 27, 2020 · Updated Aug 5, 2024
Out-of-bounds read in Lustre before 2.12.3 allows remote attackers to panic a server through a crafted client lock-cancel packet. The ptlrpc ldl_request_cancel function accepts a large attacker-controlled lock_count without validating the associated packet fields, causing an out-of-bounds read. A reachable Lustre service is the gate; no prior privileges or user interaction is required, and exploitation interrupts the affected server.
Summary
What happened
Out-of-bounds read in Lustre before 2.12.3 allows remote attackers to panic a server through a crafted client lock-cancel packet. The ptlrpc ldl_request_cancel function accepts a large attacker-controlled lock_count without validating the associated packet fields, causing an out-of-bounds read. A reachable Lustre service is the gate; no prior privileges or user interaction is required, and exploitation interrupts the affected server.
The record
- CVE
- CVE-2019-20428
- Published
- Jan 27, 2020
- Updated
- Aug 5, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-125, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 27, 2020CVE publishedPublication date reported by the CVE source.
- Aug 5, 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