Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

snapd will follow archived symlinks when unpacking a filesystem

CVSS 3.1 4.8 MEDIUMEUVD CVSS 3.1 4.8 CVSS 3.1 · [email protected] · Secondary 4.8 MEDIUMCVSS 3.1 · [email protected] · Primary 7.3 HIGHCVSS_V3 CVSS_V4 Publisher rating LOWFixed by github.com/snapcore/snapd 2.62osv · severity unknownKEV status unknown

cve-program · CVE-2024-29069

Published

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.

Read the publisher's advisory

euvd · EUVD-2024-2278

Published

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.

Read the publisher's advisory

nvd · CVE-2024-29069

Published

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.

Read the publisher's advisory

osv · GHSA-69p6-gp5x-j269

Published

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.

Read the publisher's advisory

osv · GO-2024-3009

Published

snapd failed to properly check the destination of symbolic links when extracting a snap in github.com/snapcore/snapd. NOTE: The source advisory for this report contains additional versions that could not be automatically mapped to standard Go module versions. (If this is causing false-positive reports from vulnerability scanners, please suggest an edit to the report.) The additional affected modules and versions are: github.com/snapcore/snapd before v2.62.0.

Read the publisher's advisory

Affected versions, risk and source history

cve-program · CVE-2024-29069

Published

snapd

Vendor product

Publisher's version information

Shown as published. These rules are not interpreted as NuGet package version ranges.

{
                    "vendor": "Canonical",
                    "product": "snapd",
                    "platforms": [
                        "Linux"
                    ],
                    "packageName": "snapd",
                    "repo": "https://github.com/snapcore/snapd/",
                    "modules": [
                        "squashfs"
                    ],
                    "programFiles": [
                        "snap/container.go",
                        "snap/snapdir/snapdir.go",
                        "snap/squashfs/squashfs.go"
                    ],
                    "versions": [
                        {
                            "status": "affected",
                            "version": "0",
                            "lessThan": "2.62",
                            "versionType": "custom"
                        }
                    ],
                    "defaultStatus": "unaffected"
                }

Original source record · Cite this exact observation · Complete original publisher JSON

euvd · EUVD-2024-2278

Published

EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.

Original publisher date fields

datePublished: Jul 25, 2024, 7:39:41 PM

dateUpdated: Aug 2, 2024, 1:03:51 AM

1 related source bulletins · separate from aliases

WID-SEC-W-2024-1712: Canonical Snap: Mehrere Schwachstellen

CVE-2024-1724 · CVE-2024-29068 · CVE-2024-29069

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

nvd · CVE-2024-29069

Published

NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.

Source analysis status: Modified

Weakness classifications: CWE-610 · CWE-59

Original publisher date fields

published: 2024-07-25T20:15:04.483

lastModified: 2026-06-17T07:22:21.740

1 source CPE criteria · context only
  • cpe:2.3:a:canonical:snapd:*:*:*:*:*:*:*:*

The original JSON retains the logical configuration operators, exclusions and version bounds.

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

osv · GHSA-69p6-gp5x-j269

Published

github.com/snapcore/snapd

Go

ECOSYSTEM · introduced 0 → fixed 2.62

Original source record · Cite this exact observation · Complete original publisher JSON

osv · GO-2024-3009

Published

github.com/snapcore/snapd

Go

SEMVER · introduced 0

Original source record · Cite this exact observation · Complete original publisher JSON

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 16 Nov 14:56 UTC · 274 of 275 readable · 250 fully read · 20 waiting for GitHub's hourly limit · documentation 469/469 current