MS09-048: Vulnerabilities in Windows TCP/IP could allow remote code execution

Support for Windows Vista Service Pack 1 (SP1) ends on July 12, 2011. To continue receiving security updates for Windows, make sure you're running Windows Vista with Service Pack 2 (SP2). For more information, refer to this Microsoft web page: Support is ending for some versions of Windows.

INTRODUCTION

Microsoft has released security bulletin MS09-048. To view the complete security bulletin, visit one of the following Microsoft Web sites:

• Home users:

  http:⁠//www.microsoft.com/security/updates/bulletins/200909.aspx Skip the details: Download the updates for your home computer or laptop from the Microsoft Update Web site now:

  http:⁠//update.microsoft.com/microsoftupdate

• IT professionals:

  http:⁠//www.microsoft.com/technet/security/bulletin/MS09-048.mspx

How to obtain help and support for this security update

Help installing updates:
Support for Microsoft Update

Security solutions for IT professionals:
TechNet Security Troubleshooting and Support

Help protect your computer that is running Windows from viruses and malware:
Virus Solution and Security Center

Local support according to your country:
International Support

More Information

Known issues with this security update

• On a Windows Server 2008 Service Pack 2 (SP2)-based computer, the netsh int tcp reset command now also resets the following security parameters:

  • Memory Pressure Protection (MPP)

  • Profiles

  • Port Exemption

  • Connection Rate Limiting
    To restore the Connection Rate Limiting security parameter, you must enable the registry entry for the half-open TCP connections limit.

     For more information about how to do this, click the following article number to view the article in the Microsoft Knowledge Base:

    969710 How to enable the half-open TCP connections limit in Windows Vista with Service Pack 2 and in Windows Server 2008 with Service Pack 2

• On a Windows Server 2003-based computer, if you install the IPv6 connection protocol after you install this security update package, the event log description for IPv6 Event ID 4229 does not contain the relevant details of the event. Event ID 4229 is logged when an attack is detected, and there are no issues with the event being logged.

  To resolve this issue, you must reinstall this security update package or add the following registry key manually:

  Windows Server 2003 Service Pack 2

  Add the string %systemroot%system32\w03a3409.dll to the following registry key:
  HKEY_LOCAL_MACHINE\System\CCS\Services\eventlog\System\tcpipv6\EventMessageFile

For more information about the new Memory Pressure Protection feature for TCP stack, click the following article number to view the article in the Microsoft Knowledge Base:

974288 Description of the new Memory Pressure Protection feature for TCP stack

FILE INFORMATION

The English (United States) version of this software update installs files that have the attributes that are listed in the following tables. The dates and times for these files are listed in Coordinated Universal Time (UTC). The dates and times for these files on your local computer are displayed in your local time and with your current daylight saving time (DST) bias. Additionally, the dates and times may change when you perform certain operations on the files.

Windows Server 2003 file information

• The files that apply to a specific milestone (RTM, SPn) and service branch (QFE, GDR) are noted in the "SP requirement" and "Service branch" columns.
• GDR service branches contain only those fixes that are widely released to address widespread, critical issues. QFE service branches contain hotfixes in addition to widely released fixes.
• In addition to the files that are listed in these tables, this software update also installs an associated security catalog file (KBnumber.cat) that is signed with a Microsoft digital signature.

For all supported x64-based versions of Windows Server 2003

For all supported x86-based versions of Windows Server 2003

For all supported IA-64-based versions of Windows Server 2003

Windows Vista and Windows Server 2008 file information

• The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:

  Version	Product	Milestone	Service branch
  6.0.6000.16xxx	Windows Vista	RTM	GDR
  6.0.6000.20xxx	Windows Vista	RTM	LDR
  6.0.6001.18xxx	Windows Vista SP1 and Windows Server 2008 SP1	SP1	GDR
  6.0.6001.22xxx	Windows Vista SP1 and Windows Server 2008 SP1	SP1	LDR
  6.0.6002.18xxx	Windows Vista SP2 and Windows Server 2008 SP2	SP2	GDR
  6.0.6002.22xxx	Windows Vista SP2 and Windows Server 2008 SP2	SP2	LDR

• Service Pack 1 is integrated into the release version of Windows Server 2008. Therefore, RTM milestone files apply only to Windows Vista. RTM milestone files have a 6.0.0000.xxxxxx version number.

• GDR service branches contain only those fixes that are widely released to address widespread, critical issues. LDR service branches contain hotfixes in addition to widely released fixes.

• The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately. MUM and MANIFEST files, and the associated security catalog (.cat) files, are critical to maintaining the state of the updated component. The security catalog files (attributes not listed) are signed with a Microsoft digital signature.

For all supported x86-based versions of Windows Server 2008 and of Windows Vista