LiveActive security incident?Get immediate response
CVE Record

CVE-2013-1922: qemu-nbd in QEMU, as used in Xen 4.2.x, determines the format of a raw disk image based on the header, whic...

qemu-nbd in QEMU, as used in Xen 4.2.x, determines the format of a raw disk image based on the header, which allows local guest OS administrators to read arbitrary files on the host by modifying the header to identify a different format, which is used when the guest is restarted, a different vulnerability than CVE-2008-2004.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

A guest administrator on an affected Xen/QEMU setup could manipulate a virtual disk header so qemu-nbd treats a raw image as another format after restart. That could let the guest read files from the host, creating a virtualization boundary breach. The provided sources do not give a CVSS score or evidence of active exploitation. Exposure appears limited to environments using affected QEMU qemu-nbd behavior, specifically noted with Xen 4.2.x, where guest disk format is not explicitly specified. Risk is highest for multi-tenant virtualization or hosting where guest administrators are not trusted by the host operator. Prioritize if the organization runs old Xen/QEMU virtualization for customers, labs, or tenant-isolated workloads. The business issue is possible host file exposure from a guest admin. Legacy or unsupported platforms should be updated or isolated promptly. Mitigation focus: Check current vendor guidance for QEMU, Xen, and distribution-specific packages.; Apply relevant QEMU or Xen updates from supported vendor channels.; Explicitly specify guest disk image format where platform tooling supports it..

Prepared

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2013-1922 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
1Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.