CVE-2024-29069Medium· 4.8▾ Sunlitsnapd failed to properly check the destination of symbolic links when extracting a snap
▾ Sunlit zone — Low / medium · no exploitation signal
impact 26.4 · likelihood 0 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Exploit-prediction probability, daily snapshots since Sep 12.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via OSV
Last analysed / modified upstream
0.2%
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.com/snapcore/snapd < 2.62Upgrade to a patched release:
github.com/snapcore/snapd 2.62Connected by shared product, vendor, weakness, or advisory.
CVE-2024-29068Medium· 5.8snapd failed to properly check the file type when extracting a snap
CVE-2024-1724Medium· 6.3snapd failed to restrict writes to the $HOME/bin path
CVE-2024-5138Medium· 4.0CVE-2024-5138: snapd snapctl auth bypass