CVE-2019-13179: Calamares versions 3.1 through 3.2.10 copies a LUKS encryption keyfile from /crypto_keyfile.bin (mode 0600 own

Q: How do I fix CVE-2019-13179?

calamares: upgrade to newer than 3.2.10. Exact commands for each OS are on this page.

Q: Is CVE-2019-13179 being exploited?

CVE-2019-13179 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2019-13179 affect?

CVE-2019-13179 affects calamares. Severity is high (CVSS 7.5). Calamares versions 3.1 through 3.2.10 copies a LUKS encryption keyfile from /crypto_keyfile.bin (mode 0600 owned by root) to /boot within a globally readable initramfs image with insecure permissions, which allows this originally protected

Q: How urgent is CVE-2019-13179?

Priority 57/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action

This week

HIGH 7.5REMOTEUPGRADE

CVE-2019-13179 is a high-severity flaw (CVSS 7.5) affecting calamares. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Calamares versions 3.1 through 3.2.10 copies a LUKS encryption keyfile from /crypto_keyfile.bin (mode 0600 owned by root) to /boot within a globally readable initramfs image with insecure permissions, which allows this originally protected file to be read by any user, thereby disclosing decryption keys for LUKS containers created with Full Disk Encryption.

Why this priority

High severity
Public exploit reference
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	7.5 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	2.1% (top 18%)
CISA exploited list	No
Weakness	CWE-522
Published	2019-07-02
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: calamares

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2019-07-02 23:15 UTCPublished CVE record published
2026-06-17 02:16 UTCUpdated Record last modified

calamares calamares UPGRADE

Affected: <= 3.2.10

Fixed in: newer than 3.2.10

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy calamares || rpm -q calamares || calamares --version

2. UPGRADE to newer than 3.2.10 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade calamares

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade calamares

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2019-13179?

calamares: upgrade to newer than 3.2.10. Exact commands for each OS are on this page.

Is CVE-2019-13179 being exploited?

CVE-2019-13179 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2019-13179 affect?

CVE-2019-13179 affects calamares. Severity is high (CVSS 7.5). Calamares versions 3.1 through 3.2.10 copies a LUKS encryption keyfile from /crypto_keyfile.bin (mode 0600 owned by root) to /boot within a globally readable initramfs image with insecure permissions, which allows this originally protected

How urgent is CVE-2019-13179?

Priority 57/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action

Related CVEs

CVE-2019-13178 HIGH 8.1 UPGRADE modules/luksbootkeyfile/main.py in Calamares versions 3.1 through 3.2.10 has a race condition between the time

References

← Back to latest CVEs