Persistent plaintext exposure via unauthenticated reencryption metadata
Published Aug 24, 2022 · Updated Aug 3, 2024
Metadata authentication failure in cryptsetup 2.2.0 through 2.3.6 and 2.4.0 through 2.4.2 allows physically proximate attackers to decrypt LUKS2 data. Crash recovery accepts attacker-modified reencryption metadata without a key-derived digest and rewrites part of the device as plaintext after a valid activation. Exploitation requires repeated physical access: first to alter the header and later to retrieve or modify the exposed plaintext.
Summary
What happened
Metadata authentication failure in cryptsetup 2.2.0 through 2.3.6 and 2.4.0 through 2.4.2 allows physically proximate attackers to decrypt LUKS2 data. Crash recovery accepts attacker-modified reencryption metadata without a key-derived digest and rewrites part of the device as plaintext after a valid activation. Exploitation requires repeated physical access: first to alter the header and later to retrieve or modify the exposed plaintext.
The record
- CVE
- CVE-2021-4122
- Published
- Aug 24, 2022
- Updated
- Aug 3, 2024
- Vendor
- Cryptsetup
- Product
- cryptsetup
- Classifications
- CWE-345, CWE-349, T1565
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 24, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 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=Fixed in cryptsetup 2.4.3, cryptsetup 2.3.7
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
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