LiveActive security incident?Get immediate response
CVE Record

CVE-2021-46771: Insufficient validation of addresses in AMD Secure Processor (ASP) firmware system call may potentially lea...

Insufficient validation of addresses in AMD Secure Processor (ASP) firmware system call may potentially lead to arbitrary code execution by a compromised user application.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

AMD describes a flaw in Secure Processor firmware where a compromised user application could potentially trigger arbitrary code execution. The affected product information provided names 3rd Gen AMD EPYC. No CVSS score, vendor fix detail, or active exploitation evidence is included in the supplied bundle.

Executive priority

Treat this as a targeted firmware-risk review, not an internet-wide emergency based on available evidence. Prioritize EPYC server inventory and vendor firmware guidance because potential code execution in security processor firmware can carry high business impact.

Technical view

CVE-2021-46771 is a CWE-20 input validation issue involving insufficient address validation in an AMD Secure Processor firmware system call. The stated impact is potential arbitrary code execution from a compromised user application. The source bundle identifies 3rd Gen AMD EPYC as affected, with versions unspecified.

Likely exposure

Exposure appears limited to environments running affected 3rd Gen AMD EPYC platforms with vulnerable ASP firmware. The bundle does not identify specific firmware versions, server models, operating systems, or OEM BIOS packages.

Exploitation context

The provided description requires a compromised user application as the starting point. KEV is false, and the bundle provides no evidence of active exploitation, public exploit availability, or exploitation at scale.

Researcher notes

Evidence is sparse: no CVSS vector, no named vulnerable firmware versions, and no detailed fix text is present in the supplied bundle. Analysis should stay tied to AMD-SB-1021, CVE metadata, and OEM firmware mapping.

Mitigation direction

  • Check AMD Security Bulletin AMD-SB-1021 for vendor guidance.
  • Check server OEM advisories for matching BIOS or firmware updates.
  • Prioritize affected EPYC systems that run untrusted workloads.
  • Strengthen controls that prevent local user application compromise.
  • Track asset firmware versions until affected versions are clarified.

Validation and detection

  • Inventory systems using 3rd Gen AMD EPYC processors.
  • Record current BIOS, PSP, and firmware package versions.
  • Compare inventory against AMD-SB-1021 and OEM advisories.
  • Confirm whether vendor guidance names the installed firmware as affected.
  • Document any systems where version exposure remains unresolved.
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
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-46771 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
2Source 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
AMD3rd Gen AMD EPYC™unspecifiedListed
Weakness

CWE details

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

CWE-20 · source CWE mapping

Improper Input Validation

Improper Input Validation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.