CVE-2021-46748: Insufficient bounds checking in the ASP (AMD Secure Processor) may allow an attacker to access memory outside the bounds of what is permissi
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.21% (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.
- 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 bounds checking in the ASP (AMD Secure Processor) may allow an attacker to access memory outside the bounds of what is permissible to a TA (Trusted Application) resulting in a potential denial of service.
- Published
- Nov 14, 2023
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 11th percentile
- CWE
- CWE-119
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%
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 | radeon software | cpe:2.3:a:amd:radeon_software |
| amd | radeon rx 5300 | cpe:2.3:h:amd:radeon_rx_5300 |
| amd | radeon rx 5300 xt | cpe:2.3:h:amd:radeon_rx_5300_xt |
| amd | radeon rx 5300m | cpe:2.3:h:amd:radeon_rx_5300m |
| amd | radeon rx 5500 | cpe:2.3:h:amd:radeon_rx_5500 |
| amd | radeon rx 5500 xt | cpe:2.3:h:amd:radeon_rx_5500_xt |
| amd | radeon rx 5500m | cpe:2.3:h:amd:radeon_rx_5500m |
| amd | radeon rx 5600 | cpe:2.3:h:amd:radeon_rx_5600 |
| amd | radeon rx 5600 xt | cpe:2.3:h:amd:radeon_rx_5600_xt |
| amd | radeon rx 5600m | cpe:2.3:h:amd:radeon_rx_5600m |
| amd | radeon rx 5700 | cpe:2.3:h:amd:radeon_rx_5700 |
| amd | radeon rx 5700 xt | cpe:2.3:h:amd:radeon_rx_5700_xt |
and 111 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- amd radeon pro vega 56 firmwareall versions
- amd radeon pro vega 64 firmwareall versions
- amd radeon rx vega 56 firmwareall versions
- amd radeon rx vega 64 firmwareall versions
- amd radeon softwarebefore 23.q3
- amd radeon softwarebefore 23.7.1
- intel radeon rx vega m firmwarebefore 23.10.01.46
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 Radeon™ PRO W5000/W6000/W7000 Series Graphics Cards
- variousaffected
AMD Radeon™ PRO WX Vega Series Graphics Cards
- variousaffected
AMD Radeon™ RX 5000/6000/7000 Series Graphics Cards
- variousaffected
AMD Radeon™ RX Vega Series Graphics Cards
- variousaffected
Same product
amd: all recordsOther highest-scoring records for the same primary product.
- CVE-2023-20586Radeon™ Software Crimson ReLive Edition39Monitor
- CVE-2024-21937Incorrect default permissions in the AMD HIP SDK installation directory could allow an attacker to achieve privilege escalation potentially 31Monitor
- CVE-2023-20598
An improper privilege management in the AMD Radeon™ Graphics driver may allow an authenticated attacker to craft an IOCTL request to gain31Monitor
Published before and after this one in the same product
- ← EarlierCVE-2021-26317May 12, 2022 · Failure to verify the protocol in SMM may allow an attacker to control the protocol and modify SPI flash resulting in a potential arbitrary 31Monitor
- ← EarlierCVE-2021-26363May 12, 2022 · A malicious or compromised UApp or ABL could potentially change the value that the ASP uses for its reserved DRAM, to one outside of the fen17Monitor
- Later →CVE-2023-20567Nov 14, 2023 · Improper signature verification of RadeonTM RX Vega M Graphics driver for Windows may allow an attacker with admin privileges to launch AMDS26Monitor
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
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
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
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-119 · Improper Restriction of Operations within the Bounds of a Memory BufferCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/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)
- Buffer Overflow via Environment VariablesCAPEC-10likelihood: High · High
- Overflow BuffersCAPEC-100likelihood: High · Very High
- Buffer ManipulationCAPEC-123likelihood: High · Very High
- Client-side Injection-induced Buffer OverflowCAPEC-14likelihood: Medium · High
- Filter Failure through Buffer OverflowCAPEC-24likelihood: High · High
- MIME ConversionCAPEC-42likelihood: High · High
- Overflow Binary Resource FileCAPEC-44likelihood: High · Very High
- Buffer Overflow via Symbolic LinksCAPEC-45likelihood: High · High
ATT&CK techniques
—
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.