Data EngineApplication · Microsoft

CVE-2008-0107

HIGH · 9.0 CVSS v2.0 Published 2008-07-08

Mitigation only

No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.

See remediation →

96/100

Remediation priority · Urgent

Remotely reachable Zero-click

Official description

NVD · unedited

Integer underflow in SQL Server 7.0 SP4, 2000 SP4, 2005 SP1 and SP2, 2000 Desktop Engine (MSDE 2000) SP4, 2005 Express Edition SP1 and SP2, and 2000 Desktop Engine (WMSDE); Microsoft Data Engine (MSDE) 1.0 SP4; and Internal Database (WYukon) SP2 allows remote authenticated users to execute arbitrary code via a (1) SMB or (2) WebDAV pathname for an on-disk file (aka stored backup file) with a crafted record size value, which triggers a heap-based buffer overflow, aka "SQL Server Memory Corruption Vulnerability."

Technical summary

dbcve analysis · high confidence

Integer underflow in SQL Server's handling of stored backup files allows remote authenticated attackers to trigger a heap-based buffer overflow by supplying a crafted record size value via SMB or WebDAV file paths, leading to arbitrary code execution.

MitigationApply Microsoft security patches for CVE-2008-0107 or upgrade to a supported SQL Server version. Restrict SMB/WebDAV access to untrusted networks and limit database privileges for authenticated users.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

Data EngineApplication

Affected:= 1.0

Sql ServerApplication

Affected:= 7.0= 2000= 2005

Sql Server Desktop EngineApplication

Affected:= 2000

WmsdeApplication

Affected:= 2000

WyukonApplication

Affected:all versions

Windows Server 2008Operating system

Affected:all versions

CVSS breakdown

From the vector

Attack vector: Network
Complexity: Low
Authentication: Single
Confidentiality: Complete
Integrity: Complete
Availability: Complete

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

Am I affected?

dbcve checks

Work through these to decide whether this CVE applies to you.

Identify SQL Server product and version

Run 'SELECT @@VERSION' query or check the SQL Server installation via SQL Server Configuration Manager or Windows Programs and Features

Affected if The installed version matches Microsoft Sql Server 7.0, 2000, or 2005; or Microsoft Data Engine 1.0; or Microsoft Sql Server Desktop Engine 2000; or Microsoft Wmsde 2000; or Microsoft Wyukon any version; or Windows Server 2008 any version (if SQL is running)
Confirm SMB or WebDAV access is available

Verify if the SQL Server host can access network shares via SMB or has WebDAV publishing enabled. Check network share configurations and IIS settings if WebDAV is relevant.

Affected if SMB or WebDAV is accessible to the SQL Server service, as this is the attack vector for supplying crafted backup file paths
Check SQL Server authentication mode

Review SQL Server security configuration via Enterprise Manager or by querying 'SELECT serverproperty("IsIntegratedSecurityOnly")'

Affected if SQL Server accepts SQL authentication (mixed mode) allowing remote authenticated attackers to connect and exploit the vulnerability
Verify backup or restore procedures are in use

Review SQL Server logs and job history for backup/restore operations that reference UNC paths (\\server\share) or investigate if any applications use stored backup files via WebDAV URLs

Affected if The environment uses SQL Server backup or restore operations referencing UNC paths or remote file locations accessible via SMB/WebDAV
Inspect SQL Server service account privileges

Check the service account running SQL Server services using Services.msc or 'sc query' command, and verify what network resources it can access

Affected if The SQL Server service runs with elevated privileges that could allow code execution after successful exploitation

A user is affected if their environment runs any of the vulnerable Microsoft Sql Server, Data Engine, Desktop Engine, Wmsde, Wyukon, or Windows Server 2008 with SQL components, and allows SMB/WebDAV access with authenticated user connections to trigger the backup file handling integer underflow.

Generated from the published advisory. Verify against your own configuration.

Remediation

dbcve · scoped

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Apply Microsoft security patches for CVE-2008-0107 or upgrade to a supported SQL Server version. Restrict SMB/WebDAV access to untrusted networks and limit database privileges for authenticated users.

Recommended fix High confidence

SQL Server 2005 to SP3 or later; SQL Server 2000 to latest available security update (MS08-040)

For SQL Server 2005 SP1/SP2: Apply SQL Server 2005 Service Pack 3 or later (download from Microsoft Update or the Microsoft Download Center)
For SQL Server 2000 SP4: Apply the MS08-040 security update from Microsoft (released July 8, 2008)
For SQL Server 7.0 SP4: Apply the MS08-040 security update from Microsoft
For MSDE 2000 SP4: Apply the MS08-040 security update
For MSDE 1.0 SP4: Apply the MS08-040 security update
For WYukon (Internal Database): Apply the MS08-040 security update

Caveat Service pack upgrades may require testing of existing applications; ensure backups before applying updates

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Data Engine Scoped from the published advisory

Consultation2.0 h
Implementation4.0 h
Testing3.0 h
Review / QA1.0 h

10.0 hours of engineering $1,750

Get help mitigating

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2008-0107 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2008-0107?

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.

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

At a glance

A fix existsA vendor remedy is published

Severity 9.0 High

Exploit likelihood EPSS, next 30 days 34.5%

Affects: Data Engine

Remediation

A high-priority fix

Fix this in Data Engine 10 hrs · Low

Typical engagement from $1,750

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2008-0107 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References