CVE-2021-46766: Improper clearing of sensitive data in the ASP Bootloader may expose secret keys to a privileged attacker accessing ASP SRAM, potentially…
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.22% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: kernel-firmware (openSUSE:Leap 15.5) 20230724-150500.3.9.1; kernel-firmware (openSUSE:Leap Micro 5.3) 20220509-150400.4.25.1; kernel-firmware (SUSE:Linux Enterprise High Performance Computing 15 SP1-LTSS) 20200107-150100.3.40.1.
- Severity is disputed: the assigning authority (CNA) scores it 2.5, NVD 5.5.
Low priority for now. Upgrade to kernel-firmware (openSUSE:Leap 15.5) 20230724-150500.3.9.1; kernel-firmware (openSUSE:Leap Micro 5.3) 20220509-150400.4.25.1; kernel-firmware (SUSE:Linux Enterprise High Performance Computing 15 SP1-LTSS) 20200107-150100.3.40.1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Improper 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.
- Published
- Nov 14, 2023
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 13th percentile
- CWE
- CWE-459
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CNA vs NVD score
- NVD
- 5.5
- CNA · AMD
- 2.5
- 3.0 point gap
CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:L/I:N/A:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| amd | epyc 9654p firmware | cpe:2.3:o:amd:epyc_9654p_firmware |
| amd | epyc 9654p | cpe:2.3:h:amd:epyc_9654p |
| amd | epyc 9654 firmware | cpe:2.3:o:amd:epyc_9654_firmware |
| amd | epyc 9654 | cpe:2.3:h:amd:epyc_9654 |
| amd | epyc 9634 firmware | cpe:2.3:o:amd:epyc_9634_firmware |
| amd | epyc 9634 | cpe:2.3:h:amd:epyc_9634 |
| amd | epyc 9554p firmware | cpe:2.3:o:amd:epyc_9554p_firmware |
| amd | epyc 9554p | cpe:2.3:h:amd:epyc_9554p |
| amd | epyc 9554 firmware | cpe:2.3:o:amd:epyc_9554_firmware |
| amd | epyc 9554 | cpe:2.3:h:amd:epyc_9554 |
| amd | epyc 9534 firmware | cpe:2.3:o:amd:epyc_9534_firmware |
| amd | epyc 9534 | cpe:2.3:h:amd:epyc_9534 |
and 44 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- amd epyc 9124 firmwarebefore genoapi_1.0.0.4
- amd epyc 9174f firmwarebefore genoapi_1.0.0.4
- amd epyc 9184x firmwarebefore genoapi_1.0.0.4
- amd epyc 9224 firmwarebefore genoapi_1.0.0.4
- amd epyc 9254 firmwarebefore genoapi_1.0.0.4
- amd epyc 9274f firmwarebefore genoapi_1.0.0.4
- amd epyc 9334 firmwarebefore genoapi_1.0.0.4
- amd epyc 9354 firmwarebefore genoapi_1.0.0.4
- amd epyc 9354p firmwarebefore genoapi_1.0.0.4
- amd epyc 9374f firmwarebefore genoapi_1.0.0.4
- amd epyc 9384x firmwarebefore genoapi_1.0.0.4
- amd epyc 9454 firmwarebefore genoapi_1.0.0.4
- amd epyc 9454p firmwarebefore genoapi_1.0.0.4
- amd epyc 9474f firmwarebefore genoapi_1.0.0.4
- amd epyc 9534 firmwarebefore genoapi_1.0.0.4
- amd epyc 9554 firmwarebefore genoapi_1.0.0.4
- amd epyc 9554p firmwarebefore genoapi_1.0.0.4
- amd epyc 9634 firmwarebefore genoapi_1.0.0.4
- amd epyc 9654 firmwarebefore genoapi_1.0.0.4
- amd epyc 9654p firmwarebefore genoapi_1.0.0.4
Versions reported by the vendor
Affected version ranges reported by the assigning authority (AMD). Independent of NVD's CPE analysis and usually ahead of it.
AMD 4th Gen AMD EPYC™ Processors
- variousaffected
AMD AMD EPYC™ Embedded 9003
- variousaffected
AMD Ryzen™ Threadripper™ PRO 3000WX Series Processors “Chagall” WS
- variousaffected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| openSUSE:Leap 15.5 | kernel-firmware | before 20230724-150500.3.9.1 | 20230724-150500.3.9.1 |
| openSUSE:Leap Micro 5.3 | kernel-firmware | before 20220509-150400.4.25.1 | 20220509-150400.4.25.1 |
| SUSE:Linux Enterprise High Performance Computing 15 SP1-LTSS | kernel-firmware | before 20200107-150100.3.40.1 | 20200107-150100.3.40.1 |
| SUSE:Linux Enterprise High Performance Computing 15 SP3-ESPOS | kernel-firmware | before 20210208-150300.4.19.1 | 20210208-150300.4.19.1 |
| SUSE:Linux Enterprise Micro 5.3 | kernel-firmware | before 20220509-150400.4.25.1 | 20220509-150400.4.25.1 |
| SUSE:Linux Enterprise Micro 5.5 | kernel-firmware | before 20230724-150500.3.9.1 | 20230724-150500.3.9.1 |
| SUSE:Linux Enterprise Server 12 SP5 | kernel-firmware | before 20190618-5.34.1 | 20190618-5.34.1 |
Same product
amd: all recordsOther highest-scoring records for the same primary product.
- CVE-2022-23830SMM configuration may not be immutable, as intended, when SNP is enabled resulting in a potential limited loss of guest memory integrity.21Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| opensuse:kernel-firmware | 20230724-150500.3.9.1 · openSUSE:Leap 15.5 | Package registry (OSV) |
| suse:kernel-firmware | 20210208-150300.4.19.1 · SUSE:Linux Enterprise High Performance Computing 15 SP3-ESPOS | Package registry (OSV) |
| suse:kernel-firmware | 20230724-150500.3.9.1 · SUSE:Linux Enterprise Micro 5.5 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-459 · Incomplete CleanupCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.