snapd failed to restrict writes to the $HOME/bin path
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.
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2024-1724US | high8.2 | — | ||
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 exist… | ||||
references
External citations — patches, advisories, analysis.
- https://github.com/snapcore/snapdPACKAGE
- https://github.com/snapcore/snapd/commit/aa191f97713de8dc3ce3ac818539f0b976eb8ef6WEB
- https://github.com/snapcore/snapd/pull/13689WEB
- https://gld.mcphail.uk/posts/explaining-cve-2024-1724WEB
- https://nvd.nist.gov/vuln/detail/CVE-2024-1724ADVISORY
- https://pkg.go.dev/vuln/GO-2024-3007WEB
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan