CVE-2021-33063
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 · uneditedUncontrolled search path in the Intel(R) RealSense(TM) D400 Series UWP driver for Windows 10 before version 6.1.160.22 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 · high confidenceThe Intel RealSense D400 Series UWP driver for Windows 10 before version 6.1.160.22 contains an uncontrolled search path vulnerability (also known as DLL hijacking or binary planting). An authenticated local user can place malicious executables in the search path used by the driver, causing the driver to load and execute them with elevated privileges, resulting in local privilege escalation.
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< 6.1.160.22CVSS 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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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.
-
Check if Intel RealSense D400 Series driver is installedOpen Device Manager, expand 'Imaging devices' or 'Cameras' category, look for Intel RealSense D400 series entries (e.g., Intel RealSense Depth Camera 4xx, Intel RealSense RGB Camera). Alternatively, run 'Get-PnpDevice -Class Camera | Where-Object {$_.FriendlyName -like "*RealSense*"}' in PowerShell.Affected if The device appears in Device Manager or PowerShell output, indicating the driver is present on the system.
-
Retrieve the installed driver versionIn Device Manager, right-click the Intel RealSense device, select Properties, go to the Driver tab, and note the Driver Version. Alternatively, run 'Get-PnpDevice -Class Camera | Where-Object {$_.FriendlyName -like "*RealSense*"} | Get-PnpDeviceProperty -KeyName "DEVPKEY_DriverVersion"' in PowerShell.Affected if A driver version number is returned, which can then be compared against the safe version.
-
Compare installed version against affected rangeCompare the retrieved driver version to 6.1.160.22 using version number comparison (e.g., 6.1.160.21 or lower is affected; 6.1.160.22 or higher is patched). In PowerShell: [version]"6.1.160.22" -gt [version]"INSTALLED_VERSION"Affected if The installed version is less than 6.1.160.22 (e.g., 6.1.160.21, 6.1.150.10, etc.).
A user is affected if the Intel RealSense D400 Series UWP driver is installed and its version is lower than 6.1.160.22, as this allows local privilege escalation via DLL hijacking.
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 · scoped6.1.160.22
Update the Intel RealSense D400 Series UWP driver to version 6.1.160.22 or later to obtain the vendor patch.
6.1.160.22 or later
- Identify the Intel RealSense D400 Series device in Device Manager
- Right-click on the device and select 'Update driver'
- Choose 'Search automatically for updated driver software' or download version 6.1.160.22 or later from Intel's support website
- If using the manual download method, select 'Browse my computer for driver software' and point to the downloaded driver package
- Complete the driver update and restart the system if prompted
- Verify the driver version is 6.1.160.22 or later in Device Manager
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-33063 — 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-2021-33063 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