CVE-2023-20567: Improper signature verification of RadeonTM RX Vega M Graphics driver for Windows may allow an attacker with admin privileges to launch…
Noroxi assessment
Priority: Monitor (action score 26/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.17% (FIRST EPSS).
- Someone with local access to the system can trigger it. Administrator privileges are required. 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
Improper signature verification of RadeonTM RX Vega M Graphics driver for Windows may allow an attacker with admin privileges to launch AMDSoftwareInstaller.exe without validating the file signature potentially leading to arbitrary code execution.
- Published
- Nov 14, 2023
- Updated
- Jun 17, 2026
- EPSS
- 0.1% · 6th percentile
- CWE
- CWE-347
Report tools
Action score
26
Low priority for now.
- CVSS
- 26 / 40 · 6.7 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
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 | 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
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
Affected versions · NVD (7)
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
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…31Monitor
Published before and after this one in the same product
- ← 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…17Monitor
- ← EarlierCVE-2021-46748Nov 14, 2023 · Insufficient bounds checking in the ASP (AMD Secure Processor) may allow an attacker to access memory outside the bounds of what is…22Monitor
- Later →CVE-2023-31320Nov 14, 2023 · Improper input validation in the AMD RadeonTM Graphics display driver may allow an attacker to corrupt the display potentially resulting in…30Monitor
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.
Bug bounty scope
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- Administrator privileges are 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
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-347 · Improper Verification of Cryptographic SignatureCVSS vector
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Root cause
The verifier takes the algorithm to verify with from the token’s own header. Untrusted data ends up deciding its own verification rule.
The bug in code
The whole CWE-347 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
const claims = jwt.verify(token, publicKey);Fixed
const claims = jwt.verify(token, publicKey, {
algorithms: ["RS256"],
issuer: "https://id.example.com",
audience: "portal",
});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
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.