CVE-2021-46766
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedImproper clearing of sensitive data in the ASP Bootloader may expose secret keys to a privileged attacker accessing ASP SRAM, potentially leading to a loss of confidentiality.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe ASP Bootloader fails to properly clear sensitive data, specifically secret keys, from SRAM memory after use. A privileged attacker with access to the ASP SRAM can read these uncleared cryptographic keys, resulting in loss of confidentiality.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< genoapi_1.0.0.4< genoapi_1.0.0.4< genoapi_1.0.0.4< genoapi_1.0.0.4< genoapi_1.0.0.4< genoapi_1.0.0.4< genoapi_1.0.0.4< genoapi_1.0.0.4CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the installed AMD Epyc processor modelRun 'dmidecode -t processor | grep -i "AMD Epyc"' or check system inventory to confirm the exact model numberAffected if The model is one of: 9654p, 9654, 9634, 9554p, 9554, 9534, 9474f, or 9454p
-
Determine the firmware version for the genoapi componentUse the system's firmware management tools (such as AMD's firmware update utilities, IPMI, or BIOS management interfaces) to query the installed firmware version. Look specifically for the 'genoapi' component version string.Affected if The genoapi version is displayed and is below version 1.0.0.4
-
Confirm the overall firmware baseline versionCheck the full system firmware/BIOS version for the AMD Epyc system using 'dmidecode -t bios' or the appropriate BMC/IPMI interface, noting any version information that includes the genoapi component.Affected if The firmware bundle containing genoapi is older than the version that includes genoapi_1.0.0.4
You are affected if you are running any of the listed AMD Epyc models (9654p, 9654, 9634, 9554p, 9554, 9534, 9474f, 9454p) with a firmware version where the genoapi component is older than version 1.0.0.4.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedImplement secure memory sanitization routines to overwrite all sensitive data, including cryptographic keys, in SRAM immediately after use. Verify that secret keys are not retained in memory after bootloader operations complete.
genoapi_1.0.0.4 or later
- Obtain the updated firmware (genoapi_1.0.0.4 or later) from AMD's official support website for your specific Epyc processor model
- Verify the firmware checksum and signature before applying
- Apply the firmware update using AMD's recommended update mechanism (typically via BMC/IPMI, AMD's firmware update utility, or platform-specific tools)
- Reboot the system as required by the firmware update process
- Verify the installed firmware version matches the fixed release
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-46766 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-46766 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data