dbcve.org
Radeon SoftwareApplication · Amd

CVE-2023-20586

CRITICAL · 9.8 CVSS v3.1 Published 2023-08-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
A potential vulnerability was reported in Radeon™ Software Crimson ReLive Edition which may allow escalation of privilege. Radeon™ Software Crimson ReLive Edition falls outside of the security support lifecycle and AMD does not plan to release any mitigations

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 · high confidence

A privilege escalation vulnerability exists in AMD Radeon Software Crimson ReLive Edition, an older graphics driver and control suite. The specific technical details of the flaw are not public, but the critical CVSS 9.8 score indicates remote or adjacent exploitation with low complexity, requiring no privileges or user interaction to achieve full system compromise.

MitigationSince AMD has stated no patches will be released, organizations should uninstall Radeon Software Crimson ReLive Edition and migrate to supported AMD software. If the software cannot be removed, implement network segmentation and restrict access to minimize attack surface.

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
Radeon SoftwareApplication
Affected:all versions

CVSS 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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check for AMD Radeon Software Crimson ReLive Edition installation
    Open Control Panel > Programs and Features (or Settings > Apps on Windows 10/11) and look for an entry named 'AMD Radeon Software Crimson ReLive Edition' in the installed programs list
    Affected if The program appears in the installed programs list
  2. Check for Crimson ReLive Edition executable files
    Search the file system for 'RadeonSoftware.exe' or 'RadeonSettings.exe' in typical installation paths such as C:\Program Files\AMD\Radeon Software or C:\Program Files (x86)\AMD\Radeon Software. Also check C:\Program Files\AMD\CrimsonReLive if present
    Affected if Executable files matching the Crimson ReLive Edition software are found on the system
  3. Check for related Windows services
    Open Services console (services.msc) and look for AMD-related services that may indicate the Crimson ReLive Edition driver suite is running, such as 'AMD Radeon Settings' or similar named services
    Affected if AMD services associated with Crimson ReLive Edition are running or installed
  4. Check for presence of older AMD driver components
    Inspect the Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for keys containing 'Radeon Software' or 'Crimson ReLive' in the DisplayName value
    Affected if Registry entries for AMD Radeon Software Crimson ReLive Edition are found

A user is affected if AMD Radeon Software Crimson ReLive Edition is installed on their system, as all versions of this legacy software are vulnerable and no patch will be released.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Since AMD has stated no patches will be released, organizations should uninstall Radeon Software Crimson ReLive Edition and migrate to supported AMD software. If the software cannot be removed, implement network segmentation and restrict access to minimize attack surface.

Recommended fix High confidence
  1. Radeon™ Software Crimson ReLive Edition is outside the AMD security support lifecycle and AMD has explicitly stated it does not plan to release any mitigations for this vulnerability.
  2. No patch, update, or configuration workaround is available from AMD to address CVE-2023-20586.
  3. Consider migrating to a currently supported AMD software solution such as AMD Radeon™ Software Adrenalin Edition if operational requirements permit.
  4. If continued use of Crimson ReLive Edition is mandatory, isolate the system running this software behind additional security controls such as network segmentation and restricted user privileges to reduce the exploit impact.
Caveat Radeon Software Crimson ReLive Edition is end-of-life with no security support; migrating to currently supported AMD software may introduce UI/feature changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Radeon Software Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $910
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,456.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-20586 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-20586 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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