dbcve.org
Data EngineApplication · Microsoft

CVE-2002-1145

HIGH · 10.0 CVSS v2.0 Published 2002-10-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
The xp_runwebtask stored procedure in the Web Tasks component of Microsoft SQL Server 7.0 and 2000, Microsoft Data Engine (MSDE) 1.0, and Microsoft Desktop Engine (MSDE) 2000 can be executed by PUBLIC, which allows an attacker to gain privileges by updating a webtask that is owned by the database owner through the msdb.dbo.mswebtasks table, which does not have strong permissions.

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

The xp_runwebtask extended stored procedure in SQL Server 7.0/2000 and MSDE allows execution by the PUBLIC role, meaning any database user can invoke it. The vulnerability stems from weak permissions on the msdb.dbo.mswebtasks table, enabling authenticated attackers to update webtasks owned by the database owner and execute arbitrary code with dbo privileges, achieving privilege escalation.

MitigationRevoke EXECUTE permission on xp_runwebtask from PUBLIC, or drop the procedure if the Web Tasks component is unused; apply vendor patches for affected SQL Server versions.

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:= 1.0= 2000
Sql ServerApplication
Affected:= 7.0= 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
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/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. Confirm SQL Server version
    Run SELECT @@VERSION to retrieve the installed SQL Server or MSDE version number and edition.
    Affected if The version is 7.0 or 2000 for SQL Server, or 1.0 or 2000 for MSDE.
  2. Verify xp_runwebtask exists
    Run SELECT name FROM sysobjects WHERE name = 'xp_runwebtask' in the master database. If a row is returned, the procedure is installed.
    Affected if The procedure exists in the master database.
  3. Check PUBLIC permission on xp_runwebtask
    Run SELECT permission_name FROM master..syspermissions WHERE id = (SELECT id FROM master..sysobjects WHERE name = 'xp_runwebtask') AND grantee = 0 (PUBLIC role).
    Affected if PUBLIC role has EXECUTE permission granted on xp_runwebtask.
  4. Check msdb.dbo.mswebtasks table permissions
    Run SELECT permission_name FROM msdb..syspermissions WHERE id = (SELECT id FROM msdb..sysobjects WHERE name = 'mswebtasks') AND grantee = 0 (PUBLIC role).
    Affected if PUBLIC role has INSERT, UPDATE, or DELETE permission on msdb.dbo.mswebtasks.
  5. Verify current user context
    Run SELECT SYSTEM_USER, USER to confirm you are an authenticated database user (not a Windows-only login without SQL access).
    Affected if The query returns a valid database user name (authenticated SQL login).

You are affected if running SQL Server 7.0/2000 or MSDE 1.0/2000 with xp_runwebtask installed, PUBLIC granted EXECUTE on that procedure, weak permissions on msdb.dbo.mswebtasks, and you are any authenticated database user.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Revoke EXECUTE permission on xp_runwebtask from PUBLIC, or drop the procedure if the Web Tasks component is unused; apply vendor patches for affected SQL Server versions.

Recommended fix High confidence

Microsoft SQL Server 2016 or later, or Azure SQL Database

  1. This vulnerability affects SQL Server 7.0, SQL Server 2000, MSDE 1.0, and MSDE 2000, all of which have reached end of support and no longer receive security updates from Microsoft.
  2. Upgrade to a supported version of Microsoft SQL Server (SQL Server 2016 or later recommended) or migrate to Azure SQL Database.
  3. If an immediate upgrade is not possible, restrict network access to the database server and remove PUBLIC execute permissions on xp_runwebtask using: REVOKE EXECUTE ON xp_runwebtask FROM PUBLIC
  4. Ensure msdb database permissions are properly secured and not exposed to PUBLIC.
Caveat Legacy applications may require testing and potential code changes when migrating from SQL Server 2000 to newer versions

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
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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