dbcve.org
Thunderbolt Dch DriverApplication · Intel

CVE-2023-22390

MEDIUM · 6.5 CVSS v3.1 Published 2024-02-14
Fix available
A fix is available. Upgrade to 88 or later.
See remediation →
67/100
Remediation priority · Elevated
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
Improper buffer restrictions in some Intel(R) Thunderbolt(TM) DCH drivers for Windows before version 88 may allow an authenticated user to potentially enable information disclosure 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 confidence

Improper buffer restrictions in Intel(R) Thunderbolt(TM) DCH drivers for Windows before version 88 allows an authenticated local user to potentially read beyond allocated buffer boundaries, enabling information disclosure of sensitive memory contents.

MitigationUpdate Intel Thunderbolt DCH drivers for Windows to version 88 or later to remediate the improper buffer restriction vulnerability.

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
Thunderbolt Dch DriverApplication
Affected:< 88

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
None

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

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

  1. Verify Intel Thunderbolt DCH driver is installed
    Open Device Manager, expand 'System devices' (or 'Universal Serial Bus controllers'), look for devices named 'Intel Thunderbolt' or 'Thunderbolt(TM)' - right-click and select 'Properties' to view driver information
    Affected if The device/driver is not present in Device Manager (then not affected)
  2. Retrieve the installed driver version
    In Device Manager, right-click the Intel Thunderbolt device, go to 'Driver' tab, click 'Driver Details' - look for a .sys file (typically 'tbtusb.sys' or similar), then note the file version shown
    Affected if Driver version shown is less than 88 (e.g., 87.x, 86.x, etc.)
  3. Alternative: Check driver version via PowerShell
    Run 'Get-WmiObject Win32_PnPSignedDriver | Where-Object {$_.DeviceName -like "*Thunderbolt*"} | Select-Object DeviceName, DriverVersion, DriverDate' in PowerShell to list Thunderbolt-related drivers and their versions
    Affected if The DriverVersion returned is below 88 (e.g., 1.41.xxx.0, etc.) - compare numerically against 88.0.0.0 or the version notation used
  4. Check driver date as secondary verification
    In Device Manager driver properties or via the PowerShell command above, note the DriverDate - driver versions below 88 with dates prior to the version 88 release indicate the vulnerable state
    Affected if Driver version is below 88 regardless of date (version is the primary indicator)

You are affected if the Intel Thunderbolt DCH driver for Windows is installed and its displayed version number is below 88.

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
Upgrade available Upgrade to 88 or later
Fixed in 88
Interim mitigation

Update Intel Thunderbolt DCH drivers for Windows to version 88 or later to remediate the improper buffer restriction vulnerability.

Recommended fix Moderate confidence

Intel Thunderbolt DCH Driver version 88 for Windows

  1. Identify the current Thunderbolt DCH Driver version by opening Device Manager, expanding the 'System devices' category, locating 'Intel(R) Thunderbolt(TM)', right-clicking, and selecting 'Properties' to view the driver version under the 'Driver' tab
  2. Navigate to the official Intel Support website and search for Thunderbolt DCH Driver updates for Windows
  3. Download the Thunderbolt DCH Driver version 88 or later from Intel's official download page
  4. Extract the downloaded installer and run it as an administrator to install the updated driver
  5. Restart the computer when prompted to complete the driver installation
  6. Verify the installed version by returning to Device Manager and confirming the driver version now shows version 88 or higher

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

Fix this in Thunderbolt Dch Driver Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-22390 — 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-22390 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