First published: Mon Jul 01 2024(Updated: )
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.
Credit: security@ubuntu.com security@ubuntu.com
Affected Software | Affected Version | How to fix |
---|---|---|
go/github.com/snapcore/snapd | <2.62 | 2.62 |
debian/snapd | <=2.49-1+deb11u2<=2.57.6-1 | 2.66.1-2 2.67-1 |
Snapcraft Snapd | <2.62 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2024-1724 has been classified as a medium severity vulnerability due to improper restrictions on the $HOME/bin path.
To fix CVE-2024-1724, upgrade snapd to version 2.62 or later.
CVE-2024-1724 affects snapd versions prior to 2.62.
CVE-2024-1724 can allow an attacker to manipulate scripts in the $HOME/bin directory, potentially leading to privilege escalation.
Yes, a patch is available in snapd versions 2.62 and higher.