CVE-2013-2016
CVE-2013-2016 Vulnerability Analysis & Exploit Intelligence
A flaw was found in the way qemu v1.3.0 and later (virtio-rng) validates addresses when guest accesses the config space of a virtio device. If the virtio device has zero/small sized config space, such as virtio-rng, a privileged guest user could use this flaw to access the matching host's qemu address space and thus increase their privileges on the host.
Published Updated Sources: cvelistV5, redhat
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.
Exploitation
Unreported
no source claims exploitation
EPSS
1%
chance of exploitation in 30 days
CVSS base
Unscored
no source published a base score
Affected scope
The catalog records vendors and products as separate lists, not pairs, so which product belongs to which vendor is not something this page can say.
Vendors (1)
Products (1)
Detection
Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.
- Search application, proxy, and WAF logs for requests touching /small.
References
9 on the record
- security-tracker.debian.org/tracker/CVE-2013-2016
x_refsource_MISC
- bugzilla.redhat.com/show_bug.cgi?id=CVE-2013-2016
x_refsource_MISC
- access.redhat.com/security/cve/cve-2013-2016
x_refsource_MISC
- lists.opensuse.org/opensuse-security-announce/2014-05/msg00002.html
x_refsource_MISC
- www.openwall.com/lists/oss-security/2013/04/29/5
x_refsource_MISC
- www.openwall.com/lists/oss-security/2013/04/29/6
x_refsource_MISC
- www.securityfocus.com/bid/59541
x_refsource_MISC
- exchange.xforce.ibmcloud.com/vulnerabilities/83850
x_refsource_MISC
Elsewhere on this site
- qemuevery CVE for this vendor
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.