dbcve.org
Data EngineApplication · Microsoft

CVE-2002-0644

HIGH · 7.5 CVSS v2.0 Published 2002-08-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
Buffer overflow in several Database Consistency Checkers (DBCCs) for Microsoft SQL Server 2000 and Microsoft Desktop Engine (MSDE) 2000 allows members of the db_owner and db_ddladmin roles to execute arbitrary code.

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

Buffer overflow vulnerability in SQL Server 2000 and MSDE 2000's Database Consistency Checker (DBCC) commands allows users with db_owner or db_ddladmin database roles to execute arbitrary code via specially crafted input, achieving elevated privileges on the database system.

MitigationApply Microsoft security patch for this vulnerability (refer to MS02-030 or subsequent SQL Server security bulletins); restrict db_owner and db_ddladmin role memberships to trusted personnel only; consider migrating to supported SQL Server versions as SQL Server 2000 is end-of-life.

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
Data EngineApplication
Affected:= 2000
Sql ServerApplication
Affected:= 2000

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
Low
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
Partial

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

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 or SELECT SERVERPROPERTY('ProductVersion'), SERVERPROPERTY('ProductName') to determine the installed SQL Server or MSDE version.
    Affected if The product version shows Microsoft SQL Server 2000 or Microsoft Data Engine (MSDE) 2000.
  2. Verify database role memberships
    Query sys.database_role_members joined to sys.database_principals to list users assigned to db_owner or db_ddladmin roles: SELECT r.name AS role_name, m.name AS member_name FROM sys.database_role_members rm JOIN sys.database_principals r ON rm.role_principal_id = r.principal_id JOIN sys.database_principals m ON rm.member_principal_id = m.principal_id WHERE r.name IN ('db_owner', 'db_ddladmin').
    Affected if Any non-administrative or untrusted user accounts are members of db_owner or db_ddladmin roles.
  3. Review recent DBCC command executions
    Check SQL Server error logs and default trace for DBCC commands. Query: SELECT StartTime, TextData FROM fn_trace_gettable(CONVERT(varchar(150), (SELECT TOP 1 value FROM sys.fn_trace_getinfo(NULL) WHERE property = 2)), DEFAULT) WHERE TextData LIKE '%DBCC%'.
    Affected if Any DBCC command executions appear from users who should not have elevated privileges.
  4. Confirm user privilege context
    Identify which users currently connect with db_owner or db_ddladmin privileges by checking application login mappings and database user mappings: SELECT dp.name AS database_user, sp.name AS server_login FROM sys.database_principals dp LEFT JOIN sys.server_principals sp ON dp.sid = sp.sid WHERE dp.type IN ('S', 'U') AND dp.name IN (SELECT member_name FROM sys.database_role_members rm JOIN sys.database_principals r ON rm.role_principal_id = r.principal_id WHERE r.name IN ('db_owner', 'db_ddladmin')).
    Affected if Multiple user accounts beyond trusted DBAs have db_owner or db_ddladmin role membership.

A user is affected if their environment runs SQL Server 2000 or MSDE 2000 and has untrusted accounts with db_owner or db_ddladmin database role membership, allowing potential privilege escalation via DBCC buffer overflow.

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 Microsoft security patch for this vulnerability (refer to MS02-030 or subsequent SQL Server security bulletins); restrict db_owner and db_ddladmin role memberships to trusted personnel only; consider migrating to supported SQL Server versions as SQL Server 2000 is end-of-life.

Fix this in Data Engine Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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