CVE-2013-0215

What it is

oxenstored in Xen 4.1.x, Xen 4.2.x, and xen-unstable does not properly consider the state of the Xenstore ring during read operations, which allows guest OS users to cause a denial of service (daemon crash and host-control outage, or memory consumption) or obtain sensitive control-plane data by leveraging guest administrative access.

At a glance

Exploitability

Can be exploited from the same network segment without logging in. Limited direct impact.

Exploit odds

0.6% chance of exploitation in the next 30 days (EPSS).

Fix

No patch or advisory is linked yet. Look at mitigations or restrict exposure.

Timeline

1. 2013-03-07 05:04 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-16 23:48 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 0.6% in the next 30 days (EPSS).
• Severity: 4.3 MEDIUM (CVSS).
• Fix: none linked yet, which raises it.

Details

Published

2013-03-07 05:04 UTC

Last modified

2026-06-16 23:48 UTC

Exploit probability

0.6% · EPSS, next 30 days

Weakness

CWE-264

Record status

Modified

Affected

• Xen 4.1.0
• Xen 4.1.1
• Xen 4.1.2
• Xen 4.1.3
• Xen 4.1.4
• Xen 4.2.0
• Xen 4.2.1

Attack profile CVSS 2.0 · 4.3

Attack vector

Adjacent network

Complexity

Medium

Authentication

None

Confidentiality

Partial

Integrity

None

Availability

Partial

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2013-0215.md and follow it. Check whether this project is affected by CVE-2013-0215. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge