LUKS key disclosure via plaintext initrd archive
Published Jun 29, 2023 · Updated Nov 27, 2024
Information exposure in NixOS calamares-nixos-extensions 0.3.12 and earlier allows local users to read LUKS key material. The installer module adds crypto_keyfile.bin to boot.initrd.secrets, embedding the key in a plaintext CPIO archive within unencrypted /boot. Exposure requires graphical Calamares installation on a non-UEFI system or with a LUKS partition other than /; nixos-install is unaffected.
Summary
What happened
Information exposure in NixOS calamares-nixos-extensions 0.3.12 and earlier allows local users to read LUKS key material. The installer module adds crypto_keyfile.bin to boot.initrd.secrets, embedding the key in a plaintext CPIO archive within unencrypted /boot. Exposure requires graphical Calamares installation on a non-UEFI system or with a LUKS partition other than /; nixos-install is unaffected.
The record
- CVE
- CVE-2023-36476
- Published
- Jun 29, 2023
- Updated
- Nov 27, 2024
- Vendor
- NixOS
- Product
- calamares-nixos-extensions
- Classifications
- CWE-522, CWE-256, CWE-200, T1552.001
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 29, 2023CVE publishedPublication date reported by the CVE source.
- Nov 27, 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=<= 0.3.12
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
- Vendor-documented initrd key extraction procedurefunctional · demonstrated
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