5.8
Medium
CVE-2024-29068 In snapd versions prior to 2.62, snapd failed to properly check the file type when extracting a snap
Description
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 image (such as icons etc) are directly read by snapd when it is extracted. An attacker who could convince a user to install a malicious snap which contained non-regular files at these paths could then cause snapd to block indefinitely trying to read from such files and cause a denial of service.
Affected products and versions
| Product | Affected versions | Fixed in |
|---|---|---|
| snapd 2.62 | earliest → < 2.62 | 2.62 |
References
- github.com github.com
- github.com github.com
Timeline
- Published
- Last modified
Other CVEs of snapd
The 9 CVEs of snapd →
CVE-2024-29069
In snapd versions prior to 2.62, snapd failed to properly check the
destination of symbolic links when extracting a snap
4.8
Medium
CVE-2024-1724
In snapd versions prior to 2.62, when using AppArmor for enforcement of sandbox permissions, snapd failed to restrict…
6.3
Medium
CVE-2020-27352
When generating the systemd service units for the docker snap (and other similar snaps), snapd does not specify…
9.3
Critical
CVE-2024-5138
The snapctl component within snapd allows a confined snap to interact with the snapd daemon to take certain privileged…
8.1
High