CVE-2024-29069: snapd failed to properly check the destination of symbolic links when extracting a snap
In snapd versions prior to 2.62, snapd failed to properly check the destination of symbolic links when extracting a snap. The snap format is a squashfs file-system image and so can contain symbolic links and other file types. Various file entries within the snap squashfs image (such as icons and desktop files etc) are directly read by snapd when it is extracted.
Published Jul 25, 2024 · Updated Nov 18, 2024
Affected packages
github.com/snapcore/snapd
- Ecosystem
- Go
- Affected
- < 2.62
- Fixed in
- 2.62
- Check
go list -m github.com/snapcore/snapd
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
In snapd versions prior to 2.62, snapd failed to properly check the destination of symbolic links when extracting a snap. The snap format is a squashfs file-system image and so can contain symbolic links and other file types. Various file entries within the snap squashfs image (such as icons and desktop files etc) are directly read by snapd when it is extracted. An attacker who could convince a user to install a malicious snap which contained symbolic links at these paths could then cause snapd to write out the contents of the symbolic link destination into a world-readable directory. This in-turn could allow an unprivileged user to gain access to privileged information.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2024-5138
CVE-2024-5138: snapd snapctl auth bypass
medium4.0Jan 16, 2025CVE-2024-1724
snapd failed to restrict writes to the $HOME/bin path
medium6.3Jul 25, 2024CVE-2024-29068
snapd failed to properly check the file type when extracting a snap
medium5.8Jul 25, 2024CVE-2022-3328
snapd Race Condition vulnerability
critical7.8Jan 8, 2024
