First published: Mon May 13 2013(Updated: )
Xen 4.2.x and 4.1.x does not properly restrict access to IRQs, which allows local stub domain clients to gain access to IRQs and cause a denial of service via vectors related to "passed-through IRQs or PCI devices."
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
Xen xen-unstable | =4.1.0 | |
Xen xen-unstable | =4.1.1 | |
Xen xen-unstable | =4.1.2 | |
Xen xen-unstable | =4.1.3 | |
Xen xen-unstable | =4.1.4 | |
Xen xen-unstable | =4.1.5 | |
Xen xen-unstable | =4.2.0 | |
Xen xen-unstable | =4.2.1 | |
Xen xen-unstable | =4.2.2 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2013-1919 is considered to have a moderate severity level due to its ability to cause a denial of service.
To address CVE-2013-1919, upgrade to the latest version of Xen that has implemented the necessary security patches.
CVE-2013-1919 affects Xen versions 4.1.0 through 4.1.5 and 4.2.0 through 4.2.2.
No, CVE-2013-1919 can only be exploited locally by stub domain clients.
CVE-2013-1919 allows local attackers to gain unauthorized access to IRQs, leading to potential denial of service.