CVE-2020-0560
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 permissions in the installer for the Intel(R) Renesas Electronics(R) USB 3.0 Driver, all versions, may allow an authenticated user to potentially enable escalation of privilege via local access.
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 file system or registry permissions in the Intel Renesas USB 3.0 driver installer allow an authenticated local user to manipulate installer components or installation behavior to gain elevated (system/administrator) privileges on the affected Windows system.
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 dataall 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/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 if Intel Renesas USB 3.0 Driver is installedCheck Windows installed programs via Registry at HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for entries containing 'Renesas' or 'USB 3.0', or inspect Program Files for Renesas driver directoriesAffected if Intel Renesas USB 3.0 Driver is present on the system (all versions are affected)
-
Verify file permissions on driver installation directoryRight-click the Renesas driver installation folder (typically in Program Files or Program Files (x86)), go to Properties > Security, and examine which users have Write or Full Control permissionsAffected if Non-privileged users (Authenticated Users, Users group, or specific non-admin accounts) have Write, Modify, or Full Control permissions on installer directories or files
-
Check permissions on installer executable filesUse icacls or file properties to list permissions on .exe or .msi installer files in the Renesas driver directoryAffected if Installer files are writable or modifiable by non-admin users
-
Audit registry permissions for driver keysUse regedit or icacls to inspect permissions on HKLM\SYSTEM\CurrentControlSet\Services\Renesas USB 3.0 related keys, or the uninstall registry entries under the Uninstall registry pathAffected if Non-privileged users have Write or Full Control permissions on driver-related registry keys
-
Check temp or staging folders used by installerExamine permissions on any temporary or staging directories used during driver installation, or check if Users folder contains leftover installer filesAffected if Installer temporary files or staging directories are writable by non-privileged users
A user is affected if the Intel Renesas USB 3.0 Driver is installed and non-administrative users have Write or Modify permissions on any installer-related files, directories, or registry keys.
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.
From vendor dataApply vendor-supplied patches or updated installer for the Intel Renesas USB 3.0 Driver; if no patch available, audit and restrict permissions on installer files and directories to prevent manipulation by non-privileged users.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-0560 — 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-0560 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