# CVE-2013-2076: Information disclosure in n/a

> A local attacker in a Xen guest can read floating-point state from other guests, potentially exposing sensitive data like cryptographic keys.

- **Severity:** Medium 4.3 (`AV:A/AC:H/Au:S/C:C/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 Aug 2013
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2013-2076, GHSA-86c3-896f-hgp9

## What is CVE-2013-2076?

CVE-2013-2076 is a medium-severity vulnerability in Xen Xen, published on 28 Aug 2013. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2013-2076?

It affects 1 product.


Products: Xen Xen.

## How do I fix CVE-2013-2076?

Apply the vendor's patch.

## Is CVE-2013-2076 being exploited?

There is no known exploitation of CVE-2013-2076 in the wild and no public exploit code.

## Other vulnerabilities in Xen Xen

- [CVE-2017-10912](https://insights.sbomify.com/CVE-2017-10912/): Privilege escalation in n/a (critical 10.0)
- [CVE-2017-10918](https://insights.sbomify.com/CVE-2017-10918/): Memory corruption in n/a (critical 10.0)
- [CVE-2017-10920](https://insights.sbomify.com/CVE-2017-10920/): Memory corruption in n/a (critical 10.0)
- [CVE-2017-10921](https://insights.sbomify.com/CVE-2017-10921/): Memory corruption in n/a (critical 10.0)
- [CVE-2025-27466](https://insights.sbomify.com/CVE-2025-27466/): Mutiple vulnerabilities in the Viridian interface (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-2076 and fix it if it is affected.

What it is: CVE-2013-2076 is a medium-severity vulnerability in Xen Xen, published on 28 Aug 2013. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2013-2076 in the wild and no public exploit code.

Affected product: Xen Xen. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2013-2076/ (Markdown: https://insights.sbomify.com/CVE-2013-2076/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2013-2076
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2013-2076
- OSV: https://osv.dev/vulnerability/CVE-2013-2076

---
From sbomify Insights: https://insights.sbomify.com/CVE-2013-2076/
Summaries are generated and may contain mistakes; the official description above is the record.