CVE-2002-0650
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 · uneditedThe keep-alive mechanism for Microsoft SQL Server 2000 allows remote attackers to cause a denial of service (bandwidth consumption) via a "ping" style packet to the Resolution Service (UDP port 1434) with a spoofed IP address of another SQL Server system, which causes the two servers to exchange packets in an infinite loop.
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 confidenceMicrosoft SQL Server 2000 contains a flaw in its keep-alive mechanism for the Resolution Service (UDP port 1434). Attackers can send a 'ping' packet with a spoofed source IP address pointing to another SQL Server system, causing the two servers to engage in an infinite packet exchange loop that consumes bandwidth and results in denial of service.
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
- None
- Integrity
- None
- Availability
- Partial
AV:N/AC:L/Au:N/C:N/I:N/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.
-
Confirm SQL Server 2000 is installedCheck the installed version by opening SQL Server Enterprise Manager, right-clicking the server and selecting Properties, or run 'SELECT @@VERSION' in SQL Query AnalyzerAffected if The version shown is Microsoft SQL Server 2000 (any edition or service pack)
-
Verify SQL Server Resolution Service is enabledOpen Services console (services.msc) and locate 'SQL Server Browser' service, or check if the service is running via command: 'net start | findstr SQL'Affected if The SQL Server Browser service is running or set to Automatic start
-
Confirm UDP port 1434 is listeningRun 'netstat -anp UDP | findstr 1434' from command prompt, or use a port scanner to verify UDP port 1434 is open on the serverAffected if UDP port 1434 is shown as listening or open
-
Check if port 1434 is externally accessibleRun a port scan from an external system or consult firewall rules: 'netsh advfirewall firewall show rule name=all' or check network perimeter firewall configurations for inbound UDP 1434 rulesAffected if UDP port 1434 is allowed through any firewall or exposed directly to untrusted networks
A system is affected if it runs SQL Server 2000 with the SQL Server Resolution Service enabled and UDP port 1434 is accessible to untrusted network segments.
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 dataBlock or restrict UDP port 1434 at the firewall to prevent external access to the SQL Server Resolution Service, or disable the SQL Server Browser service if not needed.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2002-0650 — 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-0650 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