Privileged file disclosure via unchecked snap symlinks
Published Jul 25, 2024 · Updated Aug 2, 2024
Information disclosure in Canonical snapd before 2.62 allows attackers to expose privileged file contents through crafted snap symlinks. The snap container validator reads metadata paths without rejecting links that resolve outside the SquashFS image, then copies target contents into a world-readable directory. Exploitation requires user installation of the crafted snap; afterward, a local unprivileged user can read the exposed privileged data.
Summary
What happened
Information disclosure in Canonical snapd before 2.62 allows attackers to expose privileged file contents through crafted snap symlinks. The snap container validator reads metadata paths without rejecting links that resolve outside the SquashFS image, then copies target contents into a world-readable directory. Exploitation requires user installation of the crafted snap; afterward, a local unprivileged user can read the exposed privileged data.
The record
- CVE
- CVE-2024-29069
- Published
- Jul 25, 2024
- Updated
- Aug 2, 2024
- Vendor
- Canonical
- Product
- snapd
- Classifications
- CWE-610, CWE-59, T1204.002
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 25, 2024CVE publishedPublication date reported by the CVE source.
- Aug 2, 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.62
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