Encrypted-disk disclosure and tampering via ignored key size
Published Aug 25, 2022 · Updated Nov 3, 2025
Cryptographic key handling in Red Hat Ceph Storage allows attackers to read or alter data on encrypted disks through weaker keys. The ceph-volume encryption code did not pass the configured osd_dmcrypt_key_size to cryptsetup, so cryptsetup always applied its default instead of the intended key length. The condition is limited to dm-crypt-encrypted OSD volumes whose keys were created by affected code.
Summary
What happened
Cryptographic key handling in Red Hat Ceph Storage allows attackers to read or alter data on encrypted disks through weaker keys. The ceph-volume encryption code did not pass the configured osd_dmcrypt_key_size to cryptsetup, so cryptsetup always applied its default instead of the intended key length. The condition is limited to dm-crypt-encrypted OSD volumes whose keys were created by affected code.
The record
- CVE
- CVE-2021-3979
- Published
- Aug 25, 2022
- Updated
- Nov 3, 2025
- Vendor
- 389 Directory Server
- Product
- Red Hat Ceph Storage
- Classifications
- CWE-327
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 25, 2022CVE publishedPublication date reported by the CVE source.
- Nov 3, 2025Record 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=Not-Known
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