CVE-2002-1123 in the critical feed json
Buffer overflow in the authentication function for Microsoft SQL Server 2000 and Microsoft Desktop Engine (MSDE) 2000 allows remote attacke…
published 2002-09-24 24 y ago modified 2026-06-16 4 mo ago also EUVD-2002-1111
- cvss
- 7.5
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 77.7%
- EPSS 77.7% chance of exploitation in 30 days, percentile 99.5%
- public exploits
- 3
- Metasploit, Exploit-DB
Summary
Buffer overflow in the authentication function for Microsoft SQL Server 2000 and Microsoft Desktop Engine (MSDE) 2000 allows remote attackers to execute arbitrary code via a long request to TCP port 1433, aka the "Hello" overflow.
Timeline
- First public exploit (Metasploit exploit/windows/mssql/ms02_056_hello)
- Published
Exploit prediction
77.71% chance of exploitation in the next 30 days, higher than 99.5% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- Metasploit exploit/windows/mssql/ms02_056_hello MS02-056 Microsoft SQL Server Hello Overflow metasploit exploit, good rank, 2002-08-05
- EDB-21693 Microsoft SQL Server 2000 - User Authentication Remote Buffer Overflow remote, 2002-08-06
- EDB-16398 Microsoft SQL Server - Hello Overflow (MS02-056) (Metasploit) remote, 2010-04-30
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
-
docs.microsoft.com
/en-us/security-updates/securitybulletins/2002/ms02-056
vendor-advisory
-
iss.net
/security_center/static/9788.php
vdb-entry, vendor-advisory
-
online.securityfocus.com
/archive/1/286220
mailing-list
-
securityfocus.com
/bid/5411
vdb-entry
-
ciac.org
/ciac/bulletins/n-003.shtml
third-party-advisory, government-resource
-
marc.info
/?l=bugtraq&m=102873609025020&w=2
mailing-list
Sources
- CVE List CVE-2002-1123
- NVD CVE-2002-1123
Fencer Vulns 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.