Skip to content
Noroxi
NVD / CVE Program· CNA mitre

CVE-2020-29483: An issue was discovered in Xen through 4.14.x.

MediumCVSS 6.5 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 26/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.37% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: xen (Alpine:v3.11) 4.13.2-r3; xen (Alpine:v3.13) 4.14.1-r0; xen (Debian:10) 4.11.4+57-g41a822c392-2.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to xen (Alpine:v3.11) 4.13.2-r3; xen (Alpine:v3.13) 4.14.1-r0; xen (Debian:10) 4.11.4+57-g41a822c392-2 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

An issue was discovered in Xen through 4.14.x. Xenstored and guests communicate via a shared memory page using a specific protocol. When a guest violates this protocol, xenstored will drop the connection to that guest. Unfortunately, this is done by just removing the guest from xenstored's internal management, resulting in the same actions as if the guest had been destroyed, including sending an @releaseDomain event. @releaseDomain events do not say that the guest has been removed. All watchers of this event must look at the states of all guests to find the guest that has been removed. When an @releaseDomain is generated due to a domain xenstored protocol violation, because the guest is still running, the watchers will not react. Later, when the guest is actually destroyed, xenstored will no longer have it stored in its internal data base, so no further @releaseDomain event will be sent. This can lead to a zombie domain; memory mappings of that guest's memory will not be removed, due to the missing event. This zombie domain will be cleaned up only after another domain is destroyed, as that will trigger another @releaseDomain event. If the device model of the guest that violated the Xenstore protocol is running in a stub-domain, a use-after-free case could happen in xenstored, after having removed the guest from its internal data base, possibly resulting in a crash of xenstored. A malicious guest can block resources of the host for a period after its own death. Guests with a stub domain device model can eventually crash xenstored, resulting in a more serious denial of service (the prevention of any further domain management operations). Only the C variant of Xenstore is affected; the Ocaml variant is not affected. Only HVM guests with a stubdom device model can cause a serious DoS.

Published
Dec 15, 2020
Updated
Jun 16, 2026
EPSS
0.3% · 31th percentile

Report tools

JSON

Action score

26

Monitor

Low priority for now.

CVSS
26 / 40 · 6.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.3%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2020-29483

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
xenxen
debiandebian linux
fedoraprojectfedora

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • debian debian linux10.0
  • fedoraproject fedora32
  • fedoraproject fedora33
  • xen xenup to 4.14.0 inclusive

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Alpine:v3.11xenbefore 4.13.2-r34.13.2-r3
Alpine:v3.13xenbefore 4.14.1-r04.14.1-r0
Debian:10xenbefore 4.11.4+57-g41a822c392-24.11.4+57-g41a822c392-2
Debian:12xenbefore 4.14.0+88-g1d1d1f5391-14.14.0+88-g1d1d1f5391-1
openSUSE:Leap 15.1xenbefore 4.12.4_06-lp151.2.36.14.12.4_06-lp151.2.36.1
openSUSE:Leap 15.2xenbefore 4.13.2_06-lp152.2.21.14.13.2_06-lp152.2.21.1
SUSE:HPE Helion OpenStack 8xenbefore 4.9.4_16-3.80.14.9.4_16-3.80.1
SUSE:Linux Enterprise High Performance Computing 15-ESPOSxenbefore 4.10.4_24-3.53.14.10.4_24-3.53.1
SUSE:Linux Enterprise Module for Basesystem 15 SP1xenbefore 4.12.4_06-3.40.14.12.4_06-3.40.1
SUSE:Linux Enterprise Module for Basesystem 15 SP2xenbefore 4.13.2_06-3.22.14.13.2_06-3.22.1
SUSE:Linux Enterprise Server 11 SP4-LTSSxenbefore 4.4.4_48-61.61.14.4.4_48-61.61.1
SUSE:Linux Enterprise Software Development Kit 12 SP5xenbefore 4.12.4_06-3.36.14.12.4_06-3.36.1
SUSE:OpenStack Cloud 7xenbefore 4.7.6_14-43.73.14.7.6_14-43.73.1
SUSE:OpenStack Cloud 9xenbefore 4.11.4_16-2.48.14.11.4_16-2.48.1

Same product

xen: all records

Other highest-scoring records for the same primary product.

  • CVE-2017-10921The grant-table feature in Xen through 4.8.x does not ensure sufficient type counts for a GNTMAP_device_map and GNTMAP_host_map mapping…
    41Plan
  • CVE-2017-10920The grant-table feature in Xen through 4.8.x mishandles a GNTMAP_device_map and GNTMAP_host_map mapping, when followed by only a…
    41Plan
  • CVE-2017-10918Xen through 4.8.x does not validate memory allocations during certain P2M operations, which allows guest OS users to obtain privileged host…
    41Plan

Published before and after this one in the same product

  • ← EarlierCVE-2020-29481Dec 15, 2020 · An issue was discovered in Xen through 4.14.x.
    35Monitor
  • ← EarlierCVE-2020-29482Dec 15, 2020 · An issue was discovered in Xen through 4.14.x.
    24Monitor
  • Later →CVE-2020-29484Dec 15, 2020 · An issue was discovered in Xen through 4.14.x.
    24Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
alpine:xen4.13.2-r3 · Alpine:v3.11Package registry (OSV)
debian:xen4.14.0+88-g1d1d1f5391-1 · Debian:12Package registry (OSV)
opensuse:xen4.12.4_06-lp151.2.36.1 · openSUSE:Leap 15.1Package registry (OSV)
suse:xen4.4.4_48-61.61.1 · SUSE:Linux Enterprise Server 11 SP4-LTSSPackage registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted

Impact can extend beyond the vulnerable component (scope changes).

Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Changed
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

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

nvd-primary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

c
free(dev->buf);/* ... another thread is still running ... */process(dev->buf);

Fixed

c
lock(&dev->lock);free(dev->buf);dev->buf = NULL;unlock(&dev->lock);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

References

All records