CVE-2013-2076: Infoleak

Published Aug 28, 2013

Updated

Xen 4.0.x, 4.1.x, and 4.2.x, when running on AMD64 processors, only save/restore the FOP, FIP, and FDP x87 registers in FXSAVE/FXRSTOR when an exception is pending, which allows one domain to determine portions of the state of floating point instructions of other domains, which can be leveraged to obtain sensitive information such as cryptographic keys, a similar vulnerability to CVE-2006-1056. NOTE: this is the documented behavior of AMD64 processors, but it is inconsistent with Intel processors in a security-relevant fashion that was not addressed by the kernels.

Affected Software

14 affected components

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

XEN Xen=4.2.1

XEN Xen=4.2.2

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

Event History

Aug 28, 2013

CVE Published

via MITRE·05:00 PM

Data Sourced

via MITRE·05:00 PM

Description

Frequently Asked Questions

What is the severity of CVE-2013-2076?

CVE-2013-2076 is considered a high severity vulnerability due to its potential to allow information leakage between domains.

How do I fix CVE-2013-2076?

To fix CVE-2013-2076, you should upgrade to a version of Xen that is not affected, such as 4.3.0 or later.

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

CVE-2013-2076 affects Xen versions 4.0.x, 4.1.x, and 4.2.x.

What could an attacker do with CVE-2013-2076?

An attacker can exploit CVE-2013-2076 to determine portions of the state of floating point instructions from other domains.

Is CVE-2013-2076 specific to any hardware architecture?

Yes, CVE-2013-2076 specifically affects Xen when running on AMD64 processors.