4.8
Moyenne
CVE-2024-29069 In snapd versions prior to 2.62, snapd failed to properly check the destination of symbolic links when extracting a snap
Description
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 (such as icons and desktop files etc) are directly read by snapd when it is extracted. An attacker who could convince a user to install a malicious snap which contained symbolic links at these paths could then cause snapd to write out the contents of the symbolic link destination into a world-readable directory. This in-turn could allow an unprivileged user to gain access to privileged information.
Produits et versions touchés
| Produit | Versions touchées | Corrigé en |
|---|---|---|
| snapd 2.62 | premières → < 2.62 | 2.62 |
Références
- github.com github.com
Chronologie
- Publiée
- Dernière modification
Autres CVE de snapd
Les 9 CVE de snapd →
CVE-2024-29068
In snapd versions prior to 2.62, snapd failed to properly check the file
type when extracting a snap
5.8
Moyenne
CVE-2024-1724
In snapd versions prior to 2.62, when using AppArmor for enforcement of sandbox permissions, snapd failed to restrict…
6.3
Moyenne
CVE-2020-27352
When generating the systemd service units for the docker snap (and other similar snaps), snapd does not specify…
9.3
Critique
CVE-2024-5138
The snapctl component within snapd allows a confined snap to interact with the snapd daemon to take certain privileged…
8.1
Élevée