Share via

  • Article

Security Bulletin

Microsoft Security Bulletin MS07-067 - Important

Vulnerability in Macrovision Driver Could Allow Local Elevation of Privilege (944653)

Published: December 11, 2007 | Updated: December 11, 2007

Version: 1.1

General Information

Executive Summary

This important security update resolves one publicly disclosed vulnerability. A local elevation of privilege vulnerability exists in the way that the Macrovision driver incorrectly handles configuration parameters. A local attacker who successfully exploited this vulnerability could take control of the system. An attacker could then install programs; view, change, or delete data; or create new accounts with full administrative rights.

This is an important security update for supported editions of Windows XP and Windows Server 2003. For more information, see the subsection, Affected and Non-Affected Software, in this section.

For more information about the vulnerability, see the Frequently Asked Questions (FAQ) subsection for the specific vulnerability entry under the next section, Vulnerability Information.

This security update also addresses the vulnerability first described in Microsoft Security Advisory 944653.

Recommendation.  Microsoft recommends that customers apply the update at the earliest opportunity.

Known Issues. None

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

Operating System Maximum Security Impact Aggregate Severity Rating Bulletins Replaced by this Update
Windows XP Service Pack 2 Local Elevation of Privilege Important None
Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2 Local Elevation of Privilege Important None
Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2 Local Elevation of Privilege Important None
Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2 Local Elevation of Privilege Important None

Non-Affected Software

Operating System
Microsoft Windows 2000 Service Pack 4
Windows Server 2003 for Itanium-based Systems
Windows Vista
Windows Vista x64 Edition

I’ve installed the security update offered by Macrovision. Should I install the update offered by Microsoft?
No action is required on systems where either security update has been successfully installed. Version 4.3.86.0 of secdrv.sys driver offered by Macrovision and Microsoft for all affected versions of Windows address the same vulnerability. Only build times differ between the Macrovision and Microsoft updates for the secdrv.sys driver.

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 has 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 Macrovision Driver Vulnerability - CVE-2007-5587 Aggregate Severity Rating
Windows XP Service Pack 2 **Important **\ Elevation of Privilege **Important **
Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2 **Important **\ Elevation of Privilege **Important **
Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2 **Important **\ Elevation of Privilege **Important **
Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2 **Important **\ Elevation of Privilege **Important **

Macrovision Driver Vulnerability - CVE-2007-5587

A local elevation of privilege vulnerability exists in the way that the Macrovision driver incorrectly handles configuration parameters. An attacker who successfully exploited this vulnerability could execute arbitrary code in the context of local system. An attacker could then install programs; view, change, or delete data; or create new accounts with full administrative rights.

To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2007-5587.

Mitigating Factors for Macrovision Driver Vulnerability - CVE-2007-5587

Mitigation refers to a setting, common configuration, or general best-practice, existing in a default state, that could reduce the severity of exploitation of a vulnerability. The following mitigating factors may be helpful in your situation:

  • An attacker must convince a user to run an executable or must have valid logon credentials to exploit this vulnerability. This is a local elevation of privilege vulnerability. The exploit for this vulnerability can not be done remotely.
  • Microsoft Windows 2000 Service Pack 4 is not affected.
  • Windows Vista is not affected.

Workarounds for Macrovision Driver Vulnerability - CVE-2007-5587

Workaround refers to a setting or configuration change that does not correct the underlying vulnerability but would help block known attack vectors before you apply the update. Microsoft has tested the following workarounds and states in the discussion whether a workaround reduces functionality:

  • Disable the secdrv.sys driver

    Disabling the secdrv.sys driver in the system registry key helps protect affected systems from attempts to exploit this vulnerability.

    Note: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk. For information about how to edit the registry, view the "Changing Keys And Values" Help topic in Registry Editor (Regedit.exe) or view the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe.

    Interactive

    1. Click Start, click Run, type regedit and then click OK.
    2. Expand HKEY_LOCAL_MACHINE.
    3. Expand SYSTEM, expand CurrentControlSet, and then expand Services.
    4. Click Secdrv.
    5. Click the File menu and select Export.
    6. To backup the registry before your edit it, left click on File menu, select Export... In the Export Registry File dialog box, type Secdrv_configuration_backup.reg and select Save.
    7. Double-click the value named Start, and change the Value data: field to 4.
    8. Click OK.
    9. Click Start, click All Programs, click Accessories, and click Command Prompt.
    10. Run the following command at a command prompt:

    Sc stop secdrv

    Managed Deployment Script

    1. Make a backup copy of the registry keys from a managed deployment script using the following command:

    regedit /e Secdrv_configuration_backup.reg HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Secdrv

    1. Save the following to a file with a .REG extension (e.g. Disable_Secdrv.reg):
    Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Secdrv]
"Start"=dword:00000004
    1. Run the registry script created in Step 2 on the target machine with the following command:

    Regedit /s Disable_Secdrv.reg

    1. Click Start, click All Programs, click Accessories, and click Command Prompt.

    2. Run the following command at a command prompt:

    sc stop secdrv

    Impact of workaround. Programs that require this driver will not run.

FAQ for Macrovision Driver Vulnerability - CVE-2007-5587

What is the scope of the vulnerability? 
This is a local elevation of privilege vulnerability. An attacker who successfully exploited this vulnerability could execute arbitrary code in the context of local system. An attacker could then install programs; view, change, or delete data; or create new accounts with full administrative rights.

What causes the vulnerability? 
The Macrovision driver incorrectly handles configuration parameters.

What is secdrv.sys? 
The driver, secdrv.sys, is used by games which use Macrovision SafeDisc. The driver validates the authenticity of games that are protected with SafeDisc and prohibits unauthorized copies of such games to play on Windows. The secdrv.sys is included with Microsoft Windows XP, Windows Server 2003, and Windows Vista to increase compatibility of the games on Windows. Without the driver, games with SafeDisc protection would be unable to play on Windows. SafeDisc remains inactive until invoked by a game for authorization to play on Windows.

What might an attacker use the vulnerability to do? 
A local attacker could successfully exploit this vulnerability to gain full control of an affected system.

How could an attacker exploit the vulnerability? 
To exploit this vulnerability, the attacker must have valid credentials to log on to the system, which would allow the attacker to run a specially crafted application that could exploit the vulnerability and gain full control of the affected system.

Does the update offered by Macrovision address the same vulnerability? 
Version 4.3.86.0 of secdrv.sys driver is offered by Macrovision and Microsoft for all affected versions of Windows. Only build times differ between the Macrovision and Microsoft updates for the secdrv.sys driver.

What systems are primarily at risk from the vulnerability? 
Workstations and terminal servers are primarily at risk. Servers could be at more risk if administrators allow users to log on to servers and to run programs. However, best practices strongly discourage allowing this.

When this security bulletin was issued, had this vulnerability been publicly disclosed?
Yes. This vulnerability had been publicly disclosed when this security bulletin was originally issued. It has been assigned the Common Vulnerability and Exposure number CVE-2007-5587. This vulnerability was first described in Microsoft Security Advisory 944653.

When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited?
Yes. When the security bulletin was released, Microsoft had received information that this vulnerability was being exploited.

Update Information

Detection and Deployment Tools and Guidance

Manage the software and security updates you need to deploy to the servers, desktop, and mobile computers in your organization. For more information see the TechNet Update Management Center. The Microsoft TechNet Security Web site provides additional information about security in Microsoft products.

Security updates are available from Microsoft Update, Windows Update, and Office Update. Security updates are also available from the Microsoft Download Center. You can find them most easily by doing a keyword search for "security update."

Finally, security updates can be downloaded from the Microsoft Update Catalog. The Microsoft Update Catalog provides a searchable catalog of content made available through Windows Update and Microsoft Update, including security updates, drivers and service packs. By searching using the security bulletin number (such as, “MS07-036”), you can add all of the applicable updates to your basket (including different languages for an update), and download to the folder of your choosing. For more information about the Microsoft Update Catalog, see the Microsoft Update Catalog FAQ.

Detection and Deployment Guidance

Microsoft has provided detection and deployment guidance for this month’s security updates. This guidance will also help IT professionals understand how they can use various tools to help deploy the security update, such as Windows Update, Microsoft Update, Office Update, the Microsoft Baseline Security Analyzer (MBSA), the Office Detection Tool, Microsoft Systems Management Server (SMS), and the Extended Security Update Inventory Tool. For more information, see Microsoft Knowledge Base Article 910723.

Microsoft Baseline Security Analyzer

Microsoft Baseline Security Analyzer (MBSA) allows administrators to scan local and remote systems for missing security updates as well as common security misconfigurations. For more information about MBSA, visit Microsoft Baseline Security Analyzer.

The following table provides the MBSA detection summary for this security update.

Software MBSA 2.0.1
Windows XP Service Pack 2 Yes
Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2 Yes
Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2 Yes
Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2 Yes

For more information about MBSA 2.0.1, see MBSA 2.0 Frequently Asked Questions.

Systems Management Server

The following table provides the SMS detection and deployment summary for this security update.

Software SMS 2.0 SMS 2003
Windows XP Service Pack 2 Yes Yes
Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2 No Yes
Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2 Yes Yes
Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2 No Yes

For SMS 2.0, the SMS SUS Feature Pack, which includes the Security Update Inventory Tool (SUIT), can be used by SMS to detect security updates. See also Downloads for Systems Management Server 2.0.

For SMS 2003, the SMS 2003 Inventory Tool for Microsoft Updates (ITMU) can be used by SMS to detect security updates that are offered by Microsoft Update and that are supported by Windows Server Update Services. For more information about the SMS 2003 ITMU, see SMS 2003 Inventory Tool for Microsoft Updates. SMS 2003 can also use the Microsoft Office Inventory Tool to detect required updates for Microsoft Office applications. For more information about the Office Inventory Tool and other scanning tools, see SMS 2003 Software Update Scanning Tools. See also Downloads for Systems Management Server 2003.

For more information about SMS, visit the SMS Web site.

For more detailed information, see Microsoft Knowledge Base Article 910723: Summary list of monthly detection and deployment guidance articles.

Security Update Information

Affected Software

For information about the specific security update for your affected software, click the appropriate link:

Windows XP (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 Windows XP Service Pack 2:\ Windowsxp-kb944653-x86-enu.exe /quiet
Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2:WindowsServer2003.WindowsXP-kb944653-x64-enu.exe /quiet
Installing without restarting Windows XP Service Pack 2:\ Windowsxp-kb944653-x86-enu.exe /norestart
Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2:Windowsserver2003.WindowsXP-kb944653-x64-enu.exe /norestart
Update log file KB944653.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%$NTUninstallKB944653$\Spuninst folder
File Information See the next subsection, File Information, for the full file manifest.
Registry Key Verification For all supported 32-bit editions of Windows XP:\ HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP\SP3\KB944653\Filelist
For all supported x64-based editions of Windows XP:\ HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP Version 2003\SP3\KB944653\Filelist

File Information

The English version of this security update has the file attributes that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.

For all supported 32-bit editions of Windows XP:

File Name Version Date Time Size Folder
secdrv.sys 4.3.86.0 12-Nov-2007 20:55 20,480 SP2GDR
secdrv.sys 4.3.86.0 12-Nov-2007 20:55 20,480 SP2QFE

For all supported x64-based editions of Windows XP Professional:

File Name Version Date Time Size CPU Folder
secdrv.sys 4.3.86.0 14-Nov-2007 07:06 23,040 X64 SP2GDR
secdrv.sys 4.3.86.0 14-Nov-2007 06:59 23,040 X64 SP2QFE

Note For a complete list of supported editions, see the Support Lifecycle Index. For a complete list of service packs, see Lifecycle Supported Service Packs. For more information on the support lifecycle policy, see Microsoft Support Lifecycle.

Deployment Information

Installing the Update

When you install this security update, the installer checks to see if one or more of the files that are being updated on your system have previously been updated by a Microsoft hotfix.

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. 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 Display 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.

Note You can combine these switches into one command. For backward compatibility, the security update also supports the setup switches that the earlier version of the Setup program uses. For more information about the supported installation switches, see Microsoft Knowledge Base Article 262841. For more information about the Update.exe installer, visit the Microsoft TechNet Web site.

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 versions of Microsoft Windows, the following steps may be different on your computer. If they are, see your product documentation to complete these steps.

    1. Click Start, and then click Search.
    2. In the Search Results pane, click All files and folders under Search Companion.
    3. In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
    4. In the list of files, right-click a file name from the appropriate file information table, and then click Properties.
      Note Depending on the version of the operating system or programs installed, some of the files that are listed in the file information table may not be installed.
    5. On the Version tab, determine the version of the file that is installed on your computer 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 32-bit editions of Windows Server 2003:WindowsServer2003-KB944653-x86-ENU.exe /quiet
For x64-based editions of Windows Server 2003:WindowsServer2003.WindowsXP-KB944653-x64-ENU.exe /quiet
Installing without restarting For 32-bit editions of Windows Server 2003:WindowsServer2003-KB944653-x86-ENU.exe /norestart
For x64-based editions of Windows Server 2003:WindowsServer2003.WindowsXP-KB944653-x64-ENU.exe /norestart
Update log file KB944653.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%$NTUninstallKB944653$\Spuninst folder
File Information See the next subsection, File Information, for the full file manifest.
Registry Key Verification For all supported 32-bit and x64-based editions of Windows Server 2003:\ HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB944653\Filelist

File Information

The English version of this security update has the file attributes that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.

For all supported 32-bit editions of Windows Server 2003:

File Name Version Date Time Size Folder
secdrv.sys 4.3.86.0 12-Nov-2007 20:02 20,480 SP2GDR
secdrv.sys 4.3.86.0 12-Nov-2007 20:02 20,480 SP2QFE

Note For a complete list of supported versions, see the Support Lifecycle Index. For a complete list of service packs, see Lifecycle Supported Service Packs. For more information on the support lifecycle policy, see Microsoft Support Lifecycle.

For all supported x64-based editions of Windows Server 2003:

File Name Version Date Time Size CPU Folder
secdrv.sys 4.3.86.0 14-Nov-2007 07:06 23,040 X64 SP2GDR
secdrv.sys 4.3.86.0 14-Nov-2007 06:59 23,040 X64 SP2QFE

Note For a complete list of supported versions, see the Support Lifecycle Index. For a complete list of service packs, see Lifecycle Supported Service Packs. For more information on the support lifecycle policy, see Microsoft Support Lifecycle.

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 Windows hotfix. If you have previously installed a hotfix to update one of these files, the installer will apply the LDR version of this update. Otherwise, the installer will apply the GDR version of the update. The LDR version of a file has a higher version number than the GDR version of a file. For more information about this behavior, see Microsoft Knowledge Base Article 824994.For more information about the installer, see Microsoft Knowledge Base Article 934307.

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
/?, /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 You can combine these switches into one command. For backward compatibility, the security update also supports the setup switches that the earlier version of the Setup program uses. For more information about the supported installation switches, see Microsoft Knowledge Base Article 262841. For more information about the Update.exe 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.

Removing the Update

To remove this update, use the Add or Remove Programs tool in Control Panel.

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 versions of Microsoft Windows, the following steps may be different on your computer. If they are, see your product documentation to complete these steps.

    1. Click Start, and then click Search.
    2. In the Search Results pane, click All files and folders under Search Companion.
    3. In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
    4. In the list of files, right-click a file name from the appropriate file information table, and then click Properties.
      Note Depending on the version of the operating system or programs installed, some of the files that are listed in the file information table may not be installed.
    5. On the General tab, determine the modified date of the file that is installed on your computer by comparing it to the modified date that is documented in the appropriate file information table. The files in this package do not have version numbers.
      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 recommended method of verifying that the update has been applied. However the files updated for this security patch do not contain file version information so using file attributes information used to verify the update is a detection mechanisms. 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

    Use the registry key provided in the Reference Table above.

Other Information

Acknowledgments

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 (December 11, 2007): Bulletin published.
  • V1.1 (December 11, 2007): Bulletin updated to clarify the impact of the vulnerability.

Built at 2014-04-18T13:49:36Z-07:00