LiveActive security incident?Get immediate response
CVE Record

CVE-2021-46767: Insufficient input validation in the ASP may allow an attacker with physical access, unauthorized write acc...

Insufficient input validation in the ASP may allow an attacker with physical access, unauthorized write access to memory potentially leading to a loss of integrity or denial of service.

MediumCVSS 6.1Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2021-46767 is an AMD EPYC platform firmware issue in the AMD Secure Processor. A person with physical access may be able to write to memory without authorization, risking system integrity or denial of service. The public bundle rates it medium, with high integrity and availability impact but physical access required.

Executive priority

Treat this as a moderate firmware risk. It is unlikely to drive emergency remote-response work, but it should be included in server firmware maintenance, especially for EPYC systems outside tightly controlled facilities.

Technical view

The issue is insufficient input validation in AMD ASP/AGESA affecting listed AMD 2nd Gen and 3rd Gen EPYC platforms. CVSS 3.1 is 6.1 with physical attack vector, low complexity, no privileges, no user interaction, no confidentiality impact, and high integrity and availability impact.

Likely exposure

Exposure is most likely in servers using AMD 2nd or 3rd Gen EPYC platforms with AGESA firmware versions covered by AMD-SB-1032. Systems in controlled datacenters have reduced practical exposure, but shared, edge, lab, or physically accessible environments deserve faster review.

Exploitation context

The provided sources do not show CISA KEV listing or active exploitation. The CVSS vector requires physical access, so this is not described as a remote internet-facing issue. Impact still matters where attackers, insiders, contractors, or untrusted users can access hardware.

Researcher notes

The bundle identifies CWE-20 and physical access memory-write risk, but does not include exact vulnerable AGESA build ranges or fixed versions. Validate against AMD-SB-1032 and OEM mappings before declaring systems affected or remediated.

Mitigation direction

  • Review AMD-SB-1032 and OEM firmware guidance for affected EPYC platforms.
  • Update BIOS/firmware/AGESA through approved server vendor channels where applicable.
  • Prioritize physically accessible, shared, colocated, or edge systems first.
  • Maintain datacenter physical access controls and tamper monitoring.
  • Track AMD and OEM advisories for fixed firmware details.

Validation and detection

  • Inventory AMD 2nd Gen and 3rd Gen EPYC servers.
  • Record BIOS, firmware, and AGESA versions from hardware management tooling.
  • Compare versions against AMD-SB-1032 and OEM advisories.
  • Confirm updates were applied through post-change firmware inventory.
  • Review physical access logs for higher-risk server locations.
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-20: 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-46767 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
6.1 (3.1)
Known Exploited
No
Published

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

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
6.1CVSS 3.1MediumCVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H0.95.2Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

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

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
AMD2nd Gen EPYCAGESA, variousunaffected
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.