CVE-2013-1920: Use After Free

Published Apr 12, 2013

Updated

Xen 4.2.x, 4.1.x, and earlier, when the hypervisor is running "under memory pressure" and the Xen Security Module (XSM) is enabled, uses the wrong ordering of operations when extending the per-domain event channel tracking table, which causes a use-after-free and allows local guest kernels to inject arbitrary events and gain privileges via unspecified vectors.

Affected Software

29 affected components

XEN Xen=3.0.2

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.2.0

XEN Xen=4.2.1

Remediation

Patch Available

http://lists.xen.org/archives/html/xen-announce/2013-04/msg00000.html

Event History

Apr 12, 2013

CVE Published

via MITRE·10:00 PM

Data Sourced

via MITRE·10:00 PM

Description

Frequently Asked Questions

What is the severity of CVE-2013-1920?

CVE-2013-1920 has a medium severity level due to its potential to allow local guest kernels to inject malicious code.

How do I fix CVE-2013-1920?

Fixing CVE-2013-1920 involves updating the Xen hypervisor to a version that is patched against the vulnerability.

What versions of Xen are affected by CVE-2013-1920?

CVE-2013-1920 affects Xen versions 4.2.x, 4.1.x, and earlier, including versions down to 3.0.2.

Can CVE-2013-1920 be exploited remotely?

CVE-2013-1920 cannot be exploited remotely, as it requires local access to the affected guest kernel.

What impact does CVE-2013-1920 have on system security?

CVE-2013-1920 can lead to unauthorized access and privilege escalation if exploited by a local attacker.