CVE-2021-46765: Insufficient input validation in ASP may allow an attacker with a compromised SMM to induce out-of-bounds memory reads within the ASP…
Noroxi assessment
Priority: Monitor (action score 30/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.61% (FIRST EPSS); higher than 50% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- According to the record, no fixed version is available yet.
Low priority for now. Update when a fix is released; follow the vendor's advisory.
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
Insufficient input validation in ASP may allow an attacker with a compromised SMM to induce out-of-bounds memory reads within the ASP, potentially leading to a denial of service.
- Published
- May 9, 2023
- Updated
- Jun 17, 2026
- EPSS
- 0.6% · 50th percentile
- CWE
- CWE-125
Report tools
Action score
30
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.6%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
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 | ryzen 6600h firmware | cpe:2.3:o:amd:ryzen_6600h_firmware |
| amd | ryzen 6600h | cpe:2.3:h:amd:ryzen_6600h |
| amd | ryzen 6600hs firmware | cpe:2.3:o:amd:ryzen_6600hs_firmware |
| amd | ryzen 6600hs | cpe:2.3:h:amd:ryzen_6600hs |
| amd | ryzen 6600u firmware | cpe:2.3:o:amd:ryzen_6600u_firmware |
| amd | ryzen 6600u | cpe:2.3:h:amd:ryzen_6600u |
| amd | ryzen 6800h firmware | cpe:2.3:o:amd:ryzen_6800h_firmware |
| amd | ryzen 6800h | cpe:2.3:h:amd:ryzen_6800h |
| amd | ryzen 6800hs firmware | cpe:2.3:o:amd:ryzen_6800hs_firmware |
| amd | ryzen 6800hs | cpe:2.3:h:amd:ryzen_6800hs |
| amd | ryzen 6800u firmware | cpe:2.3:o:amd:ryzen_6800u_firmware |
| amd | ryzen 6800u | cpe:2.3:h:amd:ryzen_6800u |
and 76 more
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 Ryzen™ 3000 Series Mobile Processors with Radeon™ Graphics “Renoir”
- variousaffected
AMD Ryzen™ 5000 Series Desktop processor with Radeon™ Graphics “Cezanne” AM4
- variousaffected
AMD Ryzen™ 5000 Series Mobile processors with Radeon™ Graphics “Cezanne”
- variousaffected
AMD Ryzen™ 5000 Series Mobile Processors with Radeon™ Graphics “Lucienne”
- variousaffected
AMD Ryzen™ 6000 Series Mobile Processors "Rembrandt"
- variousaffected
Affected versions · NVD (20)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- amd ryzen 3100 firmwarecomboam4v2_pi_1.2.0.8
- amd ryzen 3100 firmwarerenoirpi-fp6_1.0.0.9
- amd ryzen 3300x firmwarecomboam4v2_pi_1.2.0.8
- amd ryzen 3300x firmwarerenoirpi-fp6_1.0.0.9
- amd ryzen 3500 firmwarecomboam4v2_pi_1.2.0.8
- amd ryzen 3500 firmwarerenoirpi-fp6_1.0.0.9
- amd ryzen 3500x firmwarecomboam4v2_pi_1.2.0.8
- amd ryzen 3500x firmwarerenoirpi-fp6_1.0.0.9
- amd ryzen 3600 firmwarecomboam4v2_pi_1.2.0.8
- amd ryzen 3600 firmwarerenoirpi-fp6_1.0.0.9
- amd ryzen 3600x firmwarecomboam4v2_pi_1.2.0.8
- amd ryzen 3600x firmwarerenoirpi-fp6_1.0.0.9
- amd ryzen 3600xt firmwarecomboam4v2_pi_1.2.0.8
- amd ryzen 3600xt firmwarerenoirpi-fp6_1.0.0.9
- amd ryzen 3800x firmwarecomboam4v2_pi_1.2.0.8
- amd ryzen 3800x firmwarerenoirpi-fp6_1.0.0.9
- amd ryzen 3800xt firmwarecomboam4v2_pi_1.2.0.8
- amd ryzen 3800xt firmwarerenoirpi-fp6_1.0.0.9
- amd ryzen 3900 firmwarecomboam4v2_pi_1.2.0.8
- amd ryzen 3900 firmwarerenoirpi-fp6_1.0.0.9
Same product
amd: all recordsOther highest-scoring records for the same primary product.
- CVE-2021-46753Failure to validate the length fields of the ASP
(AMD Secure Processor) sensor fusion hub headers may allow an attacker with a
malicious…36Monitor
- CVE-2021-46773Insufficient input validation in ABL may enable
a privileged attacker to corrupt ASP memory, potentially resulting in a loss of
integrity…35Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
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.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-125 · Out-of-bounds ReadCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
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.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log (0)
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.