CVE-2022-34726
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 ODBC Driver 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 confidenceA remote code execution vulnerability in Microsoft ODBC Driver allows attackers to execute arbitrary code by sending specially crafted network packets or responding maliciously to ODBC connection requests. The vulnerability stems from insufficient input validation in the ODBC driver component when handling database server responses.
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.
-
Identify installed ODBC driversOpen Registry Editor and navigate to HKLM\SOFTWARE\ODBC\ODBCINST.INI\ODBC Drivers, or run 'odbcad32.exe' and check the Drivers tab. Note any Microsoft SQL Server ODBC drivers listed.Affected if Any Microsoft ODBC Driver for SQL Server is installed (v17, v18, or older versions).
-
Check ODBC driver DLL versionLocate the ODBC driver DLL (typically sqlsrv32.dll for older versions, or msodbcsql*.dll for newer versions) in the Windows\System32 folder or the driver install directory. Right-click the file, select Properties, and view the Version tab.Affected if The driver file version is older than the patched version for your driver branch (contact Microsoft for exact patched version numbers for your driver release).
-
Verify ODBC data sources using vulnerable driverOpen ODBC Data Source Administrator (odbcad32.exe), go to User DSN or System DSN tabs, and check if any configured data sources use the Microsoft ODBC Driver for SQL Server.Affected if A data source is configured using an unpatched Microsoft ODBC Driver version.
-
Check for ODBC driver usage via SQL Server connectionsReview any applications or services that connect to SQL Server using ODBC. Check configuration files, connection strings, or service configurations for ODBC driver references.Affected if Applications or services are configured to use an unpatched Microsoft ODBC Driver version for database connections.
The system is affected if Microsoft ODBC Driver for SQL Server is installed and its version falls within the unpatched version range for your Windows environment.
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 Microsoft security updates for the affected ODBC Driver version or update to the latest Microsoft SQL Server/ODBC driver package that includes the patched components.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-34726 — 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-34726 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