Skip to content

Product

ubuntu/snapd vulnerabilities

41 published CVES affecting ubuntu/snapd, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).

Total
41
Critical
5
High
27
Medium
9
Low
0
Unscored
0
CISA KEV
0

Latest ubuntu/snapd CVEs

Newest publication first · page 1 of 2

  1. HighCVSS 7.8 EPSS 1.4% Framework module

    Local privilege escalation in snapd on Linux allows local attackers to get root privilege by re-creating snap's private /tmp directory when systemd-tmpfiles is configured to automatically clean up this directory. This issue affects Ubuntu 16.04 LTS, 18.04 LTS, 20.04 LTS, 22.04 LT...

  2. HighCVSS 7.3 EPSS 0.23%

    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 snap squashfs image (s...

  3. MediumCVSS 6.6 EPSS 0.21%

    In snapd versions prior to 2.62, snapd failed to properly check the file type when extracting a snap. The snap format is a squashfs file-system image and so can contain files that are non-regular files (such as pipes or sockets etc). Various file entries within the snap squashfs...

  4. HighCVSS 8.2 EPSS 0.31%

    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 ma...

  5. HighCVSS 8.8 EPSS 0.26%

    When generating the systemd service units for the docker snap (and other similar snaps), snapd does not specify Delegate=yes - as a result systemd will move processes from the containers created and managed by these snaps into the cgroup of the main daemon within the snap itself...

Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.