CVE-2024-29069

< 2.62

In snapd versions prior to 2.62, snapd failed to properly check the destination of symbolic links when extracting a snap. The snap

4.8MEDIUM

CVE-2024-29068

< 2.62

In snapd versions prior to 2.62, snapd failed to properly check the file type when extracting a snap. The snap format is a squashf

5.8MEDIUM

CVE-2024-1724

< 2.62

In snapd versions prior to 2.62, when using AppArmor for enforcement of sandbox permissions, snapd failed to restrict writes to t

6.3MEDIUM

CVE-2020-27352

< 2.48.3

When generating the systemd service units for the docker snap (and other similar snaps), snapd does not specify Delegate=yes - as

9.3CRITICAL

CVE-2024-5138

>= 2.51.6 and < 2.63.1

The snapctl component within snapd allows a confined snap to interact with the snapd daemon to take certain privileged actions on

8.1HIGH

CVE-2022-3328

< 2.61.1

Race condition in snap-confine's must_mkdir_and_open_with_perms()

7.8HIGH

CVE-2023-1523

< 2.59.5

Using the TIOCLINUX ioctl request, a malicious snap could inject contents into the input of the controlling terminal which could a

10.0CRITICAL

CVE-2021-4120

<= 2.54.2

snapd 2.54.2 fails to perform sufficient validation of snap content interface and layout paths, resulting in the ability for snaps

8.2HIGH

CVE-2021-44731

<= 2.54.2

A race condition existed in the snapd 2.54.2 snap-confine binary when preparing a private mount namespace for a snap. This could a

7.8HIGH

CVE-2021-44730

<= 2.54.2

snapd 2.54.2 did not properly validate the location of the snap-confine binary. A local attacker who can hardlink this binary to a

7.8HIGH

CVE-2021-3155

< 2.54.3

snapd 2.54.2 and earlier created ~/snap directories in user home directories without specifying owner-only permissions. This could

3.8LOW

CVE-2020-11933

< 2.45.2

cloud-init as managed by snapd on Ubuntu Core 16 and Ubuntu Core 18 devices was run without restrictions on every boot, which a ph

7.3HIGH

CVE-2019-11503

< 2.39

snap-confine as included in snapd before 2.39 did not guard against symlink races when performing the chdir() to the current worki

7.5HIGH

CVE-2019-11502

< 2.38

snap-confine in snapd before 2.38 incorrectly set the ownership of a snap application to the uid and gid of the first calling user

7.5HIGH

CVE-2019-7304

< 2.37.1

Canonical snapd before version 2.37.1 incorrectly performed socket owner validation, allowing an attacker to run arbitrary command

9.8CRITICAL

CVE-2019-7303

< 2.37.4

A vulnerability in the seccomp filters of Canonical snapd before version 2.37.4 allows a strict mode snap to insert characters int

7.5HIGH

CVE-2017-14178

>= 2.27 and <= 2.29.2

In snapd 2.27 through 2.29.2 the 'snap logs' command could be made to call journalctl without match arguments and therefore allow

7.5HIGH