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.
The product specifies permissions for a security-critical resource in a way that allows that resource to be read or modified by unintended actors.
Name | Vendor | Start Version | End Version |
---|---|---|---|
Snapd | Canonical | * | 2.62 (excluding) |
Snapd | Ubuntu | bionic | * |
Snapd | Ubuntu | devel | * |
Snapd | Ubuntu | esm-infra/bionic | * |
Snapd | Ubuntu | esm-infra/xenial | * |
Snapd | Ubuntu | focal | * |
Snapd | Ubuntu | jammy | * |
Snapd | Ubuntu | mantic | * |
Snapd | Ubuntu | noble | * |
Snapd | Ubuntu | oracular | * |
Snapd | Ubuntu | snap | * |
Snapd | Ubuntu | trusty | * |
Snapd | Ubuntu | upstream | * |
Snapd | Ubuntu | xenial | * |