Security Bulletin
Microsoft Security Bulletin MS08-036 - Important
Vulnerabilities in Pragmatic General Multicast (PGM) Could Allow Denial of Service (950762)
Published: June 10, 2008 | Updated: February 17, 2010
Version: 1.1
General Information
Executive Summary
This security update resolves two privately reported vulnerabilities in the Pragmatic General Multicast (PGM) protocol that could allow a denial of service if malformed PGM packets are received by an affected system. An attacker who successfully exploited this vulnerability could cause a user’s system to become non-responsive and to require a restart to restore functionality. Note that the denial of service vulnerability would not allow an attacker to execute code or to elevate their user rights, but it could cause the affected system to stop accepting requests.
This security update is rated Important for all supported editions of Windows XP and Windows Server 2003 and rated Moderate for all supported editions of Windows Vista and Windows Server 2008. For more information, see the subsection, Affected and Non-Affected Software, in this section.
The security update addresses these vulnerabilities by modifying the way PGM parses malformed packets. For more information about the vulnerability, see the Frequently Asked Questions (FAQ) subsection for the specific vulnerability entry under the next section, Vulnerability Information.
Recommendation. Microsoft recommends that customers apply the update at the earliest opportunity.
Known Issues. Microsoft Knowledge Base Article 950762 documents the currently known issues that customers may experience when installing this security update. The article also documents recommended solutions for these issues. When currently known issues and recommended solutions pertain only to specific releases of this software, this article provides links to further articles.
Affected and Non-Affected Software
The following software have been tested to determine which versions or editions are affected. Other versions or editions are either past their support life cycle or are not affected. To determine the support life cycle for your software version or edition, visit Microsoft Support Lifecycle.
Affected Software
*Supported editions of Windows Server 2008 are not affected if installed using the Server Core installation option. For more information on this installation option, see Server Core. Note that the Server Core installation option does not apply to certain editions of Windows Server 2008; see Compare Server Core Installation Options.
Non-Affected Software
Operating System |
---|
Windows 2000 Service Pack 4 |
Frequently Asked Questions (FAQ) Related to This Security Update
Where are the file information details?
The file information details can be found in Microsoft Knowledge Base Article 950762.
Why does this update address several reported security vulnerabilities?
This update contains support for several vulnerabilities because the modifications that are required to address these issues are located in related files. Instead of having to install several updates that are almost the same, customers need to install this update only.
I am using an older release of the software discussed in this security bulletin. What should I do?
The affected software listed in this bulletin have been tested to determine which releases are affected. Other releases are past their support life cycle. To determine the support life cycle for your software release, visit Microsoft Support Lifecycle.
It should be a priority for customers who have older releases of the software to migrate to supported releases to prevent potential exposure to vulnerabilities. For more information about the Windows Product Lifecycle, visit Microsoft Support Lifecycle. For more information about the extended security update support period for these software versions or editions, visit Microsoft Product Support Services.
Customers who require custom support for older releases must contact their Microsoft account team representative, their Technical Account Manager, or the appropriate Microsoft partner representative for custom support options. Customers without an Alliance, Premier, or Authorized Contract can contact their local Microsoft sales office. For contact information, visit Microsoft Worldwide Information, select the country, and then click Go to see a list of telephone numbers. When you call, ask to speak with the local Premier Support sales manager. For more information, see the Windows Operating System Product Support Lifecycle FAQ.
Vulnerability Information
Severity Ratings and Vulnerability Identifiers
Affected Software | PGM Invalid Length Vulnerability - CVE-2008-1440 | PGM Malformed Fragment Vulnerability - CVE-2008-1441 | Aggregate Severity Rating |
---|---|---|---|
Windows XP Service Pack 2 | Important Denial of Service |
Moderate Denial of Service |
Important |
Windows XP Service Pack 3 | Important Denial of Service |
Moderate Denial of Service |
Important |
Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2 | Important Denial of Service |
Moderate Denial of Service |
Important |
Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2 | Important Denial of Service |
Moderate Denial of Service |
Important |
Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2 | Important Denial of Service |
Moderate Denial of Service |
Important |
Windows Server 2003 with SP1 for Itanium-based Systems and Windows Server 2003 with SP2 for Itanium-based Systems | Important Denial of Service |
Moderate Denial of Service |
Important |
Windows Vista and Windows Vista Service Pack 1 | Not affected | Moderate Denial of Service |
Moderate |
Windows Vista x64 Edition and Windows Vista x64 Edition Service Pack 1 | Not affected | Moderate Denial of Service |
Moderate |
Windows Server 2008 for 32-bit Systems\* | Not affected | Moderate Denial of Service |
Moderate |
Windows Server 2008 for x64-based Systems\* | Not affected | Moderate Denial of Service |
Moderate |
Windows Server 2008 for Itanium-based Systems | Not affected | Moderate Denial of Service |
Moderate |
Inclusion in Future Service Packs | The update for this issue will be included in a future service pack or update rollup |
Deployment | |
Installing without user intervention | For all supported 32-bit editions of Windows XP: Windowsxp-kb950762-x86-enu /quiet |
For all supported x64-based editions of Windows XP: WindowsServer2003.WindowsXP-kb950762-x64-enu /quiet |
|
Installing without restarting | For all supported 32-bit editions of Windows XP: Windowsxp-kb950762-x86-enu /norestart |
For all supported x64-based editions of Windows XP: WindowsServer2003.WindowsXP-kb950762-x64-enu /norestart |
|
Update log file | KB950762.log |
Further information | See the subsection, Detection and Deployment Tools and Guidance |
Restart Requirement | |
Restart required? | Yes, you must restart your system after you apply this security update. |
HotPatching | Not applicable |
Removal Information | Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallKB950762$\Spuninst folder |
File Information | See Microsoft Knowledge Base Article 950762 |
Registry Key Verification | For all supported 32-bit editions of Windows XP: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP\SP4\KB950762\Filelist |
For all supported x64-based editions of Windows XP: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP Version 2003\SP3\KB950762\Filelist |
Note For supported versions of Windows XP Professional x64 Edition, this security update is the same as supported versions of the Windows Server 2003 x64 Edition security update.
Deployment Information
Installing the Update
When you install this security update, the installer checks whether one or more of the files that are being updated on your system have previously been updated by a Microsoft hotfix.
If you have previously installed a hotfix to update one of these files, the installer copies the RTMQFE, SP1QFE, or SP2QFE files to your system. Otherwise, the installer copies the RTMGDR, SP1GDR, or SP2GDR files to your system. Security updates may not contain all variations of these files. For more information about this behavior, see Microsoft Knowledge Base Article 824994.
For more information about the installer, visit the Microsoft TechNet Web site.
For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.
This security update supports the following setup switches.
Switch | Description |
---|---|
**/help** | Displays the command-line options. |
Setup Modes | |
**/passive** | Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds. |
**/quiet** | Quiet mode. This is the same as unattended mode, but no status or error messages are displayed. |
Restart Options | |
**/norestart** | Does not restart when installation has completed. |
**/forcerestart** | Restarts the computer after installation and force other applications to close at shutdown without saving open files first. |
**/warnrestart\[:x\]** | Presents a dialog box with a timer warning the user that the computer will restart in *x* seconds. (The default setting is 30 seconds.) Intended for use with the **/quiet** switch or the **/passive** switch. |
**/promptrestart** | Displays a dialog box prompting the local user to allow a restart. |
Special Options | |
**/overwriteoem** | Overwrites OEM files without prompting. |
**/nobackup** | Does not back up files needed for uninstall. |
**/forceappsclose** | Forces other programs to close when the computer shuts down. |
**/log:path** | Allows the redirection of installation log files. |
**/integrate:path** | Integrates the update into the Windows source files. These files are located at the path that is specified in the switch. |
**/extract\[:path\]** | Extracts files without starting the Setup program. |
**/ER** | Enables extended error reporting. |
**/verbose** | Enables verbose logging. During installation, creates %Windir%\\CabBuild.log. This log details the files that are copied. Using this switch may cause the installation to proceed more slowly. |
Removing the Update
This security update supports the following setup switches.
Switch | Description |
---|---|
**/help** | Displays the command-line options. |
Setup Modes | |
**/passive** | Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds. |
**/quiet** | Quiet mode. This is the same as unattended mode, but no status or error messages are displayed. |
Restart Options | |
**/norestart** | Does not restart when installation has completed |
**/forcerestart** | Restarts the computer after installation and force other applications to close at shutdown without saving open files first. |
**/warnrestart\[:x\]** | Presents a dialog box with a timer warning the user that the computer will restart in *x* seconds. (The default setting is 30 seconds.) Intended for use with the **/quiet** switch or the **/passive** switch. |
**/promptrestart** | Displays a dialog box prompting the local user to allow a restart. |
Special Options | |
**/forceappsclose** | Forces other programs to close when the computer shuts down. |
**/log:path** | Allows the redirection of installation log files. |
Microsoft Baseline Security Analyzer
To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information.
File Version Verification
Because there are several editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps.
- Click Start, and then click Search.
- In the Search Results pane, click All files and folders under Search Companion.
- In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
- In the list of files, right-click a file name from the appropriate file information table, and then click Properties.
Note Depending on the edition of the operating system, or the programs that are installed on your system, some of the files that are listed in the file information table may not be installed. - On the Version tab, determine the version of the file that is installed on your system by comparing it to the version that is documented in the appropriate file information table.
Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.
Registry Key Verification
You may also be able to verify the files that this security update has installed by reviewing the registry keys listed in the Reference Table in this section.
These registry keys may not contain a complete list of installed files. Also, these registry keys may not be created correctly when an administrator or an OEM integrates or slipstreams this security update into the Windows installation source files.
Windows Server 2003 (all editions)
Reference Table
The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section.
Inclusion in Future Service Packs | The update for this issue will be included in a future service pack or update rollup |
Deployment | |
Installing without user intervention | For all supported 32-bit editions of Windows Server 2003: Windowsserver2003-kb950762-x86-enu /quiet |
For all supported x64-based editions of Windows Server 2003: Windowsserver2003.WindowsXP-KB950762-x64-enu /quiet |
|
For all supported Itanium-based editions of Windows Server 2003: Windowsserver2003-KB950762-ia64-enu /quiet |
|
Installing without restarting | For all supported 32-bit editions of Windows Server 2003: Windowsserver2003-kb950762-x86-enu /norestart |
For all supported x64-based editions of Windows Server 2003: Windowsserver2003.WindowsXP-KB950762-x64-enu /norestart |
|
For all supported Itanium-based editions of Windows Server 2003: Windowsserver2003-KB950762-ia64-enu /norestart |
|
Update log file | KB950762.log |
Further information | See the subsection, Detection and Deployment Tools and Guidance |
Restart Requirement | |
Restart required? | Yes, you must restart your system after you apply this security update. |
HotPatching | This security update does not support HotPatching. For more information about HotPatching, see Microsoft Knowledge Base Article 897341. |
Removal Information | Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallKB950762$\Spuninst folder |
File Information | See Microsoft Knowledge Base Article 950762 |
Registry Key Verification | HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB950762\Filelist |
Switch | Description |
---|---|
**/help** | Displays the command-line options. |
Setup Modes | |
**/passive** | Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds. |
**/quiet** | Quiet mode. This is the same as unattended mode, but no status or error messages are displayed. |
Restart Options | |
**/norestart** | Does not restart when installation has completed. |
**/forcerestart** | Restarts the computer after installation and force other applications to close at shutdown without saving open files first. |
**/warnrestart\[:x\]** | Presents a dialog box with a timer warning the user that the computer will restart in *x* seconds. (The default setting is 30 seconds.) Intended for use with the **/quiet** switch or the **/passive** switch. |
**/promptrestart** | Displays a dialog box prompting the local user to allow a restart. |
Special Options | |
**/overwriteoem** | Overwrites OEM files without prompting. |
**/nobackup** | Does not back up files needed for uninstall. |
**/forceappsclose** | Forces other programs to close when the computer shuts down. |
**/log:path** | Allows the redirection of installation log files. |
**/integrate:path** | Integrates the update into the Windows source files. These files are located at the path that is specified in the switch. |
**/extract\[:path\]** | Extracts files without starting the Setup program. |
**/ER** | Enables extended error reporting. |
**/verbose** | Enables verbose logging. During installation, creates %Windir%\\CabBuild.log. This log details the files that are copied. Using this switch may cause the installation to proceed more slowly. |
Removing the Update
This security update supports the following setup switches.
Switch | Description |
---|---|
**/help** | Displays the command-line options. |
Setup Modes | |
**/passive** | Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds. |
**/quiet** | Quiet mode. This is the same as unattended mode, but no status or error messages are displayed. |
Restart Options | |
**/norestart** | Does not restart when installation has completed. |
**/forcerestart** | Restarts the computer after installation and force other applications to close at shutdown without saving open files first. |
**/warnrestart\[:x\]** | Presents a dialog box with a timer warning the user that the computer will restart in *x* seconds. (The default setting is 30 seconds.) Intended for use with the **/quiet** switch or the **/passive** switch. |
**/promptrestart** | Displays a dialog box prompting the local user to allow a restart. |
Special Options | |
**/forceappsclose** | Forces other programs to close when the computer shuts down. |
**/log:path** | Allows the redirection of installation log files. |
Microsoft Baseline Security Analyzer
To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information.
File Version Verification
Because there are several editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps.
- Click Start, and then click Search.
- In the Search Results pane, click All files and folders under Search Companion.
- In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
- In the list of files, right-click a file name from the appropriate file information table, and then click Properties.
Note Depending on the edition of the operating system, or the programs that are installed on your system, some of the files that are listed in the file information table may not be installed. - On the Version tab, determine the version of the file that is installed on your system by comparing it to the version that is documented in the appropriate file information table.
Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.
Registry Key Verification
You may also be able to verify the files that this security update has installed by reviewing the registry keys listed in the Reference Table in this section.
These registry keys may not contain a complete list of installed files. Also, these registry keys may not be created correctly when an administrator or an OEM integrates or slipstreams this security update into the Windows installation source files.
Windows Vista (all editions)
Reference Table
The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section.
Inclusion in Future Service Packs | The update for this issue will be included in a future service pack or update rollup |
Deployment | |
Installing without user intervention | For all supported 32-bit editions of Windows Vista: Windows6.0-KB950762-x86 /quiet For all supported x64-based editions of Windows Vista: Windows6.0-KB950762-x64 /quiet |
Installing without restarting | For all supported 32-bit editions of Windows Vista: Windows6.0-KB950762-x86 /quiet /norestart For all supported x64-based editions of Windows Vista: Windows6.0-KB950762-x64 /quiet /norestart |
Further information | See the subsection, Detection and Deployment Tools and Guidance |
Restart Requirement | |
Restart required? | Yes, you must restart your system after you apply this security update. |
HotPatching | Not applicable. |
Removal Information | WUSA.exe does not support uninstall of updates. To uninstall an update installed by WUSA, click Control Panel, and then click Security. Under Windows Update, click View installed updates and select from the list of updates. |
File Information | See Microsoft Knowledge Base Article 950762 |
Registry Key Verification | Note A registry key does not exist to validate the presence of this update. |
Supported Security Update Installation Switches
Switch | Description |
---|---|
/?, /h, /help | Displays help on supported switches. |
/quiet | Suppresses the display of status or error messages. |
/norestart | When combined with /quiet, the system will not be restarted after installation even if a restart is required to complete installation. |
Note For more information about the wusa.exe installer, see Microsoft Knowledge Base Article 934307.
Verifying That the Update Has Been Applied
Microsoft Baseline Security Analyzer
To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information.
File Version Verification
Because there are several editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps.
- Click Start and then enter an update file name in Start Search.
- When the file appears under Programs, right-click on the file name and click Properties.
- Under the General tab, compare the file size with the file information tables provided in the bulletin KB article.
- You may also click on the Details tab and compare information, such as file version and date modified, with the file information tables provided in the bulletin KB article.
- Finally, you may also click on the Previous Versions tab and compare file information for the previous version of the file with the file information for the new, or updated, version of the file.
Windows Server 2008 (all editions)
Reference Table
The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section.
Inclusion in Future Service Packs | The update for this issue will be included in a future service pack or update rollup |
Deployment | |
Installing without user intervention | For all supported 32-bit editions of Windows Server 2008: Windows6.0-KB950762-x86 /quiet For all supported x64-based editions of Windows Server 2008: Windows6.0-KB950762-x64 /quiet For all supported Itanium-based editions of Windows Server 2008: Windows6.0-KB950762-ia64 /quiet |
Installing without restarting | For all supported 32-bit editions of Windows Server 2008: Windows6.0-KB950762-x86 /quiet /norestart For all supported x64-based editions of Windows Server 2008: Windows6.0-KB950762-x64 /quiet /norestart For all supported Itanium-based editions of Windows Server 2008: Windows6.0-KB950762-ia64 /quiet /norestart |
Further information | See the subsection, Detection and Deployment Tools and Guidance |
Restart Requirement | |
Restart required? | Yes, you must restart your system after you apply this security update. |
HotPatching | Not applicable. |
Removal Information | WUSA.exe does not support uninstall of updates. To uninstall an update installed by WUSA, click Control Panel, and then click Security. Under Windows Update, click View installed updates and select from the list of updates. |
File Information | See Microsoft Knowledge Base Article 950762 |
Registry Key Verification | Note A registry key does not exist to validate the presence of this update. |
Supported Security Update Installation Switches
Switch | Description |
---|---|
/?, /h, /help | Displays help on supported switches. |
/quiet | Suppresses the display of status or error messages. |
/norestart | When combined with /quiet, the system will not be restarted after installation even if a restart is required to complete installation. |
Note For more information about the wusa.exe installer, see Microsoft Knowledge Base Article 934307.
Verifying That the Update Has Been Applied
Microsoft Baseline Security Analyzer
To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information.
File Version Verification
Because there are several editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps.
- Click Start and then enter an update file name in Start Search.
- When the file appears under Programs, right-click on the file name and click Properties.
- Under the General tab, compare the file size with the file information tables provided in the bulletin KB article.
- You may also click on the Details tab and compare information, such as file version and date modified, with the file information tables provided in the bulletin KB article.
- Finally, you may also click on the Previous Versions tab and compare file information for the previous version of the file with the file information for the new, or updated, version of the file.
Other Information
Support
- Customers in the U.S. and Canada can receive technical support from Microsoft Product Support Services at 1-866-PCSAFETY. There is no charge for support calls that are associated with security updates.
- International customers can receive support from their local Microsoft subsidiaries. There is no charge for support that is associated with security updates. For more information about how to contact Microsoft for support issues, visit the International Support Web site.
Disclaimer
The information provided in the Microsoft Knowledge Base is provided "as is" without warranty of any kind. Microsoft disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Microsoft Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Microsoft Corporation or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply.
Revisions
- V1.0 (June 10, 2008): Bulletin published.
- V1.1 (February 17, 2010): Added a link to Microsoft Knowledge Base Article 950762 under Known Issues in the Executive Summary.
Built at 2014-04-18T13:49:36Z-07:00