Vulnerability in snapd (UBUNTU-CVE-2024-5300)
Summary
Vulnerability in snapd (UBUNTU-CVE-2024-5300). Confidential information can be exposed externally. Mitigation: upgrade to 2.61.4ubuntu0.16.04.1+esm4 or later.
Original description
The description as published by the source.
An access control bypass and information disclosure vulnerability exists in the base AppArmor security profile configuration of Canonical snapd. The abstraction rules located in /etc/apparmor.d/abstractions/nss-systemd (inherited via ) inadvertently permit strictly confined snap applications, which lack the privileged account-control interface, to interact directly with the io.systemd.Multiplexer and io.systemd.NameServiceSwitch UNIX domain sockets under /run/systemd/userdb/. On systems where the systemd-userdbd service is installed and operational, the service fails to distinguish between an unconfined root user on the host system and a restricted root user running within a snap application's sandbox (such as a daemon or configuration hook). Because systemd-userdbd returns "complete" user records—including sensitive hashed user passwords from /etc/shadow—when queried by a process running as root, a compromised or malicious strictly confined snap executing code as root can successfully query the Varlink interface to retrieve all system password hashes, bypassing intended snap sandbox restrictions. This issue is mitigated by the fact that systemd-userdbd is not installed by default on standard Ubuntu deployments.
Source: OSV.dev (Open Source Vulnerabilities) OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as UBUNTU-CVE-2024-5300 has been found in snapd.
Confidential information can be exposed externally.
What to do: upgrade snapd to 2.61.4ubuntu0.16.04.1+esm4 or later.
If unsure, ask your IT team or search "snapd UBUNTU-CVE-2024-5300" on the vendor's site.
UBUNTU-CVE-2024-5300 (snapd)
Attack vector: local / no user interaction
Patched: 2.61.4ubuntu0.16.04.1+esm4 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (unclassified) exists in snapd.
Check the vendor advisory for the affected versions of snapd.
Severity: ?. Confidential information can be exposed externally.
Update to 2.61.4ubuntu0.16.04.1+esm4.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'snapd' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'snapd' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
snapdを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade snapd to 2.61.4ubuntu0.16.04.1+esm4ステージング環境で 2.61.4ubuntu0.16.04.1+esm4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory ubuntu.com
- report ubuntu.com
- report cve.org