dbcve.org
Windows 10Operating system · Microsoft

CVE-2022-35840

HIGH · 8.8 CVSS v3.1 Published 2022-09-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
Microsoft WDAC OLE DB provider for SQL Server Remote Code Execution Vulnerability

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 confidence

This is a Remote Code Execution vulnerability in Microsoft's WDAC (Windows Data Access Components) OLE DB provider for SQL Server. An attacker could exploit this to execute arbitrary code on affected systems. The CVSS score of 8.8 indicates the vulnerability is exploitable over the network with low attack complexity and does not require privileges or user interaction.

MitigationApply the relevant Microsoft security update for this vulnerability. If patches are unavailable, restrict network access to SQL Server ports and enforce strong authentication to reduce the 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
Windows 10Operating system
Affected:all versions= 20h2= 21h1= 21h2= 1607= 1809
Windows 11Operating system
Affected:all versions
Windows 7Operating system
Affected:all versions
Windows 8.1Operating system
Affected:all versions
Windows Server 2008Operating system
Affected:all versions= r2
Windows Server 2012Operating system
Affected:all versions= r2
Windows Server 2016Operating system
Affected:all versions
Windows Server 2019Operating system
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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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

  1. Check Windows version
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to identify the Windows version
    Affected if The version matches any of the affected versions listed (Windows 10 all versions, Windows 11 all versions, Windows 7 all versions, Windows 8.1 all versions, Windows Server 2008/2012/2016/2019 all versions)
  2. Verify SQL Server OLE DB provider is installed
    Check for the presence of SQLOLEDB.dll in the system (typically in C:\Windows\System32\) or check registry key HKLM\SOFTWARE\Microsoft\OLE DB Provider for SQL Server
    Affected if The OLE DB provider for SQL Server (SQLOLEDB) is present on the system
  3. Confirm SQL Server client libraries are in use
    Check installed programs for Microsoft SQL Server OLE DB Provider or examine registry under HKLM\SOFTWARE\Classes\SQLOLEDB to verify the provider is registered
    Affected if The SQLOLEDB provider is registered and available for applications to use
  4. Identify applications using OLE DB connections
    Review application configurations or use Process Monitor to observe which processes load SQLOLEDB.dll
    Affected if Any application or service uses OLE DB connections to SQL Server using the vulnerable provider

If the system runs an affected Windows version and has the SQL Server OLE DB provider (SQLOLEDB) installed and in use, the environment is potentially affected by this vulnerability.

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

Apply the relevant Microsoft security update for this vulnerability. If patches are unavailable, restrict network access to SQL Server ports and enforce strong authentication to reduce the attack surface.

Recommended fix High confidence

Apply the Microsoft security update for CVE-2022-35840 (refer to msrc.microsoft.com for the specific KB article for your Windows version)

  1. Check the installed version of Microsoft Data Access Components (MDAC) or Windows Data Access Components (WDAC) OLE DB provider on the affected system
  2. Locate the corresponding security update for CVE-2022-35840 from the Microsoft Security Response Center (msrc.microsoft.com)
  3. Apply the appropriate security update for your specific Windows version and build
  4. Restart the affected system if required by the update
  5. Verify the update was successfully installed by checking the system for the installed patches
Caveat For Windows 7, Windows Server 2008 R2, and other legacy systems that have reached end-of-support, Microsoft may no longer provide security updates; consider migrating to a supported Windows version

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

Fix this in Windows 10 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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