CVE-2021-46753: Failure to validate the length fields of the ASP (AMD Secure Processor) sensor fusion hub headers may allow an attacker with a malicious Uap
Noroxi assessment
Priority: Monitor (action score 36/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.56% (FIRST EPSS).
- 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
Failure to validate the length fields of the ASP (AMD Secure Processor) sensor fusion hub headers may allow an attacker with a malicious Uapp or ABL to map the ASP sensor fusion hub region and overwrite data structures leading to a potential loss of confidentiality and integrity.
- Published
- May 9, 2023
- Updated
- Jun 17, 2026
- EPSS
- 0.5% · 46th percentile
- CWE
- —
Report tools
Action score
36
Monitor
Low priority for now.
- CVSS
- 36 / 40 · 9.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.5%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- total
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.
Running WordPress? Scan your site free with WP Lens
Noroxi 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 120 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- amd athlon gold 3150g firmwarepicassopi-fp5_1.0.0.e
- amd athlon gold 3150g firmwarepollockpi-ft5_1.0.0.4
- amd athlon gold 3150ge firmwarepicassopi-fp5_1.0.0.e
- amd athlon gold 3150ge firmwarepollockpi-ft5_1.0.0.4
- amd athlon silver 3050ge firmwarepicassopi-fp5_1.0.0.e
- amd athlon silver 3050ge firmwarepollockpi-ft5_1.0.0.4
- amd ryzen 1200 (af) firmwarecomboam4pi_1.0.0.9
- amd ryzen 1200 (af) firmwarecomboam4v2_pi_1.2.0.8
- amd ryzen 1200 (af) firmwarepinnaclepi-am4_1.0.0.d
- amd ryzen 1200 (af) firmwareraven-fp5-am4_1.1.0.f
- amd ryzen 1600 (af) firmwarecomboam4pi_1.0.0.9
- amd ryzen 1600 (af) firmwarecomboam4v2_pi_1.2.0.8
- amd ryzen 1600 (af) firmwarepinnaclepi-am4_1.0.0.d
- amd ryzen 1600 (af) firmwareraven-fp5-am4_1.1.0.f
- amd ryzen 2200g firmwarecomboam4pi_1.0.0.9
- amd ryzen 2200g firmwarecomboam4v2_pi_1.2.0.8
- amd ryzen 2200g firmwarepinnaclepi-am4_1.0.0.d
- amd ryzen 2200g firmwareraven-fp5-am4_1.1.0.f
- amd ryzen 2200ge firmwarecomboam4pi_1.0.0.9
- amd ryzen 2200ge firmwarecomboam4v2_pi_1.2.0.8
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 Athlon™ 3000 Series Mobile Processors with Radeon™ Graphics “Pollock”
- variousaffected
AMD Athlon™ 3000 Series Mobile Processors with Radeon™ Graphics “Dali”/”Dali” ULP
- variousaffected
AMD Ryzen™ 2000 series Desktop Processors “Raven Ridge” AM4
- variousaffected
AMD Ryzen™ 2000 Series Mobile Processors “Raven Ridge” FP5
- variousaffected
AMD Ryzen™ 3000 Series Mobile processor, 2nd Gen AMD Ryzen™ Mobile Processors with Radeon™ Graphics “Picasso”
- variousaffected
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
Same product
amd: all recordsOther highest-scoring records for the same primary product.
- CVE-2021-46773Insufficient input validation in ABL may enable
a privileged attacker to corrupt ASP memory, potentially resulting in a loss of
integrity or35Monitor
- CVE-2021-46765Insufficient input validation in ASP may allow
an attacker with a compromised SMM to induce out-of-bounds memory reads within
the ASP, poten30Monitor
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.
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
- 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
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- None
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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
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.