Bug 1062331 - (CVE-2014-1896) CVE-2014-1896 xen: libvchan failure handling malicious ring indexes (xsa-86)
CVE-2014-1896 xen: libvchan failure handling malicious ring indexes (xsa-86)
Status: CLOSED NOTABUG
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
medium Severity medium
: ---
: ---
Assigned To: Red Hat Product Security
impact=moderate,public=20140206,repor...
: Security
Depends On: 1062335
Blocks: 1062332
  Show dependency treegraph
 
Reported: 2014-02-06 11:53 EST by Petr Matousek
Modified: 2014-02-09 20:02 EST (History)
11 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2014-02-06 11:55:01 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Petr Matousek 2014-02-06 11:53:58 EST
libvchan (a library for inter-domain communication) does not correctly handle unusual or malicious contents in the xenstore ring. A malicious guest can exploit this to cause a libvchan-using facility to read or write past the end of the ring.

libvchan-using facilities are vulnerable to denial of service and perhaps privilege escalation.

External reference:

http://seclists.org/oss-sec/2014/q1/264

Acknowledgements:

Red Hat would like to thank the Xen project for reporting this issue.
Comment 1 Petr Matousek 2014-02-06 11:55:01 EST
Statement:

Not vulnerable.

This issue does not affect the versions of the xen package as shipped with Red Hat Enterprise Linux 5 as it does not provide oxenstored.

This issue does not affect Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG 2.
Comment 2 Petr Matousek 2014-02-06 11:59:57 EST
Created xen tracking bugs for this issue:

Affects: fedora-all [bug 1062335]
Comment 3 Murray McAllister 2014-02-09 20:02:16 EST
This was assigned CVE-2014-1896: http://seclists.org/oss-sec/2014/q1/283

Note You need to log in before you can comment on or make changes to this bug.