CVE-2002-0641
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 · uneditedBuffer overflow in bulk insert procedure of Microsoft SQL Server 2000, including Microsoft SQL Server Desktop Engine (MSDE) 2000, allows attackers with database administration privileges to execute arbitrary code via a long filename in the BULK INSERT query.
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 confidenceBuffer overflow in the bulk insert procedure of Microsoft SQL Server 2000 and MSDE 2000 allows attackers with database administration privileges to execute arbitrary code by specifying an excessively long filename in a BULK INSERT query.
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= 2000= 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 or MSDE versionRun 'SELECT @@VERSION' in SQL Query Analyzer or execute 'SELECT SERVERPROPERTY('ProductVersion'), SERVERPROPERTY('ProductLevel')' to retrieve the installed version numberAffected if The version returned is 8.0.xxxx (SQL Server 2000) or the product shows as MSDE 2000
-
Verify current user privilegesRun 'SELECT IS_SRVROLEMEMBER('sysadmin')' to check if the current login has sysadmin server-level privileges, or 'SELECT IS_ROLEMEMBER('db_owner')' for database-level admin rightsAffected if The query returns 1 (true), indicating the current user has database administrator privileges
-
Check for BULK INSERT usage in recent activityEnable and review SQL Server Profiler traces or query the default trace (SELECT * FROM fn_trace_getinfo(NULL, DEFAULT)) for BULK INSERT events, or review application logs for BULK INSERT statementsAffected if BULK INSERT statements have been executed in the environment, particularly with file paths controlled by user input
-
Inspect for vulnerable BULK INSERT patternsSearch application code and stored procedures for BULK INSERT statements where the DATAFILE parameter accepts user-supplied input without validation (e.g., BULK INSERT table FROM 'user_input')Affected if BULK INSERT is used with unvalidated, potentially long file path parameters from user input
You are affected if running SQL Server 2000 or MSDE 2000, have a user with database admin privileges, and BULK INSERT with user-controlled file paths is in use.
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 the relevant Microsoft security patch (MS02-038 or successor) or upgrade to a supported SQL Server version. Restrict database administration privileges to minimize attack surface.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2002-0641 — 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-0641 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