CVE-2022-35835
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 · uneditedMicrosoft 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 confidenceThis is a Remote Code Execution vulnerability in Microsoft's WDAC (Windows Data Access Components) OLE DB provider for SQL Server. The vulnerability allows an attacker to execute arbitrary code on the affected system through the database provider, likely by sending specially crafted requests to the SQL Server.
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 versions= 20h2= 21h1= 21h2= 1607= 1809all versionsall versionsall versionsall versionsall versions= r2all versions= r2all 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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Verify if SQL Server OLE DB provider is installedCheck the Windows registry under HKLM\SOFTWARE\Classes\OLE DB Providers for any SQL Server related providers (such as 'SQLOLEDB' or 'SQL Server Native Client'), or review installed programs for Microsoft SQL Server OLE DB Provider componentsAffected if The SQL Server OLE DB provider (SQLOLEDB, SQLNCLI, or similar) is present on the system
-
Confirm the OLE DB provider is enabledCheck COM+ applications or the provider registry entries under HKLM\SOFTWARE\Classes\OLE DB Providers\ to verify the provider is not explicitly disabled (look for a 'Enabled' DWORD value set to 0)Affected if The OLE DB provider is enabled and accessible to applications
-
Identify installed Windows versionRun 'winver' or 'systeminfo' from command prompt to determine the exact Windows version and build numberAffected if The system runs Windows 10 (any version including 20H2, 21H1, 21H2, 1607, 1809), Windows 11, Windows 7, Windows 8.1, Windows RT 8.1, or Windows Server 2008/2012/2016 (any version including R2 variants)
-
Check for security patch installationView installed updates via 'Get-HotFix' PowerShell cmdlet or check Windows Update history for security update KB5014678 (July 2022 SQL Server security update) or subsequent related patchesAffected if The relevant security patch for this CVE has not been installed
A system is affected if it runs a vulnerable Windows version from the affected list AND has the SQL Server OLE DB provider installed and enabled, AND the corresponding security patch has not been applied.
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 the relevant Microsoft security patch for this vulnerability. If immediate patching is not possible, restrict network access to SQL Server and disable the OLE DB provider if not required.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-35835 — 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-2022-35835 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