snapd will follow archived symlinks when unpacking a filesystem
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Canonical | snapd | unaffected |
|
No data.
No data available yet.
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2024-2278 | 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. |
Github GHSA |
GHSA-69p6-gp5x-j269 | snapd failed to properly check the destination of symbolic links when extracting a snap |
Ubuntu USN |
USN-6940-1 | snapd vulnerabilities |
Ubuntu USN |
USN-6940-2 | snapd vulnerabilities |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.228% probability within 30 days)
| Link | Providers |
|---|---|
| https://github.com/snapcore/snapd/pull/13682 |
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Canonical
Canonical snapd |
|
| Weaknesses | CWE-59 | |
| CPEs | cpe:2.3:a:canonical:snapd:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Canonical
Canonical snapd |