Bug 957155 (CVE-2013-2016)

Summary: CVE-2013-2016 qemu: virtio: out-of-bounds config space access
Product: [Other] Security Response Reporter: Petr Matousek <pmatouse>
Component: vulnerabilityAssignee: Red Hat Product Security <security-response-team>
Status: CLOSED NOTABUG QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: unspecifiedCC: acathrow, amit.shah, areis, berrange, bsarathy, cfergeau, drjones, dwmw2, ehabkost, gleb, imammedo, itamar, jlieskov, knoel, lersek, minovotn, mkenneth, mrezanin, mtosatti, pbonzini, rhod, rjones, scottt.tw, virt-maint, virt-maint, xen-maint
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-08-24 14:13:48 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 956953, 957161    
Bug Blocks: 957189    

Description Petr Matousek 2013-04-26 13:27:56 UTC
A flaw was found in the way qemu 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.

References:

https://lists.gnu.org/archive/html/qemu-devel/2013-04/msg05013.html

Proposed upstream patch:

https://lists.gnu.org/archive/html/qemu-devel/2013-04/msg05254.html

Acknowledgements:                                  

This issue was found by Jason Wang of Red Hat.

Comment 1 Petr Matousek 2013-04-26 13:33:56 UTC
Statement:

Not vulnerable.

This issue does not affect the versions of kvm package as shipped with Red Hat Enterprise Linux 5 and qemu-kvm package as shipped with Red Hat Enterprise Linux 6.

Comment 2 Petr Matousek 2013-04-26 13:35:29 UTC
Created qemu tracking bugs for this issue

Affects: fedora-all [bug 957161]