First published: Thu Mar 14 2024(Updated: )
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.
Credit: security@ubuntu.com security@ubuntu.com
Affected Software | Affected Version | How to fix |
---|---|---|
go/github.com/snapcore/snapd | <2.62 | 2.62 |
debian/snapd | <=2.49-1+deb11u2<=2.57.6-1 | 2.65.3-1 2.66.1-2 |
snapd | <2.62 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2024-29068 is classified as a high-severity vulnerability due to improper file type checks in snapd versions prior to 2.62.
To fix CVE-2024-29068, upgrade snapd to version 2.62 or later.
CVE-2024-29068 affects snapd versions prior to 2.62.
CVE-2024-29068 impacts the extraction of non-regular file types such as pipes or sockets within snap squashfs images.
The vendor for CVE-2024-29068 is Canonical, the developer of snapd.