snapd vulnerabilities
4 known vulnerabilities in snapd from Canonical. 4 are rated high or critical. Each entry lists the affected versions and the release that fixes it, where the vendor has published one.
Latest first
- 7.3 High severity
snapd: Improper Link Resolution Before File Access
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 sn
- 8.2 High severity
snap: Incorrect Permission Assignment for Critical Resource
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
- 8.1 High severity
The snapctl component within snapd allows a confined snap to interact with the snapd daemon to…
The snapctl component within snapd allows a confined snap to interact with the snapd daemon to take certain privileged actions on behalf of the snap. It was found that snapctl did not properly parse command-line arguments, allowing an unprivileged user to trig
- 10.0 Critical severity
snapd: Improper Neutralization of Special Elements in Output Used by a Downstream Component
Using the TIOCLINUX ioctl request, a malicious snap could inject contents into the input of the controlling terminal which could allow it to cause arbitrary commands to be executed outside of the snap sandbox after the snap exits. Graphical terminal emulators