# CVE-2024-1724: GO-2024-3007 - snapd failed to restrict writes to the $HOME/bin path in github.com/snapcore/snapd

Source: https://junglewise.ai/threats/cve-2024-1724-snapd-failed-to-restrict-writes-to-the-home-bin-path  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2024-08-06  
License: CC BY 4.0 with a link back

CVE-2024-1724 · Severity: low · CVSS 3.1 · Published 2024-08-06

snapd failed to restrict writes to the $HOME/bin path in github.com/snapcore/snapd

Technologies: [github.com/snapcore/snapd (Go)](https://junglewise.ai/threats/technologies/github-com-snapcore-snapd). Vendors: [Go](https://junglewise.ai/threats/vendors/go).

## Quick answers

**Is CVE-2024-1724 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2024-1724 being exploited in the wild.

**How severe is CVE-2024-1724?** Low severity, with a CVSS score of 3.1, published 6 August 2024.

**Which products and versions are affected?** github.com/snapcore/snapd (Go) ECOSYSTEM:introduced=0,fixed=2.62, SEMVER:introduced=0.

**Is there a fix for CVE-2024-1724?** Yes. github.com/snapcore/snapd (Go): upgrade to 2.62 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**Am I affected by CVE-2024-1724?** Check whether you run github.com/snapcore/snapd (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- github.com/snapcore/snapd (Go): upgrade to 2.62 or later

  ```sh
  go get github.com/snapcore/snapd@v2.62
  ```


## Affected products

- github.com/snapcore/snapd (Go) ECOSYSTEM:introduced=0,fixed=2.62, SEMVER:introduced=0

## Identifiers

- CVE-2024-1724
- GHSA-4mh8-9689-38vr
- GO-2024-3007

## Related threats

- [snapd failed to properly check the destination of symbolic links when extracting a snap](https://junglewise.ai/threats/cve-2024-29069-snapd-failed-to-properly-check-the-destination-of-symbolic-links)
- [GO-2024-3008 - snapd failed to properly check the file type when extracting a snap in github.com/snapcore/snapd](https://junglewise.ai/threats/cve-2024-29068-snapd-failed-to-properly-check-the-file-type-when-extracting-a)
- [GO-2024-2906 - in github.com/snapcore/snapd](https://junglewise.ai/threats/cve-2024-5138-snapd-snapctl-auth-bypass)
- [GO-2024-2468 - snapd Race Condition vulnerability in github.com/snapcore/snapd](https://junglewise.ai/threats/cve-2022-3328-snapd-race-condition-vulnerability)
- [Duplicate Advisory: : snapd snapctl auth bypass](https://junglewise.ai/threats/duplicate-advisory-snapd-snapctl-auth-bypass-a1fb15e5)