Canonical snap up to 2.61 AppArmor $HOME/bin permission assignment

Summaryinfo

A vulnerability classified as problematic has been found in Canonical snap up to 2.61. Impacted is an unknown function of the file $HOME/bin of the component AppArmor Handler. The manipulation leads to permission assignment. This vulnerability is listed as CVE-2024-1724. The attack must be carried out locally. There is no available exploit. It is recommended to upgrade the affected component.

Detailsinfo

A vulnerability was found in Canonical snap up to 2.61 and classified as problematic. This issue affects some unknown processing of the file $HOME/bin of the component AppArmor Handler. The manipulation with an unknown input leads to a permission assignment vulnerability. Using CWE to declare the problem leads to CWE-732. The product specifies permissions for a security-critical resource in a way that allows that resource to be read or modified by unintended actors. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

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.

The weakness was presented by Neil Mcphail as aa191f97713de8dc3ce3ac818539f0b976eb8ef6. The advisory is shared at github.com. The identification of this vulnerability is CVE-2024-1724 since 02/21/2024. The exploitation is known to be easy. An attack has to be approached locally. Technical details are known, but no exploit is available.

The vulnerability scanner Nessus provides a plugin with the ID 239945 (TencentOS Server 4: snapd (TSSA-2025:0174)), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 2.62 eliminates this vulnerability. Applying the patch aa191f97713de8dc3ce3ac818539f0b976eb8ef6 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the vulnerability database at Tenable (239945). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

• Canonical

Name

• snap

Version

• 2.0
• 2.1
• 2.2
• 2.3
• 2.4
• 2.5
• 2.6
• 2.7
• 2.8
• 2.9
• 2.10
• 2.11
• 2.12
• 2.13
• 2.14
• 2.15
• 2.16
• 2.17
• 2.18
• 2.19
• 2.20
• 2.21
• 2.22
• 2.23
• 2.24
• 2.25
• 2.26
• 2.27
• 2.28
• 2.29
• 2.30
• 2.31
• 2.32
• 2.33
• 2.34
• 2.35
• 2.36
• 2.37
• 2.38
• 2.39
• 2.40
• 2.41
• 2.42
• 2.43
• 2.44
• 2.45
• 2.46
• 2.47
• 2.48
• 2.49
• 2.50
• 2.51
• 2.52
• 2.53
• 2.54
• 2.55
• 2.56
• 2.57
• 2.58
• 2.59
• 2.60
• 2.61

License

• open-source

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion