LiveActive security incident?Get immediate response
CVE Record

CVE-2018-8935: The Promontory chipset, as used in AMD Ryzen and Ryzen Pro platforms, has a backdoor in the ASIC, aka CHIME...

The Promontory chipset, as used in AMD Ryzen and Ryzen Pro platforms, has a backdoor in the ASIC, aka CHIMERA-HW.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2018-8935 describes an alleged hardware backdoor named CHIMERA-HW in the Promontory chipset used by some AMD Ryzen and Ryzen Pro platforms. The provided record has no CVSS score, no precise affected versions, and no KEV listing, so urgency depends on whether your fleet contains those chipsets.

Executive priority

Handle as a targeted exposure review, not an emergency response, based on the provided evidence. Prioritize inventory and vendor confirmation for any business-critical systems using Ryzen or Ryzen Pro platforms with Promontory chipsets.

Technical view

The CVE record identifies a Promontory chipset ASIC issue, described as CHIMERA-HW, affecting AMD Ryzen and Ryzen Pro platforms. The source bundle does not provide CWE mapping, CPEs, affected model lists, exploit prerequisites, or confirmed remediation details. Treat the evidence as incomplete and validate against AMD and system-OEM guidance.

Likely exposure

Exposure is most plausible in endpoints or servers using AMD Ryzen or Ryzen Pro platforms with the Promontory chipset. The bundle does not identify exact motherboard, system, firmware, or chipset revisions, so inventory confirmation is required before assigning business impact.

Exploitation context

The bundle does not show CISA KEV listing or cited evidence of active exploitation. Public references include CTS-related material, Trail of Bits analysis, and AMD's technical assessment, but the provided bundle does not establish exploit-in-the-wild status.

Researcher notes

The public CVE metadata is sparse: no CVSS, CWE, CPE, precise affected versions, or patch details are included. Analysis should distinguish the allegation and third-party assessments from vendor-confirmed impact. Avoid broad conclusions until AMD or OEM guidance maps exposure to specific products.

Mitigation direction

  • Check AMD and OEM advisories for confirmed guidance and firmware status.
  • Inventory Ryzen and Ryzen Pro systems for Promontory chipset presence.
  • Do not assume all AMD systems are affected without chipset validation.
  • Track vendor statements before making hardware replacement decisions.
  • Document compensating controls while awaiting vendor-confirmed remediation.

Validation and detection

  • Identify assets running AMD Ryzen or Ryzen Pro platforms.
  • Confirm whether each platform uses a Promontory chipset.
  • Review AMD's assessment and applicable OEM security advisories.
  • Record firmware, motherboard, and chipset revisions for affected candidates.
  • Monitor CVE and vendor references for remediation updates.
Prepared
Confidence
medium
Sources
6

Public sources used

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-2018-8935 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
5Source 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.