CVE-2002-0982
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 · uneditedMicrosoft SQL Server 2000 SP2, when configured as a distributor, allows attackers to execute arbitrary code via the @scriptfile parameter to the sp_MScopyscript stored procedure.
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 confidenceThis is a code execution vulnerability in Microsoft SQL Server 2000 SP2 when configured as a replication distributor. The sp_MScopyscript stored procedure fails to properly validate the @scriptfile parameter, allowing authenticated attackers to inject and execute arbitrary operating system commands on the database server.
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= 2000CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify SQL Server versionRun 'SELECT @@VERSION' or 'EXEC xp_msver' in SQL Query Analyzer to confirm the installed version is Microsoft SQL Server 2000.Affected if The version shows Microsoft SQL Server 2000 (any build).
-
Check if replication distributor is configuredQuery the distribution database: SELECT name FROM msdb..MSdistpublishers or check SQL Server Enterprise Manager for replication configuration under Replication folder.Affected if This SQL Server instance is configured as a replication distributor with a distribution database.
-
Verify sp_MScopyscript stored procedure existsRun: USE distribution; SELECT name FROM sysobjects WHERE name = 'sp_MScopyscript' AND xtype = 'P'Affected if The stored procedure sp_MScopyscript exists in the distribution database.
-
Check execute permissions on sp_MScopyscriptRun: USE distribution; EXEC sp_helprotect 'sp_MScopyscript' or check if database users in the replicator role have execute rights.Affected if Authenticated database users (especially those in the replmonitor or replpublisher roles) can execute sp_MScopyscript.
If your environment runs Microsoft SQL Server 2000 configured as a replication distributor with sp_MScopyscript accessible to authenticated users, you are affected by this vulnerability.
Generated from the published advisory. Verify against your own configuration.
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 dataApply Microsoft security patches for SQL Server 2000, or if patching is not feasible, disable the sp_MScopyscript stored procedure and restrict database user permissions to prevent access to危险 stored procedures.
- Consultation4.0 h
- Implementation3.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2002-0982 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2002-0982 in production — separate from our analysis above.
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.
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.
- 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