LiveActive security incident?Get immediate response
CVE Record

CVE-2021-46768: Insufficient input validation in SEV firmware may allow an attacker to perform out-of-bounds memory reads w...

Insufficient input validation in SEV firmware may allow an attacker to perform out-of-bounds memory reads within the ASP boot loader, potentially leading to a denial of service.

MediumCVSS 5.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This is a medium-severity AMD server firmware issue affecting some 2nd and 3rd Gen EPYC platforms using SEV firmware. A local, low-privileged attacker could trigger out-of-bounds reads in the AMD Secure Processor boot loader, potentially causing denial of service rather than data theft or privilege escalation.

Executive priority

Treat this as a targeted infrastructure hardening item, not an emergency internet-facing incident. Prioritize data center and virtualization platforms because a denial of service on shared hosts can create business disruption even without evidence of remote exploitation.

Technical view

CVE-2021-46768 is CWE-125 insufficient input validation in AMD SEV firmware. The CVSS 3.1 vector is local, low complexity, low privileges, no user interaction, unchanged scope, and high availability impact. The provided sources describe possible out-of-bounds memory reads within the ASP boot loader leading to denial of service.

Likely exposure

Exposure is most relevant to organizations running AMD 2nd or 3rd Gen EPYC servers, especially virtualization hosts using SEV. The bundle lists affected versions only as “various,” so exact exposure requires checking platform firmware, AGESA, server OEM advisories, and AMD-SB-1032.

Exploitation context

The source bundle does not show CISA KEV listing or cited evidence of active exploitation. The CVSS vector requires local access with low privileges and no user interaction. Public evidence here supports denial-of-service concern, not confidentiality or integrity compromise.

Researcher notes

The bundle provides CVSS, CWE-125, affected EPYC generations, and AMD’s advisory URL, but not exact firmware version ranges or remediation text. Avoid over-scoping beyond AMD 2nd and 3rd Gen EPYC AGESA-related platforms until AMD or OEM details are verified.

Mitigation direction

  • Review AMD-SB-1032 and matching OEM server advisories for applicable firmware guidance.
  • Inventory AMD EPYC 2nd and 3rd Gen hosts and their AGESA or BIOS firmware versions.
  • Prioritize firmware updates for virtualization hosts or systems using SEV.
  • Restrict local access to affected hosts while firmware status is being confirmed.
  • Monitor AMD and OEM guidance for exact platform-specific fixes.

Validation and detection

  • Confirm whether servers use AMD 2nd or 3rd Gen EPYC processors.
  • Record BIOS, firmware, and AGESA versions from each potentially affected host.
  • Compare recorded versions against AMD-SB-1032 and OEM security advisories.
  • Check whether SEV is enabled or relied upon in virtualization workloads.
  • Document systems where version applicability remains unclear.
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-125: 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-46768 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:N/I:N/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
5.5CVSS 3.1MediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H1.83.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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.

CWE-125 · source CWE mapping

Out-of-bounds Read

Out-of-bounds Read represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.