CVE-2020-28368: n/a vulnerability

CVE-2020-28368: Xen through 4.14.x allows guest OS administrators to obtain sensitive information (such as AES keys from ou...

Xen through 4.14.x allows guest OS administrators to obtain sensitive information (such as AES keys from outside the guest) via a side-channel attack on a power/energy monitoring interface, aka a "Platypus" attack. NOTE: there is only one logically independent fix: to change the access control for each such interface in Xen.

UnknownCVSS not scoredNot KEV-listedUpdatedAug 4, 2024, 16:33 UTC (UTC+00:00)

Security readout for executives and security teams

This Xen issue lets an administrator inside a guest virtual machine infer sensitive data outside that guest through a CPU power/energy side channel known as Platypus. The CVE cites examples such as AES keys. It matters most for organizations running Xen-based virtualization, especially where guest admins are not fully trusted. Exposure is likely where Xen through 4.14.x is used and guest operating system administrators can access affected power or energy monitoring interfaces. Multi-tenant hosting, lab clouds, and environments with delegated guest administration have the highest relevance. Treat as high priority for Xen-based shared infrastructure. The business risk is confidentiality loss across virtualization boundaries, including potential key exposure. Dedicated single-tenant Xen hosts are less urgent but should still be remediated through normal security maintenance. Mitigation focus: Review Xen XSA-351 and apply the vendor-supported Xen fix.; Restrict guest access to affected power or energy monitoring interfaces.; Apply relevant distribution updates from Debian, Fedora, or your Xen package source..

Prepared: Jun 5, 2026, 13:31 UTC (UTC+00:00)

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-2020-28368 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: Nov 10, 2020, 18:17 UTC (UTC+00:00)

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

7Source links

CVSS and timeline data

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

Source materials

CVE List V5 sourceCVE List V5
https://xenbits.xen.org/xsa/advisory-351.htmlCVE reference · x_refsource_MISC
https://platypusattack.com/CVE reference · x_refsource_MISC
https://www.zdnet.com/article/new-platypus-attack-can-steal-data-from-intel-cpus/CVE reference · x_refsource_MISC
FEDORA-2020-2684e0faddCVE reference · vendor-advisory, x_refsource_FEDORA
FEDORA-2020-d71fa5f0b9CVE reference · vendor-advisory, x_refsource_FEDORA
DSA-4804CVE reference · vendor-advisory, x_refsource_DEBIAN

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.