Security readout for executives and security teams
Plain-English summary
This vulnerability affects Microsoft SQL Server ODBC and OLE DB drivers. If a user interaction triggers the vulnerable path on a system with affected drivers, code execution could result. Treat it as high priority where these drivers are installed, especially on systems handling untrusted data or running business applications.
Executive priority
High. This is not listed as known exploited, but successful exploitation could allow code execution with major business impact. Organizations should patch exposed driver installations through normal high-severity remediation workflows and verify inventory coverage.
Technical view
CVE-2023-23375 is a CWE-20 improper input validation issue in Microsoft ODBC Driver 17/18 for SQL Server and Microsoft OLE DB Driver 18/19 for SQL Server. The CVSS 3.1 score is 7.8 with local attack vector, no privileges required, user interaction required, and high confidentiality, integrity, and availability impact.
Likely exposure
Exposure is likely on Windows endpoints, developer machines, and servers with the listed Microsoft SQL Server ODBC or OLE DB drivers installed. The bundle does not identify specific applications, databases, or configurations beyond those driver products and versions.
Exploitation context
The source bundle marks exploit maturity as proof-of-concept, but CISA KEV is false and no cited source states active exploitation. User interaction is required, and the CVSS vector is local, so risk depends on where affected drivers are installed and how users interact with untrusted content or applications.
Researcher notes
Evidence is limited to the CVE record and Microsoft advisory metadata. The available CVSS vector indicates local access and user interaction, despite the RCE title. Do not infer internet-exposed exploitation without additional product-specific evidence.
Mitigation direction
- Apply Microsoft guidance for CVE-2023-23375 and update affected drivers.
- Prioritize systems with Microsoft SQL Server ODBC or OLE DB drivers installed.
- Remove vulnerable driver installations where they are no longer required.
- Check MSRC for fixed versions and any product-specific remediation notes.
- Avoid treating this as actively exploited unless new cited evidence appears.
Validation and detection
- Inventory installed Microsoft ODBC Driver for SQL Server versions 17 and 18.
- Inventory installed Microsoft OLE DB Driver for SQL Server versions 18 and 19.
- Compare discovered versions with Microsoft’s CVE-2023-23375 guidance.
- Confirm updated driver versions through endpoint or software inventory.
- Document remaining exposed systems and remediation owners.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-20: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2023-23375 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:P/RL:O/RC:C
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:P/RL:O/RC:C1.85.9microsoftVulnerability scoring details
Base CVSS 3.1 score
7.8HighVector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:P/RL:O/RC:C
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- Microsoft ODBC and OLE DB Remote Code Execution VulnerabilityCVE reference, microsoft · vendor-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Input Validation
Improper Input Validation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.