CVSS2
Attack Vector
NETWORK
Attack Complexity
LOW
Authentication
NONE
Confidentiality Impact
PARTIAL
Integrity Impact
PARTIAL
Availability Impact
PARTIAL
AV:N/AC:L/Au:N/C:P/I:P/A:P
EPSS
Percentile
99.6%
Microsoft SQL Server 2000 contains a remotely exploitable stack buffer overflow that allows attackers to execute arbitrary code with the same privileges as the SQL server.
The SQL Server Resolution Service (SSRS) was introduced in Microsoft SQL Server 2000 to provide referral services for multiple server instances running on the same machine. The service listens for requests on UDP port 1434 and returns the IP address and port number of the SQL server instance that provides access to the requested database.
The SSRS contains a stack buffer overflow that allows an attacker to execute arbitrary code by sending a crafted request to port 1434/udp. The code within such a request will be executed by the server host with the privileges of the SQL Server service account.
This vulnerability allows unauthenticated remote attackers to execute arbitrary code with the privileges of the SQL service account. If the privileges of the service account are elevated via VU#796313, this vulnerability may result in compromise of the server host.
Apply a patch
This vulnerability was originally addressed by Microsoft in Security Bulletin MS02-039. In January 2003, Microsoft updated MS02-039 to recommend that customers apply the patch from Microsoft Security Bulletin MS02-061, which addresses additional vulnerabilities. For more information, please see
http://www.microsoft.com/technet/security/bulletin/MS02-039.asp
http://www.microsoft.com/technet/security/bulletin/MS02-061.asp
This vulnerability also affects any products that include the Microsoft Desktop Engine (MSDE) 2000. For more information, please see
http://www.microsoft.com/technet/security/MSDEapps.asp
Block port 1434/udp
As a workaround, system administrators can use a firewall to block port 1434/udp at an appropriate network border, thus preventing external attackers from exploiting this vulnerability.
484891
Filter by status: All Affected Not Affected Unknown
Filter by content: __ Additional information available
__ Sort by: Status Alphabetical
Expand all
Javascript is disabled. Click here to view vendors.
Notified: February 13, 2003 Updated: February 20, 2003
Affected
Approximately 24 hours after the announcement of the vulnerability exploited by SQL Slammer (aka, Sapphire) in July, 2002, BindView provided it’s customers with a tool for identifying vulnerable systems. BindView products have a requirement for customers to use either MSDE or SQL, which are vulnerable if unpatched. Guidance provided to customers at that time recommended immediate installation of the patches to correct the vulnerability. BindView re-issued both the tools and the guidance immediately after the initial outbreak of SQL Slammer.
Technical Note: Where BindView products require MSDE or SQL installed, the patches published by Microsoft will support BindView installations. No additional special patches are required.
The vendor has not provided us with any further information regarding this vulnerability.
The CERT/CC has no additional comments at this time.
If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%23484891 Feedback>).
Notified: January 26, 2003 Updated: January 27, 2003
Affected
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
Cisco Systems has published an Cisco Security Advisory to address this issue. For more information, please see:
http://www.cisco.com/warp/public/707/cisco-sa-20030126-ms02-061.shtml
If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%23484891 Feedback>).
Notified: March 04, 2003 Updated: March 06, 2003
Affected
The following link is provided for our customers:
<http://www.expressmetrix.com/techdocs/1610.asp>
The vendor has not provided us with any further information regarding this vulnerability.
The CERT/CC has no additional comments at this time.
If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%23484891 Feedback>).
Notified: February 13, 2003 Updated: February 20, 2003
Affected
SSRT3481 - HP OpenView, HP Insight Manager, HP SANworks Management Appliance (the Slammer SQL Worm) Patch Information
This bulletin was posted to the support website within 24 hours of release to - www.hp.com Use the SEARCH IN feature box, enter SSRT3481 in the search window.
The vendor has not provided us with any further information regarding this vulnerability.
The CERT/CC has no additional comments at this time.
If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%23484891 Feedback>).
Notified: March 04, 2003 Updated: March 26, 2003
Affected
The Kaseya Virtual System Administrator comes bundled with Microsoft
Desktop Engine (MSDE) version 8.00.194. If your VSA is on a network
and has port 1433 or 1434 open to the internal or external network
then your system is vulnerable. To close this vulnerability apply the
Microsoft’s SP3 for MSDE. We have posted instructions for applying
the latest MSDE service pack on our web site at
<http://www.kaseya.com/support/kbase/article10012.phtml>
The vendor has not provided us with any further information regarding this vulnerability.
The CERT/CC has no additional comments at this time.
If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%23484891 Feedback>).
Notified: March 04, 2003 Updated: March 05, 2003
Affected
Our advice is to have customers using MSDE SP2 version install the
security patch roll-up available for SP2 installations to fix this
(and other) issues. Customers who have the SP1 installation, or
those unsure of the version installed are urged to contact Lightspeed
Systems Customer Support immediately for assistance.
This information is summarized here:
<http://updates.lightspeedsystems.com/>
The vendor has not provided us with any further information regarding this vulnerability.
The CERT/CC has no additional comments at this time.
If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%23484891 Feedback>).
Notified: May 31, 2002 Updated: July 25, 2002
Affected
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
Microsoft has published Security Bulletin MS02-039 to address this vulnerability. For more information, please see
http://www.microsoft.com/technet/security/bulletin/MS02-039.asp
If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%23484891 Feedback>).
Notified: March 04, 2003 Updated: March 04, 2003
Affected
We have issued a statement on the Slammer worm at the following URL:
<http://www.smallwonders.com/Support/slammer.htm>
This gives technical specs on how to update MSDE 2000 with SP3.
Additionally, all new downloads include the MSDE 2000 with SP3.
The vendor has not provided us with any further information regarding this vulnerability.
The CERT/CC has no additional comments at this time.
If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%23484891 Feedback>).
Notified: February 13, 2003 Updated: May 20, 2003
Affected
<http://seer.support.veritas.com/docs/254244.htm>
The vendor has not provided us with any further information regarding this vulnerability.
The CERT/CC has no additional comments at this time.
If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%23484891 Feedback>).
Notified: March 04, 2003 Updated: May 20, 2003
Affected
SecureScan NX
SecureScan NX ships with MSDE. In order to protect existing installations, we urge all customers to update to MSDE SP3. SecureScan NX is fully supported on MSDE SP3.
A FAQ item has been posted on our website on how to update: <http://support.vigilante.com/faq/>
VIGILANTe now ships a new version of SecureScan NX setup program that installs MSDE SP3 and is not affected by this vulnerability.
SecureScan SP
SecureScan SP does not ship with MSDE. However, SecureScan SP needs access to an MS SQL Server for proper installation. SecureScan SP users need to make sure their SQL Servers are not affected by this vulnerability. SecureScan SP is fully supported on MS SQL Server SP 3.
The vendor has not provided us with any further information regarding this vulnerability.
The CERT/CC has no additional comments at this time.
If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%23484891 Feedback>).
Notified: February 13, 2003 Updated: February 20, 2003
Affected
A response to this advisory is available from our Security
Information site: <http://www.xerox.com/security>.
The vendor has not provided us with any further information regarding this vulnerability.
The CERT/CC has no additional comments at this time.
If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%23484891 Feedback>).
Notified: March 04, 2003 Updated: March 13, 2003
Not Affected
MonTel is a Telephone call accounting system with a server and clients for use
on a computer network. A default installation of MonTel is not vulnerable to
the ‘Slammer’ worm since it only installs MSDE 1.0. (MonTel is also provided
with the MS Jet engine for use on small work groups, though this is being
phased out in favour of MSDE.)
MonTel can, however, also be used on a pre-existing MS SQL Server 2000, which
is vulnerable. SQL 2000 should be fully secured and the latest patches applied.
Details of this can be found at:
http://www.microsoft.com/technet/treeview/default.asp?url=/technet/security/bul
letin/MS02-039.asp.
For MSDE 1.0 we recommend that MonTel sites apply the Service Pack 4 patch for
Microsoft SQL 7.0 which is used to also patch MSDE 1.0 and the SQL Server 7.0
Security Update for Service Pack 4. More detail on where to find these, and
other information can be found on the Netwiz web site at
<http://www.netwiz.com.au/appnotes/i3154.htm>.
The vendor has not provided us with any further information regarding this vulnerability.
The CERT/CC has no additional comments at this time.
If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%23484891 Feedback>).
Notified: February 03, 2003 Updated: February 06, 2003
Not Affected
Current Nortel Networks products and solutions do not ship with Microsoft SQL Server 2000. However, due to the high volume of traffic generated between other vendors’ impacted systems running Microsoft SQL Server 2000, some Nortel Networks switches may experience high CPU utilization leading to traffic congestion.
Nortel Networks recommends following the ingress/egress filtering mitigation strategies outlined by CERT in the “Solutions” section of Advisory CA-2003-04. Product-specific bulletins with instructions for configuration of ingress filters are available from the following Nortel Networks support contacts:
North America: 1-800-4NORTEL or 1-800-466-7835
Europe, Middle East and Africa: 00800 8008 9009, or +44 (0) 870 907 9009
The vendor has not provided us with any further information regarding this vulnerability.
The CERT/CC has no additional comments at this time.
If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%23484891 Feedback>).
Notified: March 04, 2003 Updated: March 18, 2003
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
The CERT/CC has no additional comments at this time.
If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%23484891 Feedback>).
Notified: March 04, 2003 Updated: March 17, 2003
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
The CERT/CC has no additional comments at this time.
If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%23484891 Feedback>).
Notified: March 04, 2003 Updated: March 11, 2003
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
The CERT/CC has no additional comments at this time.
If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%23484891 Feedback>).
Notified: February 13, 2003 Updated: February 20, 2003
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
The CERT/CC has no additional comments at this time.
If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%23484891 Feedback>).
Notified: February 13, 2003 Updated: February 20, 2003
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
The CERT/CC has no additional comments at this time.
If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%23484891 Feedback>).
Notified: March 04, 2003 Updated: March 05, 2003
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
The CERT/CC has no additional comments at this time.
If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%23484891 Feedback>).
Notified: February 13, 2003 Updated: February 20, 2003
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
The CERT/CC has no additional comments at this time.
If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%23484891 Feedback>).
Notified: February 13, 2003 Updated: February 20, 2003
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
The CERT/CC has no additional comments at this time.
If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%23484891 Feedback>).
Notified: February 13, 2003 Updated: February 20, 2003
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
The CERT/CC has no additional comments at this time.
If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%23484891 Feedback>).
Notified: February 13, 2003 Updated: February 20, 2003
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
The CERT/CC has no additional comments at this time.
If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%23484891 Feedback>).
Notified: March 04, 2003 Updated: March 05, 2003
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
The CERT/CC has no additional comments at this time.
If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%23484891 Feedback>).
Notified: March 04, 2003 Updated: March 05, 2003
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
The CERT/CC has no additional comments at this time.
If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%23484891 Feedback>).
Notified: March 04, 2003 Updated: March 05, 2003
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
The CERT/CC has no additional comments at this time.
If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%23484891 Feedback>).
Notified: March 04, 2003 Updated: March 17, 2003
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
The CERT/CC has no additional comments at this time.
If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%23484891 Feedback>).
Notified: March 04, 2003 Updated: March 05, 2003
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
The CERT/CC has no additional comments at this time.
If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%23484891 Feedback>).
Notified: March 04, 2003 Updated: March 17, 2003
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
The CERT/CC has no additional comments at this time.
If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%23484891 Feedback>).
Notified: March 04, 2003 Updated: March 05, 2003
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
The CERT/CC has no additional comments at this time.
If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%23484891 Feedback>).
Notified: March 04, 2003 Updated: March 11, 2003
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
The CERT/CC has no additional comments at this time.
If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%23484891 Feedback>).
Notified: March 04, 2003 Updated: March 06, 2003
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
The CERT/CC has no additional comments at this time.
If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%23484891 Feedback>).
Notified: March 04, 2003 Updated: March 05, 2003
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
The CERT/CC has no additional comments at this time.
If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%23484891 Feedback>).
Notified: March 04, 2003 Updated: March 07, 2003
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
The CERT/CC has no additional comments at this time.
If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%23484891 Feedback>).
Notified: February 13, 2003 Updated: February 20, 2003
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
The CERT/CC has no additional comments at this time.
If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%23484891 Feedback>).
Notified: February 13, 2003 Updated: February 20, 2003
Unknown
We have not received a statement from the vendor.
The vendor has not provided us with any further information regarding this vulnerability.
The CERT/CC has no additional comments at this time.
If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%23484891 Feedback>).
View all 36 vendors __View less vendors __
Group | Score | Vector |
---|---|---|
Base | ||
Temporal | ||
Environmental |
The CERT/CC thanks Microsoft for the information provided in their advisory and NGSSoftware for their discovery and analysis of this vulnerability.
This document was written by Jeffrey P. Lanza.
CVE IDs: | CVE-2002-0649 |
---|---|
CERT Advisory: | CA-2002-22 Severity Metric: |
online.securityfocus.com/bid/5311
support.microsoft.com/support/misc/kblookup.asp?id=Q323875
www.cert.org/advisories/CA-2003-04.html
www.microsoft.com/technet/prodtechnol/sql/maintain/security/sql2ksec.asp
www.microsoft.com/technet/security/bulletin/MS02-039.asp
www.microsoft.com/technet/security/MSDEapps.asp
www.microsoft.com/technet/security/virus/alerts/slammer.asp
www.nextgenss.com/advisories/mssql-udp.txt
www.nextgenss.com/vna/ms-sql.txt