GHSA-69p6-gp5x-j269

Suggest an improvement
Source
https://github.com/advisories/GHSA-69p6-gp5x-j269
Import Source
https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2024/07/GHSA-69p6-gp5x-j269/GHSA-69p6-gp5x-j269.json
JSON Data
https://api.osv.dev/v1/vulns/GHSA-69p6-gp5x-j269
Aliases
Published
2024-07-25T21:31:20Z
Modified
2024-08-26T19:33:21Z
Severity
  • 4.8 (Medium) CVSS_V3 - CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:L CVSS Calculator
  • 2.4 (Low) CVSS_V4 - CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:P/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N CVSS Calculator
Summary
snapd failed to properly check the destination of symbolic links when extracting a snap
Details

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.

References

Affected packages

Go / github.com/snapcore/snapd

Package

Name
github.com/snapcore/snapd
View open source insights on deps.dev
Purl
pkg:golang/github.com/snapcore/snapd

Affected ranges

Type
SEMVER
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
2.62