CVE-2024-45004
Last modified
CVE-2024-45004 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: KEYS: trusted: dcp: fix leak of blob encryption key Trusted keys unseal the key blob on load, but keep the sealed payload in the blob field so that every subsequent read (export) will simply convert this field to hex and send it to userspace. With DCP-based trusted keys, we decrypt the blob encryption key (BEK) in the Kernel due hardware limitations and then decrypt the blob payload. BEK decryption is done in-place which means that the trusted key blob field is modified and it consequently holds the BEK in plain text. Every subsequent read of that key thus send the plain text BEK instead of the encrypted BEK to userspace. This issue only occurs when importing a trusted DCP-based key and then exporting it again. This should rarely happen as the common use cases are to either create a new trusted key and export it, or import a key blob and then just use it without exporting it again. Fix this by performing BEK decryption and encryption in a dedicated buffer. EPSS estimates a 0.10% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: KEYS: trusted: dcp: fix leak of blob encryption key Trusted keys unseal the key blob on load, but keep the sealed payload in the blob field so that every subsequent read (export) will simply convert this field to hex and send it to userspace. With DCP-based trusted keys, we decrypt the blob encryption key (BEK) in the Kernel due hardware limitations and then decrypt the blob payload. BEK decryption is done in-place which means that the trusted key blob field is modified and it consequently holds the BEK in plain text. Every subsequent read of that key thus send the plain text BEK instead of the encrypted BEK to userspace. This issue only occurs when importing a trusted DCP-based key and then exporting it again. This should rarely happen as the common use cases are to either create a new trusted key and export it, or import a key blob and then just use it without exporting it again. Fix this by performing BEK decryption and encryption in a dedicated buffer. Further always wipe the plain text BEK buffer to prevent leaking the key via uninitialized memory.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 6.10, < 6.10.7 | — |
| Linux | Linux Kernel | 6.11 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2024-45004?
How severe is CVE-2024-45004?
How do I fix CVE-2024-45004?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2024
- CVE-2024-44999In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2024-4500A vulnerability was found in SourceCodester Prison Managemen…8.8
- CVE-2024-45000In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-45001In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-45002In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-45003In the Linux kernel, the following vulnerability has been re…4.7
- CVE-2024-45005In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-45006In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-45007In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-45008In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-45009In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-4501A vulnerability was found in Ruijie RG-UAC up to 20240428. I…7.2
Are you affected by CVE-2024-45004?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
