cve.bz

CVE-2024-29069 canonical snapd: Link Following

7.3 highEPSS 0.2%Fix available

High (7.3) in canonical snapd. EPSS 0.2% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/snapcore/snapd 2.62.

On this page
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.

Severity

CVSS 3.1

7.3 high
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 14th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2024-07-26. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-59 Improper Link Resolution Before File Access (Link Following)
CWE-610 Externally Controlled Reference to a Resource in Another Sphere
OWASP Top 10
A01:2025 Broken Access Control, A05:2025 Injection
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2024-29069 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2024-29069?via=ask-ai-copy and https://cve.bz/cve/CVE-2024-29069?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2024-29069 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Canonical snapdbefore 2.62

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-69p6-gp5x-j269Gogithub.com/snapcore/snapd<2.622.62
GO-2024-3009Gogithub.com/snapcore/snapdall versionsno fix published

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12snapdno fix listedDEBIAN-CVE-2024-29069
Debian13, 14snapd2.62-1DEBIAN-CVE-2024-29069
Ubuntu20.04:LTSsnapd2.63+20.04ubuntu0.1UBUNTU-CVE-2024-29069 USN-6940-1
Ubuntu22.04:LTSsnapd2.63+22.04ubuntu0.1UBUNTU-CVE-2024-29069 USN-6940-1
Ubuntu24.04:LTSsnapd2.63+24.04ubuntu0.1UBUNTU-CVE-2024-29069 USN-6940-1
UbuntuPro:16.04:LTSsnapd2.61.4ubuntu0.16.04.1+esm1UBUNTU-CVE-2024-29069 USN-6940-2
UbuntuPro:18.04:LTSsnapd2.61.4ubuntu0.18.04.1+esm1UBUNTU-CVE-2024-29069 USN-6940-2

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu.

Attack patterns (CAPEC)

  • CAPEC-219 XML Routing Detour Attacks Likelihood: High · Severity: Medium
  • CAPEC-17 Using Malicious Files Likelihood: High · Severity: Very High
  • CAPEC-35 Leverage Executable Code in Non-Executable Files Likelihood: High · Severity: Very High
  • CAPEC-76 Manipulating Web Input to File System Calls Likelihood: High · Severity: Very High
  • CAPEC-132 Symlink Attack Likelihood: Low · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON