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.
References
Link | Resource |
---|---|
https://github.com/snapcore/snapd/pull/13682 | Issue Tracking Patch |
Configurations
History
26 Aug 2024, 16:55
Type | Values Removed | Values Added |
---|---|---|
CVSS |
v2 : v3 : |
v2 : unknown
v3 : 7.3 |
CWE | CWE-59 | |
First Time |
Canonical
Canonical snapd |
|
CPE | cpe:2.3:a:canonical:snapd:*:*:*:*:*:*:*:* | |
References | () https://github.com/snapcore/snapd/pull/13682 - Issue Tracking, Patch |
26 Jul 2024, 12:38
Type | Values Removed | Values Added |
---|---|---|
Summary |
|
25 Jul 2024, 20:15
Type | Values Removed | Values Added |
---|---|---|
New CVE |
Information
Published : 2024-07-25 20:15
Updated : 2024-08-26 16:55
NVD link : CVE-2024-29069
Mitre link : CVE-2024-29069
CVE.ORG link : CVE-2024-29069
JSON object : View
Products Affected
canonical
- snapd