Headline
GHSA-69p6-gp5x-j269: 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. 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.
- GitHub Advisory Database
- GitHub Reviewed
- CVE-2024-29069
snapd failed to properly check the destination of symbolic links when extracting a snap
Moderate severity GitHub Reviewed Published Jul 25, 2024 to the GitHub Advisory Database • Updated Jul 26, 2024
Package
gomod github.com/snapcore/snapd (Go)
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
- https://nvd.nist.gov/vuln/detail/CVE-2024-29069
- snapcore/snapd#13682
- snapcore/snapd@b66fee8
Published to the GitHub Advisory Database
Jul 25, 2024
Last updated
Jul 26, 2024