← Back
CVE-2024-6219
Authentication Bypass in github.com/canonical/lxd (CVE-2024-6219)
Summary
authentication bypass in github.com/canonical/lxd (CVE-2024-6219). Risk of unauthorized operations or information disclosure. Exploitable via ``server.ca``. Mitigation: upgrade to `0.0.0-20240403103450-0e7f2b5bf4d2` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2024-6219** has been found in github.com/canonical/lxd.
Attackers can target a specific entry point like ``server.ca`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade github.com/canonical/lxd to **0.0.0-20240403103450-0e7f2b5bf4d2** or later.
If unsure, ask your IT team or search "github.com/canonical/lxd CVE-2024-6219" on the vendor's site.
CVE-2024-6219 (github.com/canonical/lxd) — CWE-287 /
Attack vector: local / no user interaction
Attack surface: `server.ca` / `LXD_DIR` / `core.trust_ca_certificates` / `false`
Patched: `0.0.0-20240403103450-0e7f2b5bf4d2` — 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.
❓ What is the problem
**authentication bypass** (CWE-287) exists in github.com/canonical/lxd. Attackers reach the vulnerable code path via ``server.ca`` without authentication.
📍 Affected scope
github.com/canonical/lxd — . Attack surface: `server.ca` / `LXD_DIR` / `core.trust_ca_certificates` / `false`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **0.0.0-20240403103450-0e7f2b5bf4d2**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'github.com/canonical/lxd' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/canonical/lxd' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `github.com/canonical/lxd` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade github.com/canonical/lxd to 0.0.0-20240403103450-0e7f2b5bf4d2ステージング環境で 0.0.0-20240403103450-0e7f2b5bf4d2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
go
github.com/canonical/lxd
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"0.0.0-20240403103450-0e7f2b5bf4d2"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2024-6219
- package https://github.com/canonical/lxd
- web https://github.com/canonical/lxd/security/advisories/GHSA-jpmc-7p9c-4rxf
- web https://github.com/canonical/lxd/pull/12313
- web https://pkg.go.dev/vuln/GO-2024-3313
- web https://www.cve.org/CVERecord?id=CVE-2024-6219
- web https://github.com/canonical/lxd/commit/5cdc9a35b9c51e981b1e70330bde0413ccacc7fd
- web https://github.com/advisories/GHSA-jpmc-7p9c-4rxf