First published: Tue Dec 24 2013(Updated: )
Xen 3.0.3 through 4.1.x (possibly 4.1.6.1), 4.2.x (possibly 4.2.3), and 4.3.x (possibly 4.3.1) does not properly prevent access to hypercalls, which allows local guest users to gain privileges via a crafted application running in ring 1 or 2.
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
Xen Xen | =3.0.3 | |
Xen Xen | =3.0.4 | |
Xen Xen | =3.1.3 | |
Xen Xen | =3.1.4 | |
Xen Xen | =3.2.0 | |
Xen Xen | =3.2.1 | |
Xen Xen | =3.2.2 | |
Xen Xen | =3.2.3 | |
Xen Xen | =3.3.0 | |
Xen Xen | =3.3.1 | |
Xen Xen | =3.3.2 | |
Xen Xen | =3.4.0 | |
Xen Xen | =3.4.1 | |
Xen Xen | =3.4.2 | |
Xen Xen | =3.4.3 | |
Xen Xen | =3.4.4 | |
Xen Xen | =4.0.0 | |
Xen Xen | =4.0.1 | |
Xen Xen | =4.0.2 | |
Xen Xen | =4.0.3 | |
Xen Xen | =4.0.4 | |
Xen Xen | =4.1.0 | |
Xen Xen | =4.1.1 | |
Xen Xen | =4.1.2 | |
Xen Xen | =4.1.3 | |
Xen Xen | =4.1.4 | |
Xen Xen | =4.1.5 | |
Xen Xen | =4.1.6.1 | |
Xen Xen | =4.2.0 | |
Xen Xen | =4.2.1 | |
Xen Xen | =4.2.2 | |
Xen Xen | =4.2.3 | |
Xen Xen | =4.3.0 | |
Xen Xen | =4.3.1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.