CVE-2014-1447 json
Race condition in the virNetServerClientStartKeepAlive function in libvirt before 1.2.1 allows remote attackers to cause a denial of servic…
published 12y ago modified 4mo ago also EUVD-2014-1523
- cvss
- 3.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.3%
- EPSS 2.3% chance of exploitation in 30 days, percentile 83%
- public exploits
- 0
- none known
Summary
Race condition in the virNetServerClientStartKeepAlive function in libvirt before 1.2.1 allows remote attackers to cause a denial of service (libvirtd crash) by closing a connection before a keepalive response is sent.
Patch / fix
- libvirt Debian 14, Debian 13, Debian 12 1.2.1-1
debian advisories DEBIAN-CVE-2014-1447
- libvirt RHEL 6 0.10.2-29.el6_5.3
- libvirt-client RHEL 6 0.10.2-29.el6_5.3
- libvirt-python RHEL 6 0.10.2-29.el6_5.3
- libvirt-lock-sanlock RHEL 6 0.10.2-29.el6_5.3
red hat advisories RHSA-2014:0103
- libvirt openSUSE Tumbleweed 2.5.0-1.1
opensuse advisories openSUSE-SU-2024:10209-1
Is CVE-2014-1447 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2014-1447 updated cvss 3.3
libvirt: denial of service with keepalive
-
Red Hat Enterprise Linux 7 libvirt, libvirt-nss, libvirt-libs, libvirt-admin, libvirt-client, libvirt-daemon, +24 moreaffected: no fix available
-
Red Hat Enterprise Linux Desktop (v. 6) libvirt 0.10.2-29.el6_5.3, libvirt-client 0.10.2-29.el6_5.3, libvirt-python 0.10.2-29.el6_5.3 Red Hat Enterprise Linux Desktop Optional (v. 6) libvirt 0.10.2-29.el6_5.3, libvirt-lock-sanlock 0.10.2-29.el6_5.3 Red Hat Enterprise Linux HPC Node (v. 6) libvirt 0.10.2-29.el6_5.3, libvirt-client 0.10.2-29.el6_5.3, libvirt-python 0.10.2-29.el6_5.3 Red Hat Enterprise Linux HPC Node Optional (v. 6) libvirt 0.10.2-29.el6_5.3, libvirt-lock-sanlock 0.10.2-29.el6_5.3 Red Hat Enterprise Linux Server (v. 6) libvirt 0.10.2-29.el6_5.3, libvirt-client 0.10.2-29.el6_5.3, libvirt-python 0.10.2-29.el6_5.3 Red Hat Enterprise Linux Server Optional (v. 6) libvirt 0.10.2-29.el6_5.3, libvirt-lock-sanlock 0.10.2-29.el6_5.3fixed: vendor fix RHSA-2014:0103
+2 more productsfewer
Red Hat Enterprise Linux Workstation (v. 6) libvirt 0.10.2-29.el6_5.3, libvirt-client 0.10.2-29.el6_5.3, libvirt-python 0.10.2-29.el6_5.3 Red Hat Enterprise Linux Workstation Optional (v. 6) libvirt 0.10.2-29.el6_5.3, libvirt-lock-sanlock 0.10.2-29.el6_5.3 -
Red Hat Enterprise Linux 5 libvirtnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
2.34% chance of exploitation in the next 30 days, higher than 83% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 3.3 | AV:A/AC:L/Au:N/C:N/I:N/A:P |
Classification
- Weakness
-
- CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization
References
-
ubuntu.com
/usn/USN-2093-1
vendor-advisory
-
debian.org
/security/2014/dsa-2846
vendor-advisory
-
security.gentoo.org
/glsa/glsa-201412-04.xml
vendor-advisory
-
lists.opensuse.org
/opensuse-updates/2014-02/msg00060.html
vendor-advisory
-
rhn.redhat.com
/errata/RHSA-2014-0103.html
vendor-advisory
-
lists.opensuse.org
/opensuse-updates/2014-02/msg00062.html
vendor-advisory
-
bugzilla.redhat.com
/show_bug.cgi?id=1047577
vendor-advisory
-
secunia.com
/advisories/56446
third-party-advisory
- libvirt.org /news.html
-
secunia.com
/advisories/60895
third-party-advisory
-
secunia.com
/advisories/56321
third-party-advisory
-
securitytracker.com
/id/1029695
vdb-entry
Sources
- CVE List CVE-2014-1447
- NVD CVE-2014-1447
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.