Security readout for executives and security teams
Plain-English summary
This AMD EPYC firmware issue could let an attacker who already has local access corrupt AMD Secure Processor OS memory. The main business risk is loss of system integrity or availability, not data disclosure. It is high severity, but the source bundle does not show active exploitation.
Executive priority
Prioritize remediation for EPYC servers supporting critical workloads or shared environments. This is not presented as actively exploited, but firmware-level integrity and availability impact can create high operational risk if an attacker first gains local execution.
Technical view
CVE-2021-46779 is insufficient input validation in the SVC_ECC_PRIMITIVE system call. A compromised user application or ABL may corrupt ASP OS memory. CVSS 3.1 is 7.1: local attack vector, low complexity, low privileges, no user interaction, high integrity and availability impact, no confidentiality impact.
Likely exposure
Exposure is most relevant to systems using AMD 1st, 2nd, or 3rd Gen EPYC platforms with affected AGESA firmware. The bundle does not provide exact vulnerable firmware version ranges, so inventory must be checked against AMD-SB-1032 and OEM firmware advisories.
Exploitation context
The provided sources support local, low-privilege exploitation conditions after a user application or ABL is compromised. The bundle marks KEV as false and provides no evidence of active exploitation. Treat this as a platform firmware integrity and availability risk, not a remote network exposure.
Researcher notes
The evidence is limited to AMD and CVE records. Exact affected AGESA versions and fixed builds are not included in the supplied bundle. Avoid assuming exploit maturity. Focus research on firmware provenance, platform inventory, and whether local execution paths exist on candidate systems.
Mitigation direction
- Review AMD-SB-1032 and applicable OEM firmware advisories.
- Update BIOS or firmware packages that include corrected AGESA versions.
- Prioritize internet-facing, multi-tenant, and high-value EPYC servers.
- Restrict local access and reduce untrusted code execution on affected hosts.
- Track vendor release notes for exact platform-specific remediation guidance.
Validation and detection
- Inventory AMD EPYC generation and current BIOS or AGESA firmware levels.
- Compare firmware versions against AMD-SB-1032 and OEM advisories.
- Confirm whether affected hosts allow low-privilege local code execution.
- Validate update deployment through standard firmware attestation or asset tooling.
- Record exceptions where vendor firmware is unavailable or unsupported.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-787: 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 lookupCVE-2021-46779 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.1 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
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.
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H1.85.2Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.1HighVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://www.amd.com/en/corporate/product-security/bulletin/AMD-SB-1032CVE reference · vendor-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Out-of-bounds Write
Out-of-bounds Write represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.