LibvirtApplication · Redhat
CVE-2013-1962
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe remoteDispatchStoragePoolListAllVolumes function in the storage pool manager in libvirt 1.0.5 allows remote attackers to cause a denial of service (file descriptor consumption) via a large number of requests "to list all volumes for the particular pool."
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA remote denial of service vulnerability in libvirt 1.0.5 where the remoteDispatchStoragePoolListAllVolumes function in the storage pool manager consumes file descriptors without proper cleanup, allowing remote attackers to cause file descriptor exhaustion via a large number of requests to list volumes for a storage pool.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
LibvirtApplication
= 1.0.5CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- None
- Integrity
- None
- Availability
- Partial
AV:N/AC:L/Au:N/C:N/I:N/A:P
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed libvirt versionRun 'rpm -q libvirt' or 'virsh --version' and 'libvirtd --version' to determine the exact version of libvirt installed on the systemAffected if The installed version is exactly 1.0.5 (note: other versions may have similar issues but only 1.0.5 is explicitly listed as affected)
-
Verify libvirtd daemon is runningRun 'systemctl status libvirtd' or 'ps aux | grep libvirtd' to check if the libvirt daemon is activeAffected if The libvirtd daemon is running and serving remote connections (the vulnerability is only exploitable via the remote API)
-
Confirm remote API access is enabledCheck /etc/libvirt/libvirtd.conf for 'listen_tls' and 'listen_tcp' settings, and check if the daemon is bound to a network interface (netstat -tlnp | grep libvirtd)Affected if Remote TCP access is enabled (listen_tcp = 1) or TLS is configured without proper access restrictions, exposing the API to network attackers
-
Check for configured storage poolsRun 'virsh pool-list --all' or 'virsh pool-list' to enumerate any defined storage pools in libvirtAffected if Storage pools exist (the vulnerability is triggered when attackers repeatedly request volume listings from an existing pool)
You are affected if libvirt version 1.0.5 is installed AND the remote API is accessible on the network AND storage pools are configured, enabling remote attackers to exhaust file descriptors through repeated volume listing requests.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate libvirt to a patched version that properly manages file descriptors. Additionally, implement network access controls and rate limiting on the libvirt remote API to limit exposure to unauthenticated remote attackers.
Fix this in Libvirt
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-1962 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2013-1962 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data