CVE-2002-0695
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 the Transact-SQL (T-SQL) OpenRowSet component of Microsoft Data Access Components (MDAC) 2.5 through 2.7 for SQL Server 7.0 or 2000 allows remote attackers to execute arbitrary code via a query that calls the OpenRowSet command.
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 Transact-SQL OpenRowSet component of Microsoft Data Access Components (MDAC) 2.5-2.7 allows remote attackers to execute arbitrary code via specially crafted queries targeting SQL Server 7.0 or 2000.
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= 1.5= 2.0= 2.1= 2.1.1.3711.11= 2.5= 2.6= 2.7= 2.12.4202.3= 2.12.4292.3_ga_cleanCVSS 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 installed MDAC versionOpen Registry Editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\DataAccess. Check the value of the 'Version' string entry. Alternatively, run 'reg query "HKLM\SOFTWARE\Microsoft\DataAccess" /v Version' from command prompt.Affected if The reported version matches 1.5, 2.0, 2.1, 2.1.1.3711.11, 2.5, 2.6, 2.7, 2.12.4202.3, or 2.12.4292.3_ga_clean exactly.
-
Confirm SQL Server versionConnect to the SQL Server instance and run 'SELECT @@VERSION' or check the SQL Server service version through SQL Server Enterprise Manager or via 'sqlservr -v' from command line in the Binn folder.Affected if The SQL Server version is 7.0 or 2000.
-
Check for OpenRowSet component availabilityVerify that the OpenRowSet function is accessible by attempting a simple query: 'SELECT * FROM OPENROWSET(...)' or check SQL Server configuration for ad hoc distributed queries using 'sp_configure' for 'ad hoc distributed queries' setting.Affected if OpenRowSet is enabled or the component is present in the MDAC installation.
-
Verify network exposure of SQL ServerReview SQL Server network configuration via SQL Server Network Utility (svrnetcn.exe) or check which TCP ports SQL Server is listening on (default 1433). Confirm if the server is accessible from network segments where untrusted users could send queries.Affected if SQL Server is listening on accessible network interfaces and accepts queries from untrusted sources.
You are affected if MDAC version 2.5, 2.6, 2.7, or 2.12.x is installed AND SQL Server 7.0 or 2000 is running with OpenRowSet functionality accessible to potential attackers.
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 this vulnerability (MS02-040) or upgrade to a supported SQL Server version, as SQL Server 7.0 and 2000 are end-of-life and no longer receive security updates.
- Consultation2.0 h
- Implementation4.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,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2002-0695 — 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-0695 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