CVE-2024-1724Medium· 6.3▾ Sunlitsnapd failed to restrict writes to the $HOME/bin path
▾ Sunlit zone — Low / medium · no exploitation signal
impact 34.7 · likelihood 0.1 · 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.3%
In snapd versions prior to 2.62, when using AppArmor for enforcement of sandbox permissions, snapd failed to restrict writes to the $HOME/bin path. In Ubuntu, when this path exists, it is automatically added to the users PATH. An attacker who could convince a user to install a malicious snap which used the 'home' plug could use this vulnerability to install arbitrary scripts into the users PATH which may then be run by the user outside of the expected snap sandbox and hence allow them to escape confinement.
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-29069Medium· 4.8snapd failed to properly check the destination of symbolic links when extracting a snap
CVE-2024-29068Medium· 5.8snapd failed to properly check the file type when extracting a snap
CVE-2024-5138Medium· 4.0CVE-2024-5138: snapd snapctl auth bypass