dbcve.org
Sql ServerApplication · Microsoft

CVE-2015-1763

HIGH · 8.5 CVSS v2.0 Published 2015-07-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
91/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 SQL Server 2008 SP3 and SP4, 2008 R2 SP2 and SP3, 2012 SP1 and SP2, and 2014 does not prevent use of uninitialized memory in certain attempts to execute virtual functions, which allows remote authenticated users to execute arbitrary code via a crafted query, aka "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 · high confidence

Microsoft SQL Server contains a memory corruption vulnerability where the database engine fails to properly initialize memory before using it in virtual function calls. An authenticated remote attacker can send a specially crafted SQL query to trigger use of uninitialized memory, potentially leading to arbitrary code execution with SQL Server service account privileges.

MitigationApply the Microsoft security update (MS15-058) for this vulnerability. In the interim, minimize the attack surface by restricting database access to only necessary authenticated users, enforcing least privilege principles, and leveraging network-level isolation.

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
Sql ServerApplication
Affected:= 2008= 2012= 2014

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
M
Authentication
Single
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:M/Au:S/C:C/I:C/A:C

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. Identify SQL Server version
    Run SELECT @@VERSION in a SQL query or check the SQL Server version via SQL Server Management Studio, PowerShell Get-ItemProperty for registry key HKLM:\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQLServer\CurrentVersion, or the SQL Server Installation Center
    Affected if The installed version is SQL Server 2008, SQL Server 2012, or SQL Server 2014 (any build)
  2. Verify SQL Server service is running
    Check if the SQL Server service (MSSQLSERVER) is running via Services console, PowerShell Get-Service MSSQLSERVER, or tasklist /FI "IMAGENAME eq sqlservr.exe"
    Affected if SQL Server service is active and accepting connections
  3. Confirm authenticated access exists
    Review SQL Server login configurations: check sys.server_principals for all logins, verify authentication mode via SELECT serverproperty('IsIntegratedSecurityOnly'), and inspect public server roles
    Affected if Any login other than highly privileged admins (sysadmin) exists, or integrated Windows authentication is enabled allowing domain users access
  4. Assess network exposure
    Check SQL Server network protocols via SQL Server Configuration Manager, specifically TCP/IP and Named Pipes enabled status, and review firewall rules or port 1433/1434 listening status
    Affected if SQL Server is listening on network interfaces accessible to remote attackers (not localhost-only)
  5. Check for presence of security update
    Review installed Windows updates or check SQL Server build number against known vulnerable builds prior to MS15-058: SQL Server 2008 SP3 (build 10.0.5500), SQL Server 2012 SP1 (build 11.0.3401), SQL Server 2014 RTM (build 12.0.2000)
    Affected if SQL Server is a pre-patch build and MS15-058 update has not been applied

User is affected if SQL Server 2008, 2012, or 2014 is running, the service is accessible to authenticated remote users, and the MS15-058 security update has not been installed.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the Microsoft security update (MS15-058) for this vulnerability. In the interim, minimize the attack surface by restricting database access to only necessary authenticated users, enforcing least privilege principles, and leveraging network-level isolation.

Fix this in Sql Server 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-2015-1763 — 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-2015-1763 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