USN-6940-1: snapd vulnerabilities
Neil McPhail discovered that snapd did not properly restrict writes to the $HOME/bin path in the AppArmor profile for snaps using the home plug. An attacker who could convince a user to install a malicious snap could use this vulnerability to escape the snap sandbox. (CVE-2024-1724) Zeyad Gouda discovered that snapd failed to properly check the file type when extracting a snap. An attacker who could convince a user to install a malicious snap containing non-regular files could then cause snapd to block indefinitely while trying to read from such files and cause a denial of service. (CVE-2024-29068) Zeyad Gouda discovered that snapd failed to properly check the destination of symbolic links when extracting a snap. An attacker who could convince a user to install a malicious snap containing crafted symbolic links could then cause snapd to write out the contents of the symbolic link destination into a world-readable directory. This in-turn could allow a local unprivileged user to gain access to privileged information. (CVE-2024-29069)
Affected Software
Event History
Child vulnerabilities
Contains the following vulnerabilities.
Frequently Asked Questions
What is the severity of USN-6940-1?
USN-6940-1 has been classified with a high severity due to the potential for a sandbox escape.
How do I fix USN-6940-1?
To fix USN-6940-1, update the snapd package to versions 2.63+24.04ubuntu0.1, 2.63+22.04ubuntu0.1, or 2.63+20.04ubuntu0.1 as per your Ubuntu version.
What causes the vulnerability in USN-6940-1?
The vulnerability in USN-6940-1 is caused by improper restrictions on the $HOME/bin path in the AppArmor profile for snaps using the home plug.
Who discovered the vulnerability in USN-6940-1?
The vulnerability in USN-6940-1 was discovered by Neil McPhail.
Which versions of Ubuntu are affected by USN-6940-1?
USN-6940-1 affects Ubuntu versions 20.04, 22.04, and 24.04 that use the snapd package.