How severe is CVE-2024-1724?

CVE-2024-1724 has a CVSS 3.x base score of 6.3, rated medium severity. It is exploitable over local access with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is low, integrity low, and availability low.

Is CVE-2024-1724 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (22nd percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2024-1724?

CVE-2024-1724 affects Canonical Snapd. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2024-1724?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

Does CVE-2024-1724 have an EU (EUVD) identifier?

Yes. CVE-2024-1724 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2024-2247.

When was CVE-2024-1724 published?

CVE-2024-1724 was published on 2024-07-25 and last updated on 2026-06-17.

CVE-2024-1724

CVE-2024-1724 is a medium-severity vulnerability in Canonical Snapd with a CVSS 3.x base score of 6.3. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-732.

Key facts

Severity: Medium (CVSS 3.x base score 6.3)
EPSS exploit prediction: 0% (22nd percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2024-2247
Weakness: CWE-732
Affected product: Canonical Snapd
Published: 2024-07-25
Last modified: 2026-06-17

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.

Frequently asked questions

What is CVE-2024-1724?: 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.
How severe is CVE-2024-1724?: CVE-2024-1724 has a CVSS 3.x base score of 6.3, rated medium severity. It is exploitable over local access with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is low, integrity low, and availability low.
Is CVE-2024-1724 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (22nd percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2024-1724?: CVE-2024-1724 affects Canonical Snapd. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2024-1724?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2024-1724 have an EU (EUVD) identifier?: Yes. CVE-2024-1724 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2024-2247.
When was CVE-2024-1724 published?: CVE-2024-1724 was published on 2024-07-25 and last updated on 2026-06-17.

References

Affected products (1)

cpe:2.3:a:canonical:snapd:*:*:*:*:*:*:*:*

More vulnerabilities in Canonical Snapd

CVE-2023-1523 — Critical (CVSS 10.0): Using the TIOCLINUX ioctl request, a malicious snap could inject contents into the input of the controlling terminal…
CVE-2019-7304 — Critical (CVSS 9.8): Canonical snapd before version 2.37.1 incorrectly performed socket owner validation, allowing an attacker to run…
CVE-2020-27352 — Critical (CVSS 9.3): When generating the systemd service units for the docker snap (and other similar snaps), snapd does not specify…
CVE-2021-4120 — High (CVSS 8.2): snapd 2.54.2 fails to perform sufficient validation of snap content interface and layout paths, resulting in the…
CVE-2024-5138 — High (CVSS 8.1): The snapctl component within snapd allows a confined snap to interact with the snapd daemon to take certain privileged…
CVE-2022-3328 — High (CVSS 7.8): Race condition in snap-confine's must_mkdir_and_open_with_perms()

All CVEs affecting Canonical Snapd →

Other CWE-732 (Incorrect Permission Assignment for Critical Resource) vulnerabilities

CVE-2026-9508 — Critical (CVSS 10.0): Incorrect permission settings on a critical resource in Suprema BioStar 2 (versions 2.9.3 through 2.9.11) that allow…
CVE-2025-14988 — Critical (CVSS 10.0): A security issue has been identified in ibaPDA that could allow unauthorized actions on the file system under certain…
CVE-2025-69426 — Critical (CVSS 10.0): The Ruckus vRIoT IoT Controller firmware versions prior to 3.0.0.0 (GA) contain hardcoded credentials for an operating…
CVE-2025-12004 — Critical (CVSS 10.0): Incorrect Permission Assignment for Critical Resource vulnerability in The Wikimedia Foundation Mediawiki - Lockdown…
CVE-2014-125121 — Critical (CVSS 10.0): Array Networks vAPV (version 8.3.2.17) and vxAG (version 9.2.0.34) appliances are affected by a privilege escalation…
CVE-2025-46093 — Critical (CVSS 9.9): LiquidFiles before 4.1.2 supports FTP SITE CHMOD for mode 6777 (setuid and setgid), which allows FTPDrop users to…

Browse all CWE-732 (Incorrect Permission Assignment for Critical Resource) vulnerabilities →