dbcve.org
Windows 10Operating system · Microsoft

CVE-2022-34731

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 (RCE) vulnerability in Microsoft's OLE DB provider for SQL Server. The vulnerability allows attackers to execute arbitrary code on affected systems via specially crafted queries or network packets, likely through memory corruption or improper input validation in the OLE DB provider component.

MitigationApply Microsoft security updates (KB5012344 or subsequent patches) to address this vulnerability. Prioritize patching systems with direct SQL Server connectivity and ensure network segmentation limits exposure to unauthenticated attackers.

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 Rt 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

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 if OLE DB Provider for SQL Server is installed
    Open Registry Editor and navigate to HKEY_CLASSES_ROOT\SQLOLEDB to see if the provider is registered. Alternatively, check for the presence of sqloledb.dll in the System32 or SysWOW64 directories.
    Affected if The SQLOLEDB provider registry key exists or sqloledb.dll file is present on the system.
  2. Identify the OLE DB provider DLL version
    Locate the sqloledb.dll file (typically in C:\Windows\System32\ or C:\Windows\SysWOW64\) and view its file properties to obtain the version number. Compare this version against the patched version.
    Affected if The DLL version is lower than the patched version or cannot be verified as updated.
  3. Check for SQL Server Native Client OLE DB provider
    Examine registry keys under HKEY_CLASSES_ROOT\ for SQLNCLI or SQL Server Native Client entries, and locate the corresponding DLL (sqlncli.dll) to check its version.
    Affected if SQL Server Native Client OLE DB provider is installed and its version is unpatched.
  4. Review installed SQL Server components
    Open Programs and Features (appwiz.cpl) and look for installations of SQL Server, SQL Server Native Client, or Microsoft OLE DB Provider for SQL Server.
    Affected if Any SQL Server or OLE DB provider component for SQL Server is installed on an affected Windows version.
  5. Audit applications using OLE DB SQL connections
    Review application configurations and documentation to identify any applications configured to connect to SQL Server using OLE DB (SQLOLEDB or SQLNCLI providers).
    Affected if Applications are configured to use OLE DB connections to SQL Server on affected Windows versions.

The system is affected if OLE DB Provider for SQL Server (SQLOLEDB) or SQL Server Native Client OLE DB is installed on any of the affected Windows versions listed, regardless of whether the specific update KB5012344 has been applied.

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 Microsoft security updates (KB5012344 or subsequent patches) to address this vulnerability. Prioritize patching systems with direct SQL Server connectivity and ensure network segmentation limits exposure to unauthenticated attackers.

Recommended fix High confidence

July 2022 Security Updates (KB5015827 and related patches for your Windows version)

  1. Check your current Windows version by running 'winver' or 'systeminfo'
  2. Navigate to Windows Update settings (Settings > Update & Security > Windows Update)
  3. Click 'Check for updates' to download and install the July 2022 security updates
  4. Alternatively, download and install the specific security update for this CVE (KB5015827 or subsequent superseded updates) from the Microsoft Update Catalog
  5. Restart the system after the update is installed
  6. Verify the update was installed successfully by checking Windows Update history
Caveat Security patches typically have minimal breaking changes; however, test in a non-production environment if concerned about application compatibility with updated WDAC/OLE DB components

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 / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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