LiveActive security incident?Get immediate response
CVE Record

CVE-2021-26343: Insufficient validation in ASP BIOS and DRTM commands may allow malicious supervisor x86 software to disclo...

Insufficient validation in ASP BIOS and DRTM commands may allow malicious supervisor x86 software to disclose the contents of sensitive memory which may result in information disclosure.

MediumCVSS 5.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This flaw could let already-privileged local software on affected AMD 3rd Gen EPYC systems read sensitive memory through insufficiently validated ASP BIOS and DRTM commands. It is not a remote break-in issue, but it matters on servers that process high-value secrets or run untrusted workloads.

Executive priority

Treat this as a targeted firmware hygiene issue, not an emergency internet-facing incident. Prioritize high-value EPYC servers and environments where local privileged compromise could expose sensitive memory.

Technical view

CVE-2021-26343 is an information disclosure issue in AGESA affecting AMD 3rd Gen EPYC, tied to insufficient validation of ASP BIOS and DRTM commands. CVSS 3.1 is 5.5: local attack vector, low complexity, low privileges, no user interaction, high confidentiality impact only.

Likely exposure

Exposure is likely limited to AMD 3rd Gen EPYC platforms running affected AGESA/BIOS versions. The source bundle lists versions only as “various,” so exact exposure requires checking AMD and OEM firmware guidance for each server model.

Exploitation context

The supplied sources do not show CISA KEV listing, active exploitation, or public weaponization. The vulnerability requires local privileged or supervisor-level x86 software, so risk rises after endpoint or host compromise rather than from the internet directly.

Researcher notes

Key evidence gaps are exact vulnerable AGESA builds, OEM-specific fixed BIOS versions, and any practical exploitation details. Avoid assuming broader AMD product impact beyond the supplied affected product statement.

Mitigation direction

  • Review AMD-SB-1032 and OEM advisories for affected AGESA or BIOS versions.
  • Update affected 3rd Gen EPYC server BIOS or firmware using vendor-approved packages.
  • Prioritize systems handling credentials, encryption keys, regulated data, or multi-tenant workloads.
  • Restrict local administrative access and untrusted kernel-level drivers on EPYC hosts.
  • Track vendor guidance if exact firmware applicability is unclear.

Validation and detection

  • Inventory AMD 3rd Gen EPYC systems and record current BIOS and AGESA versions.
  • Compare firmware versions against AMD-SB-1032 and server OEM security advisories.
  • Confirm firmware updates were successfully applied and remain supported by the OEM.
  • Review privileged software, drivers, and hypervisor components allowed on affected hosts.
  • Check vulnerability management data for CVE-2021-26343 coverage and exceptions.
Prepared
Confidence
medium
Sources
3

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.

cwe · low confidence lookup

CWE-668: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-26343 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
Medium
CVSS
5.5 (3.1)
Known Exploited
No
Published

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

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.

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

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.5CVSS 3.1MediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N1.83.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.5Medium
CVSS 3.1 vector shape for CVE-2021-26343Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
AMD3rd Gen EPYCAGESA, variousunaffected
Weakness

CWE details

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

CWE-668 · source CWE mapping

Exposure of Resource to Wrong Sphere

Exposure of Resource to Wrong Sphere represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.