# CVE-2024-1724: snapd allows $HOME/bin symlink

> Attackers can escape snap confinement by writing scripts to $HOME/bin, enabling arbitrary code execution outside the sandbox.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Jul 2024
- **Updated:** 1 Aug 2024
- **Also known as:** DEBIAN-CVE-2024-1724, GHSA-4mh8-9689-38vr, GO-2024-3007, UBUNTU-CVE-2024-1724

## What is CVE-2024-1724?

CVE-2024-1724 is a medium-severity path traversal vulnerability in Canonical snap, published on 25 Jul 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

## Which versions are affected by CVE-2024-1724?

3 open source packages ship an affected version, including github.com/snapcore/snapd. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/snapcore/snapd` | Go | All versions | None |
| `github.com/snapcore/snapd` | Go | All versions | 2.62 |
| `github.com/snapcore/snapd` | Go | All versions | 2.62 |

Products: Canonical Snapd.

## How do I fix CVE-2024-1724?

Upgrade github.com/snapcore/snapd to 2.62 or later.

## Is CVE-2024-1724 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-1724 exists.

## Other vulnerabilities in Canonical snap

- [CVE-2023-1523](https://insights.sbomify.com/CVE-2023-1523/): Command injection in snapd (critical 10.0)
- [CVE-2020-27352](https://insights.sbomify.com/CVE-2020-27352/): Privilege escalation in snapd (critical 9.3)
- [CVE-2019-7304](https://insights.sbomify.com/CVE-2019-7304/): Local privilege escalation via snapd socket (high 8.8)
- [CVE-2021-4120](https://insights.sbomify.com/CVE-2021-4120/): snapd could be made to bypass intended access restrictions through snap content interfaces and layout paths (high 8.2)
- [CVE-2024-5138](https://insights.sbomify.com/CVE-2024-5138/): CVE-2024-5138: snapd snapctl auth bypass (high 8.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-1724 and fix it if it is affected.

What it is: CVE-2024-1724 is a medium-severity path traversal vulnerability in Canonical snap, published on 25 Jul 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-1724 exists.

Affected packages and fixed versions:
- github.com/snapcore/snapd (Go): affected all versions; no fix listed
- github.com/snapcore/snapd (Go): affected all versions; fixed in 2.62
- github.com/snapcore/snapd (Go): affected all versions; fixed in 2.62

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-1724/ (Markdown: https://insights.sbomify.com/CVE-2024-1724/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-1724
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-1724
- OSV: https://osv.dev/vulnerability/CVE-2024-1724

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-1724/
Summaries are generated and may contain mistakes; the official description above is the record.