Vulnerability Note VU#333636

Microsoft Server Service may disclose information used to store SMB traffic

Original Release date: 20 Jul 2006 | Last revised: 20 Jul 2006


A vulnerability in the Microsoft Server service may allow an attacker to view fragments of memory used to store SMB traffic.


Microsoft Server Service
The Microsoft Server service supports file, print, and named-pipe sharing over the network.

Server Message Block
Server Message Block (SMB) is a protocol used to share files and printers, and is the default file and print sharing service on supported versions of the Windows operating system.

There is an uninitialized buffer in the Server driver that may allow an attacker to view contents of the SMB buffers.


This vulnerability may result in information being disclosed that would aid in launching other attacks on the affected system. An attacker could not exploit this vulnerability to run arbitrary code.

Note that per Microsoft, other protocols such as Internetwork Packet Exchange (IPX) and Sequenced Packet Exchange (SPX) could also be vulnerable to this issue.


Apply a Patch from the Vendor

Apply the patch supplied by Microsoft. See Microsoft Security Bulletin MS06-035 for details.

Restrict Access
Per Microsoft, restricting access to ports 139/tcp and 445/tcp to trusted hosts may prevent this vulnerability from being exploited.

Systems Affected (Learn More)

VendorStatusDate NotifiedDate Updated
Microsoft CorporationUnknown11 Jul 200619 Jul 2006
If you are a vendor and your product is affected, let us know.

CVSS Metrics (Learn More)

Group Score Vector
Base N/A N/A
Temporal N/A N/A
Environmental N/A N/A



Microsoft Security reported this issue. Microsoft credits Mike Price and Rafal Wojtczuk of McAfee Avert Labs with reporting information about this issue to them.

This document was written by Ryan Giobbi.

Other Information

  • CVE IDs: CVE-2006-1315
  • Date Public: 11 Jul 2006
  • Date First Published: 20 Jul 2006
  • Date Last Updated: 20 Jul 2006
  • Severity Metric: 0.39
  • Document Revision: 15


If you have feedback, comments, or additional information about this vulnerability, please send us email.