Vulnerability Note VU#145134
Microsoft Windows Internet Naming Service (WINS) replication protocol contains a heap-based buffer overflow
A buffer overflow vulnerability in the Microsoft Windows Internet Naming Service (WINS) replication protocol may allow a remote attacker to execute arbitrary code or cause a denial-of-service condition.
The Microsoft WINS service maps IP addresses to NETBIOS computer names. WINS servers share information via a server-to-server replication protocol that operates on TCP port 42. Connection information for replication peers is stored in a data structure called the association context. Insufficient validation of the buffer where the association context data structure is written allows a heap-based buffer overflow to occur. If a remote attacker supplies a specially crafted replication packet to a vulnerable WINS server, that attacker may be able to exploit the buffer overflow to write arbitrary data to WINS server process memory.
According to Microsoft Knowledge Base Article 890710:
By default, WINS is not installed on Windows NT Server 4.0, Windows NT Server 4.0 Terminal Server Edition, Windows 2000 Server, or Windows Server 2003. By default, WINS is installed and running on Microsoft Small Business Server 2000 and Microsoft Windows Small Business Server 2003. By default, on all versions of Microsoft Small Business Server, the WINS component communication ports are blocked from the Internet, and WINS is available only on the local network.
Please refer to Microsoft Security Bulletin MS04-045 for more information regarding this vulnerability and its remediation.
A remote attacker may be able to execute arbitrary code with SYSTEM privileges or cause a denial-of-service condition.
Consider Workarounds in MS04-045
Systems Affected (Learn More)
|Vendor||Status||Date Notified||Date Updated|
|Microsoft Corporation||Affected||-||16 Dec 2004|
CVSS Metrics (Learn More)
This vulnerability was reported by Nicolas Waisman.
This document was written by Jeff Gennari.
- CVE IDs: CAN-2004-1080
- Date Public: 26 Nov 2004
- Date First Published: 29 Nov 2004
- Date Last Updated: 17 Dec 2004
- Severity Metric: 26.29
- Document Revision: 150
If you have feedback, comments, or additional information about this vulnerability, please send us email.