In snapd versions prior to 2.62, snapd failed to properly check the destination of symbolic links when extracting a snap. The snap format is a squashfs file-system image and so can contain symbolic links and other file types. Various file entries within the snap squashfs image (such as icons and desktop files etc) are directly read by snapd when it is extracted. An attacker who could convince a user to install a malicious snap which contained symbolic links at these paths could then cause snapd to write out the contents of the symbolic link destination into a world-readable directory. This in-turn could allow an unprivileged user to gain access to privileged information.

The version of Tencent Linux installed on the remote TencentOS Server 4 host is prior to tested version. It is, therefore, affected by multiple vulnerabilities as referenced in the TSSA-2025:0174 advisory.

    Package updates are available for TencentOS Server 4 that fix the following vulnerabilities:

    CVE-2024-29069:
    In snapd versions prior to 2.62, snapd failed to properly check the     destination of symbolic links when extracting a snap. The snap format     is a squashfs file-system image and so can contain symbolic links and     other file types. Various file entries within the snap squashfs image     (such as icons and desktop files etc) are directly read by snapd when     it is extracted. An attacker who could convince a user to install a     malicious snap which contained symbolic links at these paths could then     cause snapd to write out the contents of the symbolic link destination     into a world-readable directory. This in-turn could allow an unprivileged     user to gain access to privileged information.

    CVE-2024-29068:
    In snapd versions prior to 2.62, snapd failed to properly check the file     type when extracting a snap. The snap format is a squashfs file-system     image and so can contain files that are non-regular files (such as pipes     or sockets etc). Various file entries within the snap squashfs image     (such as icons etc) are directly read by snapd when it is extracted. An     attacker who could convince a user to install a malicious snap which     contained non-regular files at these paths could then cause snapd to block     indefinitely trying to read from such files and cause a denial of service.

    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.

Tenable has extracted the preceding description block directly from the Tencent Linux security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - In snapd versions prior to 2.62, snapd failed to properly check the destination of symbolic links when     extracting a snap. The snap format is a squashfs file-system image and so can contain symbolic links and     other file types. Various file entries within the snap squashfs image (such as icons and desktop files     etc) are directly read by snapd when it is extracted. An attacker who could convince a user to install a     malicious snap which contained symbolic links at these paths could then cause snapd to write out the     contents of the symbolic link destination into a world-readable directory. This in-turn could allow an     unprivileged user to gain access to privileged information. (CVE-2024-29069)

Note that Nessus relies on the presence of the package as reported by the vendor.

There are packages installed that are affected by a vulnerability referenced in the following CVE:

  - In snapd versions prior to 2.62, snapd failed to properly check the destination of symbolic links when
    extracting a snap. The snap format is a squashfs file-system image and so can contain symbolic links and
    other file types. Various file entries within the snap squashfs image (such as icons and desktop files
    etc) are directly read by snapd when it is extracted. An attacker who could convince a user to install a
    malicious snap which contained symbolic links at these paths could then cause snapd to write out the
    contents of the symbolic link destination into a world-readable directory. This in-turn could allow an
    unprivileged user to gain access to privileged information. (CVE-2024-29069)

The remote Ubuntu 16.04 LTS / 18.04 LTS host has packages installed that are affected by multiple vulnerabilities as referenced in the USN-6940-2 advisory.

    USN-6940-1 fixed vulnerabilities in snapd. This update provides the

    corresponding updates for Ubuntu 18.04 LTS and Ubuntu 16.04 LTS.



Tenable has extracted the preceding description block directly from the Ubuntu security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote Ubuntu 20.04 LTS / 22.04 LTS / 24.04 LTS host has packages installed that are affected by multiple vulnerabilities as referenced in the USN-6940-1 advisory.

    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)

Tenable has extracted the preceding description block directly from the Ubuntu security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

ID	Name	Product	Family	Type	Severity
239945	TencentOS Server 4: snapd (TSSA-2025:0174)	Nessus	Tencent Local Security Checks	Local	medium
227647	Linux Distros Unpatched Vulnerability : CVE-2024-29069	Nessus	Misc.	Local	high
411347	SCA: security update for github.com/snapcore/snapd (GHSA-69p6-gp5x-j269)	Tenable Cloud Security	SCA Checks	Local	low
411347	SCA: security update for github.com/snapcore/snapd (GHSA-69p6-gp5x-j269)	Tenable Self-Hosted Container Security	SCA Checks	Local	low
213997	Ubuntu 16.04 LTS / 18.04 LTS : snapd vulnerabilities (USN-6940-2)	Nessus	Ubuntu Local Security Checks	Local	high
204952	Ubuntu 20.04 LTS / 22.04 LTS / 24.04 LTS : snapd vulnerabilities (USN-6940-1)	Nessus	Ubuntu Local Security Checks	Local	high

Detections

Analytics

CVE-2024-29069

low

Tenable Plugins

medium

high

low

low

high

high