Skip to content
Fencer Vulns
medium 6.3

CVE-2024-1724 json

snapd allows $HOME/bin symlink

published 2024-07-25 2 y ago modified 2026-09-10 1 mo ago also GHSA-4mh8-9689-38vr , GO-2024-3007 , EUVD-2024-2247

cvss
6.3
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 23%
public exploits
0
none known

Summary

In snapd versions prior to 2.62, when using AppArmor for enforcement of sandbox permissions, snapd failed to restrict writes to the $HOME/bin path. In Ubuntu, when this path exists, it is automatically added to the users PATH. An attacker who could convince a user to install a malicious snap which used the 'home' plug could use this vulnerability to install arbitrary scripts into the users PATH which may then be run by the user outside of the expected snap sandbox and hence allow them to escape confinement.

Patch / fix

  • go github.com/snapcore/snapd 2.62
  • Canonical snap 2.62
  • canonical snapd 2.62
  • snapd Debian 14, Debian 13 2.62-1

debian advisories DEBIAN-CVE-2024-1724

  • snapd Ubuntu 20.04 LTS 2.63+20.04ubuntu0.1
  • snapd Ubuntu 22.04 LTS 2.63+22.04ubuntu0.1
  • snapd Ubuntu 24.04 LTS 2.63+24.04ubuntu0.1
  • snapd Ubuntu Pro 16.04 LTS 2.61.4ubuntu0.16.04.1+esm1
  • snapd Ubuntu Pro 18.04 LTS 2.61.4ubuntu0.18.04.1+esm1

ubuntu advisories UBUNTU-CVE-2024-1724

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2024-1724 updated cvss 8.2

snapd: Snapd versions prior to 2.62, when using AppArmor for enforcement of sandbox permissions, snapd failed to restrict writes to the $HOME/bin path.

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
partial
Assessed
2 y ago

Exploit prediction

0.31% chance of exploitation in the next 30 days, higher than 23% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • gld.mcphail.uk https://gld.mcphail.uk/posts/explaining-cve-2024-1724/ referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 6.3 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L
NVD 3.1 8.2 CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H
GitHub 3.1 6.3 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L

Affected packages

ecosystem package affected fixed in
go github.com/snapcore/snapd
<2.62
all versions
2.62

Affected products

  • Canonical snap
  • canonical snapd

Classification

Weakness
  • CWE-732 Incorrect Permission Assignment for Critical Resource

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.