Bug 1012554 (CVE-2013-4369) - CVE-2013-4369 xen: possible null dereference when parsing vif ratelimiting info (XSA-68)
Summary: CVE-2013-4369 xen: possible null dereference when parsing vif ratelimiting in...
Keywords:
Status: CLOSED NOTABUG
Alias: CVE-2013-4369
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 1017843
Blocks: 1012558
TreeView+ depends on / blocked
 
Reported: 2013-09-26 16:00 UTC by Vincent Danen
Modified: 2023-05-12 00:30 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-09-26 16:01:21 UTC
Embargoed:


Attachments (Terms of Use)

Description Vincent Danen 2013-09-26 16:00:05 UTC
The libxlu library function xlu_vif_parse_rate does not properly
handle inputs which consist solely of the '@' character, leading to a
NULL pointer dereference.

A toolstack which allows untrusted users to specify an arbitrary
configuration for the VIF rate can be subjected to a DOS.

The only known user of this library is the xl toolstack which does not
have a central long running daemon and therefore the impact is limited
to crashing the process which is creating the domain, which exists
only to service a single domain.


Acknowledgements:

Red Hat would like to thank the Xen project for reporting this issue.

Comment 1 Vincent Danen 2013-09-26 16:01:21 UTC
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 support for the libxl toolstack.

This issue does not affect Red Hat Enterprise Linux 6 and Red Hat Enterprise MRG 2.

Comment 2 Vincent Danen 2013-10-10 15:57:20 UTC
External References:

http://xenbits.xen.org/xsa/advisory-68.html

Comment 3 Vincent Danen 2013-10-10 15:58:45 UTC
Created xen tracking bugs for this issue:

Affects: fedora-all [bug 1017843]


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