CVE-2023-34327VulnerabilityPublished 5 Jan 2024Updated 3 Jun 2025

CVE-2023-34327: Xen · Vulnerability

Affects XenSource CVE Database V5

Mentioned vulnerabilities

Not known to be exploited · CVSS 5.5 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

5.5Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 15% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Attack Vector: Local
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 5 Jan 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

To mitigate CVE-2023-34327, European organizations should first verify if their Xen hypervisor deployments run on AMD CPUs with debugging extensions enabled and assess whether their environments use HVM or PV guests susceptible to this issue. Immediate steps include: 1) Applying any available Xen hypervisor patches or updates from the vendor that address this vulnerability once released. 2) Reviewing and potentially disabling or restricting the use of AMD CPU debugging extensions in virtualized guests if feasible, to reduce attack surface. 3) Implementing strict access controls to limit local or privileged access to virtual machines, minimizing the risk of exploitation by low-privileged users. 4) Monitoring hypervisor and VM logs for unusual debug mask states or breakpoint placements that could indicate exploitation attempts. 5) Testing failover and recovery procedures to ensure rapid restoration of services in case of DoS incidents. 6) Engaging with cloud or virtualization service providers to confirm their mitigation status if using hosted Xen environments. These measures go beyond generic advice by focusing on the specific AMD CPU debugging features and Xen guest types involved in the vulnerability.

Description

[This CNA information record relates to multiple CVEs; the text explains which aspects/vulnerabilities correspond to which CVE.] AMD CPUs since ~2014 have extensions to normal x86 debugging functionality. Xen supports guests using these extensions. Unfortunately there are errors in Xen's handling of the guest state, leading to denials of service.1) CVE-2023-34327 - An HVM vCPU can end up operating in the context of a previous vCPUs debug mask state.2) CVE-2023-34328 - A PV vCPU can place a breakpoint over the live GDT. This allows the PV vCPU to exploit XSA-156 / CVE-2015-8104 and lock up the CPU entirely.

Impact

For European organizations, the primary impact of CVE-2023-34327 is the risk of denial-of-service attacks against virtualized infrastructure running the Xen hypervisor on AMD CPUs. This can lead to service interruptions, affecting cloud service providers, data centers, and enterprises relying on Xen for virtualization. Critical services hosted on affected VMs could become unavailable, impacting business continuity and potentially causing financial and reputational damage. Since the vulnerability does not allow for privilege escalation or data leakage, the confidentiality and integrity of data remain intact. However, availability disruptions in sectors such as finance, healthcare, telecommunications, and government could have significant operational consequences. The lack of known exploits reduces immediate risk, but the presence of a known attack vector means that motivated attackers or insiders with local access could trigger these DoS conditions. Organizations using Xen in multi-tenant or public cloud environments should be particularly cautious, as denial-of-service could affect multiple customers or critical workloads.

Summary

CVE-2023-34327 is a medium-severity vulnerability affecting the Xen hypervisor, specifically related to its handling of AMD CPU debugging extensions introduced since approximately 2014. Xen supports guest virtual machines (VMs) that utilize these CPU debugging features. However, errors in managing the guest state lead to potential denial-of-service (DoS) conditions. The vulnerability manifests in two related issues: first, an HVM (Hardware Virtual Machine) virtual CPU (vCPU) may operate with a debug mask state leftover from a previous vCPU, potentially causing inconsistent or erroneous behavior. Second, a PV (paravirtualized) vCPU can place breakpoints over the live Global Descriptor Table (GDT), exploiting a previously known vulnerability (XSA-156 / CVE-2015-8104) to lock up the CPU entirely. These flaws do not compromise confidentiality or integrity but can disrupt availability by causing system hangs or crashes. The CVSS 3.1 base score is 5.5, reflecting a local attack vector requiring low privileges but no user interaction, with impact limited to availability. No known exploits are reported in the wild, and no patches are linked in the provided data, indicating that mitigation may require vendor updates or configuration changes. The vulnerability affects Xen hypervisor deployments running on AMD CPUs with these debugging extensions enabled, which are common in many server and cloud environments using Xen virtualization technology.

References

xenbits.xenproject.org/xsa/advisory-444.html (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 4 Jul 2025, 04:43 UTC

Technical details

References

Community reviews

Related threats