CVE-2002-0186 in the critical feed json
Buffer overflow in the SQLXML ISAPI extension of Microsoft SQL Server 2000 allows remote attackers to execute arbitrary code via data queri…
published 24y ago modified 4mo ago also EUVD-2002-0183
- cvss
- 7.5
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 55.5%
- EPSS 55.5% chance of exploitation in 30 days, percentile 99%
- public exploits
- 1
- Exploit-DB
Summary
Buffer overflow in the SQLXML ISAPI extension of Microsoft SQL Server 2000 allows remote attackers to execute arbitrary code via data queries with a long content-type parameter, aka "Unchecked Buffer in SQLXML ISAPI Extension."
Patch / fix
Is CVE-2002-0186 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerTimeline
- First public exploit (EDB-21540)
- Published
Exploit prediction
55.46% chance of exploitation in the next 30 days, higher than 99% of all scored CVEs (FIRST EPSS, 2026-11-14).
Exploits and checks
- EDB-21540 Microsoft SQL Server 2000 - 'SQLXML' Buffer Overflow (PoC) dos, 2002-06-12
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
Classification
- Technology feeds
References
-
archives.neohapsis.com
/archives/vulnwatch/2002-q2/0100.html
mailing-list, patch, vendor-advisory
-
docs.microsoft.com
/en-us/security-updates/securitybulletins/2002/ms02-030
vendor-advisory
-
kb.cert.org
/vuls/id/811371
third-party-advisory, us-government-resource
-
osvdb.org
/5347
vdb-entry
-
securityfocus.com
/bid/5004
vdb-entry
-
iss.net
/security_center/static/9328.php
vdb-entry
-
oval.cisecurity.org
/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A484
vdb-entry, signature
-
oval.cisecurity.org
/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A489
vdb-entry, signature
-
marc.info
/?l=bugtraq&m=102397345410856&w=2
mailing-list
Sources
- CVE List CVE-2002-0186
- NVD CVE-2002-0186
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.