Metadata-server crash via oversized eadatasize field
Published Jan 27, 2020 · Updated Aug 5, 2024
Denial of service in Lustre before 2.12.3 allows remote attackers to crash the metadata server with a crafted MDT request. The mdt module accepts an oversized MDT Body eadatasize field without validating it against the packet's supplied field sizes, reaching an LBUG panic. Any client capable of sending MDT requests can stop metadata service, interrupting filesystem namespace operations until the server recovers.
Summary
What happened
Denial of service in Lustre before 2.12.3 allows remote attackers to crash the metadata server with a crafted MDT request. The mdt module accepts an oversized MDT Body eadatasize field without validating it against the packet's supplied field sizes, reaching an LBUG panic. Any client capable of sending MDT requests can stop metadata service, interrupting filesystem namespace operations until the server recovers.
The record
- CVE
- CVE-2019-20430
- Published
- Jan 27, 2020
- Updated
- Aug 5, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-670, CWE-20, 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.
Weakness, pattern, technique
Public exploit references
- LU-12602 issue reportproof of concept · unverified
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