CVE-2020-12905
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 · uneditedOut of Bounds Read in AMD Graphics Driver for Windows 10 in Escape 0x3004403 may lead to arbitrary information disclosure.
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 confidenceOut-of-bounds read vulnerability in AMD Graphics Driver for Windows 10's Escape function 0x3004403 allows reading arbitrary memory contents, leading to information disclosure. This is a local vulnerability with high confidentiality impact but no integrity or availability impact.
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< 20.11.2CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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.
-
Verify AMD Radeon Software is installedOpen Windows Settings > Apps & features, or use PowerShell: Get-WmiObject -Class Win32_Product | Where-Object {$_.Name -like '*AMD*' -or $_.Name -like '*Radeon*'}Affected if No AMD Radeon Software is found, the system is not affected by this specific vulnerability
-
Identify the installed AMD Radeon Software versionOpen AMD Radeon Software, click the gear icon (Settings), then select System > Software. Alternatively, check Control Panel > Programs and Features for the version entry.Affected if Version is missing or cannot be determined, unable to assess impact
-
Compare installed version against CVE thresholdCompare the installed version number to 20.11.2. Note that version 20.11.2 is the first fixed release. Any version below 20.11.2 (including 20.11.1, 20.10.1, etc.) is affected.Affected if Installed version is 20.11.1 or lower, the system is vulnerable to CVE-2020-12905
-
Check graphics driver file version as secondary confirmationNavigate to C:\Windows\System32\Drivers\ and locate atiadlxx.dll or similar AMD driver DLLs. Right-click > Properties > Details to view the File Version.Affected if Driver file version corresponds to software versions below 20.11.2
A system is affected if AMD Radeon Software for Windows 10 is installed with a version number lower than 20.11.2, as this is the specific condition under which the Escape function 0x3004403 out-of-bounds read vulnerability exists.
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 · scoped20.11.2
Apply the vendor-supplied AMD graphics driver patch for Windows 10. Until patched, restrict local access to trusted users only and monitor for exploitation attempts.
Radeon Software version 20.11.2 or later
- Navigate to the official AMD support website (www.amd.com/en/support)
- Locate and download Radeon Software version 20.11.2 or later for your specific GPU and Windows 10
- Run the installer with administrator privileges
- Follow the on-screen prompts to complete the driver installation
- Restart your computer to ensure the new driver loads properly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.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 $3,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-12905 — 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-2020-12905 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