CVE-2023-20567
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedImproper 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceImproper signature verification in the Radeon RX Vega M Graphics driver for Windows allows an attacker with existing admin privileges to launch AMDSoftwareInstaller.exe without validating the file signature, potentially leading to arbitrary code execution with elevated privileges.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 23.10.01.46< 23.7.1< 23.q3all versionsall versionsall versionsall versionsCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed AMD Radeon Software versionOpen Programs and Features (appwiz.cpl) or check the installed version via the AMD Radeon Settings application, or run 'wmic product get name,version' to list installed AMD software componentsAffected if The version is less than 23.7.1 or 23.q3 for AMD Radeon Software, or less than 23.10.01.46 for Intel Radeon Rx Vega M Firmware, or if using any version of Rx Vega 56/64 or Pro Vega 56/64 firmware
-
Locate AMDSoftwareInstaller.exe on the systemSearch for the file using File Explorer or command: 'Get-ChildItem -Path C:\ -Recurse -Filter AMDSoftwareInstaller.exe -ErrorAction SilentlyContinue'Affected if The executable exists on the system - this is the vulnerable component
-
Verify digital signature of AMDSoftwareInstaller.exeRight-click the executable, go to Properties > Digital Signatures tab, or run 'Get-AuthenticodeSignature <path_to_AMDSoftwareInstaller.exe>' in PowerShellAffected if The signature is invalid, missing, or shows a warning/error indicating the signature was not properly validated at launch time
-
Check for presence of affected GPU firmware/driverOpen Device Manager > Display adapters, right-click the AMD/Intel Vega GPU > Properties > Driver tab to view driver version, or run 'wmic path win32_VideoController get name,driverversion'Affected if The GPU is a Radeon Rx Vega 56, Rx Vega 64, Pro Vega 56, Pro Vega 64, or Intel Radeon Rx Vega M with driver version in the affected ranges
-
Confirm user has administrative privilegesRun 'whoami /groups' or check if the current user is a member of the Administrators groupAffected if The current user has administrator-level privileges - this is required for the attack vector to function
A user is affected if they have an affected AMD Radeon product installed (Rx Vega 56/64, Pro Vega 56/64, Intel Rx Vega M with firmware < 23.10.01.46, or AMD Radeon Software < 23.7.1/23.q3), the AMDSoftwareInstaller.exe file exists, and the user has administrative privileges on the system.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped23.q323.7.123.10.01.46
Apply vendor-supplied patches/updates for the AMD Radeon driver when available. Until patched, restrict administrative access, implement application whitelisting, and monitor for unauthorized execution of AMDSoftwareInstaller.exe.
Radeon Software: 23.7.1 or 23.q3 (or later); Vega M Firmware: 23.10.01.46 or later
- Verify the current installed version of AMD Radeon Software by opening AMD Radeon Software and checking the version information in Settings > About
- For systems with Radeon RX Vega M graphics, navigate to the official AMD support website and download Radeon Software version 23.7.1 or later (or 23.q3 depending on your region)
- For Radeon RX Vega M firmware, ensure the firmware is updated to version 23.10.01.46 or later through the AMD driver update process
- For Radeon RX Vega 56/64 and Pro Vega 56/64, apply the latest available AMD Radeon Software driver update which should include the signature verification fix
- Restart the system after driver installation to ensure the fix takes effect
- Verify the fix by checking that AMDSoftwareInstaller.exe now properly validates file signatures before execution
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-20567 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-20567 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data