CVE-2016-2858: Medium severity Qemu Qemu vulnerability
Qemu emulator built with the Pseudo Random Number Generator(PRNG) back-end support is vulnerable to an arbitrary stack based allocation and memory corruption via random bytes issue. It could occur when a guest requests for entropy for random number generation.
A user/process inside guest could use this flaw to crash the Qemu process resulting in DoS.
Upstream patch: --------------- -> http://git.qemu.org/?p=qemu.git;a=commit;h=60253ed1e6ec6d8e5ef2efe7bf755f475
Reference: ---------- -> http://www.openwall.com/lists/oss-security/2016/03/04/1
Other sources
QEMU, when built with the Pseudo Random Number Generator (PRNG) back-end support, allows local guest OS users to cause a denial of service (process crash) via an entropy request, which triggers arbitrary stack based allocation and memory corruption.
— MITRE
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Patch 60253ed1e6ec6d8e5ef2efe7bf755f475
Event History
Frequently Asked Questions
What is the severity of CVE-2016-2858?
CVE-2016-2858 is considered a medium severity vulnerability due to its potential for memory corruption.
How do I fix CVE-2016-2858?
To fix CVE-2016-2858, users should upgrade to a version of QEMU later than 2.5.1.1 that resolves this vulnerability.
What impact does CVE-2016-2858 have on systems?
CVE-2016-2858 can lead to arbitrary stack-based memory corruption, potentially allowing an attacker to execute arbitrary code.
Which software is affected by CVE-2016-2858?
CVE-2016-2858 affects QEMU versions up to and including 2.5.1.1, as well as specific versions of Ubuntu and Debian Linux.
Who can exploit CVE-2016-2858?
An attacker with access to a guest environment can exploit CVE-2016-2858 by requesting entropy for random number generation.