Encrypted disk disclosure through GRUB shell access
Published Nov 13, 2024 · Updated Nov 13, 2024
Improper access control in GRUB2 on openSUSE Tumbleweed before 2.12-28.1 allows physically proximate attackers to read encrypted disk files. SUSE has not published the responsible function or the access-control operation that fails inside the GRUB shell. Physical access and entry to the GRUB shell are required; the demonstrated consequence is disclosure of files protected by disk encryption.
Summary
What happened
Improper access control in GRUB2 on openSUSE Tumbleweed before 2.12-28.1 allows physically proximate attackers to read encrypted disk files. SUSE has not published the responsible function or the access-control operation that fails inside the GRUB shell. Physical access and entry to the GRUB shell are required; the demonstrated consequence is disclosure of files protected by disk encryption.
The record
- CVE
- CVE-2024-49504
- Published
- Nov 13, 2024
- Updated
- Nov 13, 2024
- Vendor
- OpenSUSE
- Product
- openSUSE Tumbleweed
- Classifications
- CWE-276
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 13, 2024CVE publishedPublication date reported by the CVE source.
- Nov 13, 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 <2.12-28.1
- Affected versionversion=? <2.12-28.1
What conditions does exploitation require?
What is affected?
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