Export (0) Print
Expand All
This topic has not yet been rated - Rate this topic

Microsoft Security Bulletin MS07-050 - Critical

Vulnerability in Vector Markup Language Could Allow Remote Code Execution (938127)

Published: August 14, 2007 | Updated: August 26, 2008

Version: 2.0

General Information

Executive Summary

This security update resolves a privately reported vulnerability in the Vector Markup Language (VML) implementation in Windows. The vulnerability could allow remote code execution if a user viewed a specially crafted Web page using Internet Explorer. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.

The security update is rated critical for supported releases of Internet Explorer 5.01, Internet Explorer 6, and Internet Explorer 7. For more information, see the subsection, Affected and Non-Affected Software, in this section.

The security update addresses the vulnerability by strengthening the validation of requests to render VML within Internet Explorer. For more information about the vulnerability, see the Frequently Asked Questions (FAQ) subsection under the next section, Vulnerability Information.

Recommendation. Microsoft recommends that customers apply the update immediately.

Known Issues. Microsoft Knowledge Base Article 938127 documents the currently known issues that customers may experience when they install this security update. The article also documents recommended solutions for these issues.

Affected and Non-Affected Software

The software listed here has 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 SystemComponentMaximum Security ImpactAggregate Severity RatingBulletins Replaced by This Update
Internet Explorer 5.01 and Internet Explorer 6 Service Pack 1
Microsoft Windows 2000 Service Pack 4Microsoft Internet Explorer 5.01 Service Pack 4Remote Code ExecutionCriticalMS07-004
Microsoft Windows 2000 Service Pack 4Microsoft Internet Explorer 6 Service Pack 1Remote Code ExecutionCriticalMS07-004
Internet Explorer 6
Windows XP Service Pack 2Microsoft Internet Explorer 6Remote Code ExecutionCriticalMS07-004
Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2Microsoft Internet Explorer 6Remote Code ExecutionCriticalMS07-004
Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2Microsoft Internet Explorer 6Remote Code ExecutionCriticalMS07-004
Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2Microsoft Internet Explorer 6Remote Code ExecutionCriticalMS07-004
Windows Server 2003 with SP1 for Itanium-based Systems and Windows Server 2003 with SP2 for Itanium-based SystemsMicrosoft Internet Explorer 6Remote Code ExecutionCriticalMS07-004
Internet Explorer 7
Windows XP Service Pack 2Windows Internet Explorer 7Remote Code ExecutionCriticalMS07-004
Windows XP Service Pack 3Windows Internet Explorer 7Remote Code ExecutionCriticalNone
Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2Windows Internet Explorer 7Remote Code ExecutionCriticalMS07-004
Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2Windows Internet Explorer 7Remote Code ExecutionCriticalMS07-004
Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2Windows Internet Explorer 7Remote Code ExecutionCriticalMS07-004
Windows Server 2003 with SP1 for Itanium-based Systems and Windows Server 2003 with SP2 for Itanium-based SystemsWindows Internet Explorer 7Remote Code ExecutionCriticalMS07-004
Windows VistaWindows Internet Explorer 7Remote Code ExecutionCriticalNone
Windows Vista x64 EditionWindows Internet Explorer 7Remote Code ExecutionCriticalNone

Why was this Bulletin revised on August 26, 2008? 
This Bulletin was revised adding Internet Explorer 7 on Windows XP Service Pack 3 as an affected product and will now be offered for update.

What are the known issues that customers may experience when they install this security update? 
Microsoft Knowledge Base Article 938127 documents the currently known issues that customers may experience when they install this security update. The article also documents recommended solutions for these issues.

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 the following Microsoft Support Lifecycle. For more information about the extended security update support period for these software releases, visit the Microsoft Product Support Services Web site.

Customers who require custom support for older software 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 the Microsoft Worldwide Information Web site, 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.

If I install this security update before upgrading to Internet Explorer 7, will I still need to apply this update after upgrading to Internet Explorer 7? 
Yes. Customers who have installed the current VML security update on systems with Internet Explorer 6 and later install Internet Explorer 7, will be offered this update for Internet Explorer 7. The vgx.dll version installed with Windows Internet Explorer 7 is a major-version higher than vgx.dll included in Windows 2000, Windows XP, or Windows Server 2003. When Internet Explorer 7 is installed, it will replace vgx.dll updated by Internet Explorer 6 provided by in this security update.

Vulnerability Information

Vulnerability Severity Rating and Maximum Security Impact by Affected Software
Affected SoftwareVML Buffer Overrun Vulnerability - CVE-2007-1749
Internet Explorer 5.01 and Internet Explorer 6 Service Pack 1
Internet Explorer 5.01 Service Pack 4 on Microsoft Windows 2000 Service Pack 4Critical

Remote Code Execution

Internet Explorer 6 Service Pack 1 when installed on Microsoft Windows 2000 Service Pack 4Critical

Remote Code Execution

Internet Explorer 6
Internet Explorer 6 for Windows XP Service Pack 2Critical

Remote Code Execution

Internet Explorer 6 for Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2Critical

Remote Code Execution

Internet Explorer 6 for Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2Critical

Remote Code Execution

Internet Explorer 6 for Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2Critical

Remote Code Execution

Internet Explorer 6 for Windows Server 2003 with SP1 for Itanium-based Systems and Windows Server 2003 with SP2 for Itanium-based SystemsCritical

Remote Code Execution

Internet Explorer 7
Internet Explorer 7 for Windows XP Service Pack 2 and Windows XP Service Pack 3Critical

Remote Code Execution

Internet Explorer 7 for Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2.Critical

Remote Code Execution

Internet Explorer 7 for Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2Critical

Remote Code Execution

Internet Explorer 7 for Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2Critical

Remote Code Execution

Internet Explorer 7 for Windows Server 2003 with SP1 for Itanium-based Systems and Windows Server 2003 with SP2 for Itanium-based SystemsCritical

Remote Code Execution

Internet Explorer 7 in Windows VistaCritical

Remote Code Execution

Internet Explorer 7 in Windows Vista x64 EditionCritical

Remote Code Execution

A remote code execution vulnerability exists in the Vector Markup Language (VML) implementation in Microsoft Windows. An attacker could exploit the vulnerability by constructing a specially crafted Web page or HTML e-mail. When a user views the Web page or the message, the vulnerability could allow remote code execution.

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

Mitigating Factors for VML Buffer Overrun Vulnerability - CVE-2007-1749

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:

  • In a Web-based attack scenario, an attacker could host a Web site that contains a Web page that is used to exploit this vulnerability. In addition, compromised Web sites and Web sites that accept or host user-provided content or advertisements could contain specially crafted content that could exploit this vulnerability. In all cases, however, an attacker would have no way to force users to visit these Web sites. Instead, an attacker would have to persuade users to visit the Web site, typically by getting them to click a link in an e-mail message or Instant Messenger message that takes users to the attacker's Web site.
  • An attacker who successfully exploited this vulnerability could gain the same user rights as the local user. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.
  • In an e-mail based attack of this exploit, customers who read e-mail in plain text are at less risk from this vulnerability. Instead, users would have to either click on a link that would take them to a malicious Web site or open an attachment to be at risk from this vulnerability.

Workarounds for VML Buffer Overrun Vulnerability - CVE-2007-1749

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:

  • Unregister VGX.DLL
    1. Click Start, click Run, type "%SystemRoot%\System32\regsvr32.exe" -u "%CommonProgramFiles%\Microsoft Shared\VGX\vgx.dll", and then click OK.
    2. A dialog box appears to confirm that the un-registration process has succeeded. Click OK to close the dialog box.

    Impact of Workaround: Applications that render VML will no longer do so once vgx.dll has been unregistered.

    This security update does not automatically re-register vgx.dll so any applications that render VML will no longer do so until vgx.dll has been re-registered. To re-register vgx.dll follow, these steps:

    1. Click Start, click Run, type "%SystemRoot%\System32\regsvr32.exe" "%CommonProgramFiles%\Microsoft Shared\VGX\vgx.dll", and then click OK.
    2. A dialog box appears to confirm that the registration process has succeeded. Click OK to close the dialog box.
  • Set Internet and Local intranet security zone settings to “High” to prompt before running ActiveX Controls and Active Scripting in these zones

    You can help protect against this vulnerability by changing your settings for the Internet security zone to prompt before running ActiveX controls. You can do this by setting your browser security to High.

    To raise the browsing security level in Microsoft Internet Explorer, follow these steps:

    1. On the Internet Explorer Tools menu, click Internet Options.
    2. In the Internet Options dialog box, click the Security tab, and then click the Internet icon.
    3. Under Security level for this zone, move the slider to High. This sets the security level for all Web sites you visit to High.

    Note If no slider is visible, click Default Level, and then move the slider to High.

    Note Setting the level to High may cause some Web sites to work incorrectly. If you have difficulty using a Web site after you change this setting, and you are sure the site is safe to use, you can add that site to your list of trusted sites. This will allow the site to work correctly even with the security setting set to High.

    Impact of workaround: There are side effects to prompting before running ActiveX Controls and Active Scripting. Many Web sites that are on the Internet or on an intranet use ActiveX or Active Scripting to provide additional functionality. For example, an online e-commerce site or banking site may use ActiveX Controls to provide menus, ordering forms, or even account statements. Prompting before running ActiveX Controls or Active Scripting is a global setting that affects all Internet and intranet sites. You will be prompted frequently when you enable this workaround. For each prompt, if you feel you trust the site that you are visiting, click Yes to run ActiveX Controls or Active Scripting. If you do not want to be prompted for all these sites, use the steps outlined in "Add sites that you trust to the Internet Explorer Trusted sites zone”.

    Add sites that you trust to the Internet Explorer Trusted sites zone

    After you set Internet Explorer to require a prompt before it runs ActiveX controls and Active Scripting in the Internet zone and in the Local intranet zone, you can add sites that you trust to the Internet Explorer Trusted sites zone. This will allow you to continue to use trusted Web sites exactly as you do today, while helping to protect you from this attack on untrusted sites. We recommend that you add only sites that you trust to the Trusted sites zone.

    To do this, follow these steps:

    1. In Internet Explorer, click Tools, click Internet Options, and then click the Security tab.
    2. In the Select a Web content zone to specify its current security settings box, click Trusted Sites, and then click Sites.
    3. If you want to add sites that do not require an encrypted channel, click to clear the Require server verification (https:) for all sites in this zone check box.
    4. In the Add this Web site to the zone box, type the URL of a site that you trust, and then click Add.
    5. Repeat these steps for each site that you want to add to the zone.
    6. Click OK two times to accept the changes and return to Internet Explorer.

    Note Add any sites that you trust not to take malicious action on your computer. Two in particular that you may want to add are *.windowsupdate.microsoft.com and *.update.microsoft.com. These are the sites that will host the update, and it requires an ActiveX Control to install the update.

FAQ for VML Buffer Overrun Vulnerability - CVE-2007-1749

What is the scope of the vulnerability? 
This is a remote code execution vulnerability. An attacker who successfully exploited this vulnerability could take complete control of an affected system remotely. An attacker could then install programs or view, change, or delete data.

What causes the vulnerability? 
In the VML implementation in Microsoft Windows, routines in the vector graphics link library, vgx.dll, do not perform sufficient validation of requests to render VML within Internet Explorer.

What might an attacker use the vulnerability to do? 
An attacker who successfully exploited this vulnerability could gain the same user rights as the local user. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.

How could an attacker exploit the vulnerability? 
An attacker could host a specially crafted Web site that is designed to exploit this vulnerability through Internet Explorer and then persuade a user to view the Web site. This can also include compromised Web sites and Web sites that accept or host user-provided content or advertisements. These Web sites could contain specially crafted content that could exploit this vulnerability. In all cases, however, an attacker would have no way to force users to visit these Web sites. Instead, an attacker would have to persuade users to visit the Web site, typically by getting them to click a link in an e-mail message or in an Instant Messenger request that takes users to the attacker's Web site. It could also be possible to display specially crafted Web content by using banner advertisements or by using other methods to deliver Web content to affected systems.

What systems are primarily at risk from the vulnerability? 
This vulnerability requires that a user is logged on and reading e-mail messages or is visiting Web sites for any malicious action to occur. Therefore, any systems where e-mail messages are read or where Internet Explorer is used frequently, such as workstations or terminal servers, are at the most risk from this vulnerability. Systems that are not typically used to visit Web sites, such as most server systems, are at a reduced risk.

What does the update do? 
The update changes the way that routines in the vector graphics link library, vgx.dll, validate requests to render VML within Internet Explorer.

When this security bulletin was issued, had this vulnerability been publicly disclosed? 
No. Microsoft received information about this vulnerability through responsible disclosure.

When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited? 
No. Microsoft had not received any information to indicate that this vulnerability had been publicly used to attack customers and had not seen any examples of proof of concept code published when this security bulletin was originally issued.

Update Information

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 at the Microsoft Download Center. You can find them most easily by doing a keyword search for "security_patch." Finally, security updates can be downloaded from the Windows Update Catalog. For more information about the Windows Update Catalog, see Microsoft Knowledge Base Article 323166.

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), the Extended Security Update Inventory Tool, and the Enterprise Update Scan Tool (EST). 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 Web site. The following table provides the MBSA detection summary for this security update.

SoftwareMBSA 1.2.1Enterprise Scanning Tool (EST)MBSA 2.0.1
Windows 2000 Service Pack 4NoYesYes
Windows XP Service Pack 2 and Windows XP Service Pack 3NoYesYes
Windows XP Professional x64 Edition and Microsoft Windows XP Professional x64 Edition Service Pack 2NoYesYes
Windows Server 2003 Service Pack 1 and Microsoft Windows Server 2003 Service Pack 2NoYesYes
Windows Server 2003 x64 Edition and Microsoft Windows Server 2003 x64 Edition Service Pack 2NoYesYes
Windows Server 2003 with SP1 for Itanium-based Systems and Microsoft Windows Server 2003 with SP2 for Itanium-based SystemsNoYesYes
Windows VistaNoNoSee Note for Windows Vista below
Windows Vista x64 EditionNoNoSee Note for Windows Vista below

Note for Windows Vista Microsoft does not support installing MBSA 2.0.1 on computers that run Windows Vista, but you may install MBSA 2.0.1 on a supported operating system and then scan the Windows Vista-based computer remotely. For additional information about MBSA support for Windows Vista, visit the MBSA Web site. See also Microsoft Knowledge Base Article 931943: Microsoft Baseline Security Analyzer (MBSA) support for Windows Vista.

For more information about MBSA, visit the MBSA Web site. For more information about the software that Microsoft Update and MBSA 2.0 currently do not detect, see Microsoft Knowledge Base Article 895660.

What is the Enterprise Update Scan Tool (EST)?

As part of an ongoing commitment to provide detection tools for bulletin-class security updates, Microsoft delivers a stand-alone detection tool whenever the Microsoft Baseline Security Analyzer (MBSA) and the Office Detection Tool (ODT) cannot detect whether the update is required for an MSRC release cycle. This stand-alone tool is called the Enterprise Update Scan Tool (EST) and is designed for enterprise administrators. When a version of the Enterprise Update Scan Tool is created for a specific bulletin, customers can run the tool from a command line interface (CLI) and view the results of the XML output file. To help customers better utilize the tool, detailed documentation will be provided with the tool. There is also a version of the tool that offers an integrated experience for SMS administrators.

Can I use a version of the Enterprise Update Scan Tool (EST) to determine whether this update is required?

Yes. Microsoft has created a version of the EST that will determine if you have to apply this update. For download links and more information about the version of the EST that is being released this month, see the following Microsoft Web site.

Windows Server Update Services

By using Windows Server Update Services (WSUS), administrators can deploy the latest critical updates and security updates for Windows 2000 operating systems and later, Office XP and later, Exchange Server 2003, and SQL Server 2000 to Windows 2000 and later operating systems. For more information about how to deploy this security update using Windows Server Update Services, visit the Windows Server Update Services Web site.

Systems Management Server

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

SoftwareSMS 2.0SMS 2003
Microsoft Windows 2000 Service Pack 4YesYes
Windows XP Service Pack 2 and Windows XP Service Pack 3YesYes
Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2NoYes
Windows Server 2003 Service Pack 1 and Microsoft Windows Server 2003 Service Pack 2YesYes
Windows Server 2003 x64 Edition and Microsoft Windows Server 2003 x64 Edition Service Pack 2NoYes
Windows Server 2003 with SP1 for Itanium-based Systems and Windows Server 2003 with SP2 for Itanium-based SystemsNoYes
Windows VistaNoSee Note for Windows Vista below
Windows Vista x64 EditionNoSee Note for Windows Vista below

SMS 2.0 and SMS 2003 Software Update Services (SUS) Feature Pack can use MBSA 1.2.1 for detection and therefore have the same limitation that is listed earlier in this bulletin related to programs that MBSA 1.2.1 does not detect.

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. SMS SUIT uses the MBSA 1.2.1 engine for detection. For more information about SUIT, visit the following Microsoft Web site. For more information about the limitations of SUIT, see Microsoft Knowledge Base Article 306460. The SMS SUS Feature Pack also includes the Microsoft Office Inventory Tool to detect required updates for Microsoft Office applications.

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, visit the following Microsoft Web site. SMS 2003 can also use the Microsoft Office Inventory Tool to detect required updates for Microsoft Office applications.

Note for Windows Vista  Microsoft Systems Management Server 2003 with Service Pack 3 includes support for Windows Vista manageability.

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

Affected Software

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

Windows 2000 (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 PacksThe update for this issue may be included in a future update rollup
Deployment
Installing without user interventionInternet Explorer 5.01 Service Pack 4:
IE5.01sp4-KB938127-Windows2000sp4-x86-enu /quiet
Internet Explorer 6 Service Pack 1:
IE6.0sp1-KB938127-Windows2000-x86-enu /quiet
Installing without restartingInternet Explorer 5.01 Service Pack 4:
IE5.01sp4-KB938127-Windows2000sp4-x86-enu /norestart
Internet Explorer 6 Service Pack 1:
IE6.0sp1-KB938127-Windows2000-x86-enu /norestart
Update log fileInternet Explorer 5.01 Service Pack 4:
KB938127-IE501SP4-20070626.120000.log
Internet Explorer 6 Service Pack 1:
KB938127-IE6SP1-20070626.120000.log
Further informationSee the subsection, Detection and Deployment Tools and Guidance
Restart Requirement
Restart requiredIn some cases, this update does not require a restart. If the required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart
HotpatchingNot applicable
Removal InformationInternet Explorer 5.01 Service Pack 4:
Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallKB938127-IE501SP4- 20070626.120000$\Spuninst folder
Internet Explorer 6 Service Pack 1:
Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallKB938127-IE6SP1- 20070626.120000$\Spuninst folder
File InformationSee the heading, File Information, below for the full file manifest
Registry Key VerificationFor Internet Explorer 5.01 Service Pack 4 on all supported editions of Microsoft Windows 2000 Service Pack 4:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Internet Explorer 5.01\SP4\KB938127-IE501SP4-20070626.120000\Filelist
For Internet Explorer 6 Service Pack 1 when installed on all supported editions of Microsoft Windows 2000 Service Pack 4:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Internet Explorer 6\SP1\KB938127-IE6SP1-20070626.120000\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 Internet Explorer 5.01 Service Pack 4 on all supported editions of Windows 2000:

File NameVersionDateTimeSize
iecustom.dll6.0.2800.158513-Oct-200623:5043,984
vgx.dll5.0.3854.250026-Jun-200717:001,757,256
iecustom.dll6.0.2800.158513-Oct-200623:5043,984

Note For a complete list of supported versions and 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.

For Internet Explorer 6 Service Pack 1 when installed on all supported editions of Windows 2000:

File NameVersionDateTimeSize
iecustom.dll6.0.2800.158513-Oct-200623:5043,984
vgx.dll6.0.2800.159926-Jun-200721:522,286,080
iecustom.dll6.0.2800.158513-Oct-200623:5043,984

Note For a complete list of supported versions and 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 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.

Supported Security Update Installation Switches
SwitchDescription
/helpDisplays the command-line options
Setup Modes
/passiveUnattended 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.
/quietQuiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options
/norestartDoes not restart when installation has completed
/forcerestartRestarts 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.
/promptrestartDisplay a dialog box prompting the local user to allow a restart
Special Options
/overwriteoemOverwrites OEM files without prompting
/nobackupDoes not back up files needed for uninstall
/forceappscloseForces other programs to close when the computer shuts down
/log:pathAllows the redirection of installation log files
/extract[:path]Extracts files without starting the Setup program
/EREnables extended error reporting
/verboseEnables 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.

Removing the Update

This security update supports the following setup switches.

Supported Spuninst.exe Switches
SwitchDescription
/helpDisplays the command-line options
Setup Modes
/passiveUnattended 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.
/quietQuiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options
/norestartDoes not restart when installation has completed
/forcerestartRestarts 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.
/promptrestartDisplay a dialog box prompting the local user to allow a restart
Special Options
/forceappscloseForces other programs to close when the computer shuts down
/log:pathAllows the redirection of installation log files

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.

    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 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.
    5. 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 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 PacksThe update for this issue will be included in a future service pack or update rollup
Deployment
Installing without user interventionInternet Explorer 6 for Windows XP Service Pack 2:
Windowsxp-kb938127-x86-enu /quiet
Internet Explorer 7 for Windows XP Service Pack 2 and Internet Explorer 7 for Windows XP Service Pack 3:
IE7-KB938127-WindowsXP-x86-enu /quiet
Installing without restartingInternet Explorer 6 for Windows XP Service Pack 2:
Windowsxp-kb938127-x86-enu /norestart
Internet Explorer 7 for Windows XP Service Pack 2 and Internet Explorer 7 for Windows XP Service Pack 3:
IE7-KB938127-WindowsXP-x86-enu /norestart
Update log fileInternet Explorer 6 for Windows XP Service Pack 2:
KB938127.log
Internet Explorer 7 for Windows XP Service Pack 2 and Internet Explorer 7 for Windows XP Service Pack 3:
KB938127-IE7.log
Further informationSee the subsection, Detection and Deployment Tools and Guidance
Restart Requirement
Restart requiredIn some cases, this update does not require a restart. If the required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart
HotpatchingNot applicable
Removal InformationInternet Explorer 6 for Windows XP:
Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallKB938127$\Spuninst folder
Internet Explorer 7 for Windows XP:
Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\ie7updates\KB938127-IE7\spuninst folder
File InformationSee the heading, File Information, below for the full file manifest
Registry Key VerificationInternet Explorer 6 for all supported 32-bit editions of Windows XP:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP\SP3\KB938127\Filelist
Internet Explorer 6 for all supported x64 editions of Windows XP:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP Version 2003\SP3\KB938127\Filelist
Internet Explorer 7 for all supported 32-bit editions of Windows XP:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP\SP0\KB938127-IE7\Filelist
Internet Explorer 7 for all supported x64 editions of Windows XP:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP Version 2003\SP0\KB938127-IE7\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.

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 Internet Explorer 6 for all supported 32-bit editions of Windows XP:

File NameVersionDateTimeSizeFolder
vgx.dll6.0.2900.316426-Jun-200715:13851,968SP2GDR
vgx.dll6.0.2900.316426-Jun-200715:16851,968SP2QFE

Note For a complete list of supported versions and 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.

For Internet Explorer 7 for all supported 32-bit editions of Windows XP:

File NameVersionDateTimeSize
vgx.dll7.0.6000.2062812-Jul-200723:31765,952
vgx.dll7.0.6000.2062812-Jul-200723:28765,952

Note For a complete list of supported versions and 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.

For Internet Explorer 6 for all supported x64 editions of Windows XP:

File NameVersionDateTimeSizeCPUFolder
vgx.dll6.0.3790.296227-Jun-200720:001,427,456X64SP1GDR
wvgx.dll6.0.3790.296227-Jun-200720:00852,992X86SP1GDR\wow
vgx.dll6.0.3790.296227-Jun-200720:021,427,456X64SP1QFE
wvgx.dll6.0.3790.296227-Jun-200720:02852,992X86SP1QFE\wow
vgx.dll6.0.3790.410627-Jun-200720:051,427,456X64SP2GDR
wvgx.dll6.0.3790.410627-Jun-200720:05852,992X86SP2GDR\wow
vgx.dll6.0.3790.410627-Jun-200720:011,427,456X64SP2QFE
wvgx.dll6.0.3790.410627-Jun-200720:01852,992X86SP2QFE\wow

Note For a complete list of supported versions and 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.

For Internet Explorer 7 for all supported x64 editions of Windows XP:

File NameVersionDateTimeSizeCPUFolder
vgx.dll7.0.6000.2062820-Jul-200711:371,104,384X64SP1GDR
wvgx.dll7.0.6000.2062820-Jul-200711:37765,952X86SP1GDR\wow
vgx.dll7.0.6000.2062820-Jul-200711:371,104,384X64SP1QFE
wvgx.dll7.0.6000.2062820-Jul-200711:37765,952X86SP1QFE\wow
vgx.dll7.0.6000.2062820-Jul-200711:421,104,384X64SP2GDR
wvgx.dll7.0.6000.2062820-Jul-200711:42765,952X86SP2GDR\wow
vgx.dll7.0.6000.2062820-Jul-200711:371,104,384X64SP2QFE
wvgx.dll7.0.6000.2062820-Jul-200711:37765,952X86SP2QFE\wow

Note For a complete list of supported versions and 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 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.

Supported Security Update Installation Switches
SwitchDescription
/helpDisplays the command-line options
Setup Modes
/passiveUnattended 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.
/quietQuiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options
/norestartDoes not restart when installation has completed
/forcerestartRestarts 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.
/promptrestartDisplay a dialog box prompting the local user to allow a restart
Special Options
/overwriteoemOverwrites OEM files without prompting
/nobackupDoes not back up files needed for uninstall
/forceappscloseForces other programs to close when the computer shuts down
/log:pathAllows the redirection of installation log files
/integrate:pathIntegrates 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
/EREnables extended error reporting
/verboseEnables 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.

Removing the Update

This security update supports the following setup switches.

Supported Spuninst.exe Switches
SwitchDescription
/helpDisplays the command-line options
Setup Modes
/passiveUnattended 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.
/quietQuiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options
/norestartDoes not restart when installation has completed
/forcerestartRestarts 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.
/promptrestartDisplay a dialog box prompting the local user to allow a restart
Special Options
/forceappscloseForces other programs to close when the computer shuts down
/log:pathAllows the redirection of installation log files

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.

    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 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.
    5. 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 PacksThe update for this issue will be included in a future service pack or update rollup
Deployment
Installing without user interventionInternet Explorer 6 for all supported 32-bit editions, x64 editions, and Itanium-based editions of Windows Server 2003:
Windowsserver2003-kb938127-x86-enu /quiet
Internet Explorer 7 for all supported 32-bit editions, x64 editions, and Itanium-based editions of Windows Server 2003:
IE7-KB938127-WindowsServer2003-x86-enu /quiet
Installing without restartingInternet Explorer 6 for all supported 32-bit editions, x64 editions, and Itanium-based editions of Windows Server 2003:
Windowsserver2003-kb938127-x86-enu /norestart
Internet Explorer 7 for all supported 32-bit editions, x64 editions, and Itanium-based editions of Windows Server 2003:
IE7-KB938127-WindowsServer2003-x86-enu /norestart
Update log fileKB938127.log
Further informationSee the subsection, Detection and Deployment Tools and Guidance
Restart Requirement
Restart requiredIn some cases, this update does not require a restart. If the required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart
HotpatchingThis security update does not support HotPatching. For more information about HotPatching see Microsoft Knowledge Base Article 897341.
Removal InformationInternet Explorer 6 for all supported 32-bit editions, x64 editions, and Itanium-based editions of Windows Server 2003:
Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the Use the Spuninst.exe utility, located in the %Windir%\$NTUninstallKB938127$\Spuninst folder
Internet Explorer 7 for all supported 32-bit editions, x64 editions, and Itanium-based editions of Windows Server 2003:
Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\ie7updates\KB938127-IE7\spuninst folder
File InformationSee the heading, File Information, below for the full file manifest
Registry Key VerificationInternet Explorer 6 for all supported 32-bit editions, x64 editions, and Itanium-based editions of Windows Server 2003:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB938127\Filelist
Internet Explorer 7 for all supported 32-bit editions, x64 editions, and Itanium-based editions of Windows Server 2003:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP0\KB938127-IE7\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 Internet Explorer 6 for all supported 32-bit editions of Windows Server 2003:

File NameVersionDateTimeSizeFolder
vgx.dll6.0.3790.296329-Jun-200713:30852,992SP1GDR
vgx.dll6.0.3790.296329-Jun-200712:58852,992SP1QFE
vgx.dll6.0.3790.410729-Jun-200713:10852,992SP2GDR
vgx.dll6.0.3790.410729-Jun-200713:11852,992SP2QFE

Note For a complete list of supported versions and 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.

For Internet Explorer 7 for all supported 32-bit editions of Windows Server 2003:

File NameVersionDateTimeSize
vgx.dll7.0.6000.2062819-Jul-200713:18765,952
vgx.dll7.0.6000.2062819-Jul-200713:30765,952
vgx.dll7.0.6000.2062819-Jul-200713:54765,952
vgx.dll7.0.6000.2062819-Jul-200713:49765,952

Note For a complete list of supported versions and 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.

For Internet Explorer 6 for all supported Itanium-based editions of Windows Server 2003:

File NameVersionDateTimeSizeCPUFolder
vgx.dll6.0.3790.296227-Jun-200713:042,424,320IA-64SP1GDR
wvgx.dll6.0.3790.296227-Jun-200713:04852,992X86SP1GDR\wow
vgx.dll6.0.3790.296227-Jun-200713:042,424,320IA-64SP1QFE
wvgx.dll6.0.3790.296227-Jun-200713:04852,992X86SP1QFE\wow
vgx.dll6.0.3790.410627-Jun-200713:072,424,320IA-64SP2GDR
wvgx.dll6.0.3790.410627-Jun-200713:07852,992X86SP2GDR\wow
vgx.dll6.0.3790.410627-Jun-200713:042,424,320IA-64SP2QFE
wvgx.dll6.0.3790.410627-Jun-200713:04852,992X86SP2QFE\wow

Note For a complete list of supported versions and 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.

For Internet Explorer 7 for all supported Itanium-based editions of Windows Server 2003:

File NameVersionDateTimeSizeCPUFolder
vgx.dll7.0.6000.2063920-Jul-200704:402,190,848IA-64SP1GDR
wvgx.dll7.0.6000.2062820-Jul-200704:40765,952X86SP1GDR\wow
vgx.dll7.0.6000.2063920-Jul-200704:382,190,848IA-64SP1QFE
wvgx.dll7.0.6000.2062820-Jul-200704:38765,952X86SP1QFE\wow
vgx.dll7.0.6000.2063920-Jul-200704:412,190,848IA-64SP2GDR
wvgx.dll7.0.6000.2062820-Jul-200704:41765,952X86SP2GDR\wow
vgx.dll7.0.6000.2063920-Jul-200704:382,190,848IA-64SP2QFE
wvgx.dll7.0.6000.2062820-Jul-200704:38765,952X86SP2QFE\wow

Note For a complete list of supported versions and 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.

For Internet Explorer 6 for all supported x64 editions of Windows Server 2003:

File NameVersionDateTimeSizeCPUFolder
vgx.dll6.0.3790.296227-Jun-200713:001,427,456X64SP1GDR
wvgx.dll6.0.3790.296227-Jun-200713:00852,992X86SP1GDR\wow
vgx.dll6.0.3790.296227-Jun-200713:021,427,456X64SP1QFE
wvgx.dll6.0.3790.296227-Jun-200713:02852,992X86SP1QFE\wow
vgx.dll6.0.3790.410627-Jun-200713:051,427,456X64SP2GDR
wvgx.dll6.0.3790.410627-Jun-200713:05852,992X86SP2GDR\wow
vgx.dll6.0.3790.410627-Jun-200713:011,427,456X64SP2QFE
wvgx.dll6.0.3790.410627-Jun-200713:01852,992X86SP2QFE\wow

Note For a complete list of supported versions and 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.

For Internet Explorer 7 for all supported x64 editions of Windows Server 2003:

File NameVersionDateTimeSizeCPUFolder
vgx.dll7.0.6000.2062820-Jul-200711:371,104,384X64SP1GDR
wvgx.dll7.0.6000.2062820-Jul-200711:37765,952X86SP1GDR\wow
vgx.dll7.0.6000.2062820-Jul-200711:371,104,384X64SP1QFE
wvgx.dll7.0.6000.2062820-Jul-200711:37765,952X86SP1QFE\wow
vgx.dll7.0.6000.2062820-Jul-200711:421,104,384X64SP2GDR
wvgx.dll7.0.6000.2062820-Jul-200711:42765,952X86SP2GDR\wow
vgx.dll7.0.6000.2062820-Jul-200711:371,104,384X64SP2QFE
wvgx.dll7.0.6000.2062820-Jul-200711:37765,952X86SP2QFE\wow

Note For a complete list of supported versions and 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.

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.

Supported Security Update Installation Switches
SwitchDescription
/helpDisplays the command-line options
Setup Modes
/passiveUnattended 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.
/quietQuiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options
/norestartDoes not restart when installation has completed
/forcerestartRestarts 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.
/promptrestartDisplay a dialog box prompting the local user to allow a restart
Special Options
/overwriteoemOverwrites OEM files without prompting
/nobackupDoes not back up files needed for uninstall
/forceappscloseForces other programs to close when the computer shuts down
/log:pathAllows the redirection of installation log files
/integrate:pathIntegrates 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
/EREnables extended error reporting
/verboseEnables 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 many of 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.

Removing the Update

This security update supports the following setup switches.

Supported Spuninst.exe Switches
SwitchDescription
/helpDisplays the command-line options
Setup Modes
/passiveUnattended 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.
/quietQuiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options
/norestartDoes not restart when installation has completed
/forcerestartRestarts 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.
/promptrestartDisplay a dialog box prompting the local user to allow a restart
Special Options
/forceappscloseForces other programs to close when the computer shuts down
/log:pathAllows the redirection of installation log files

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.

    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 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.
    5. 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 PacksThe update for this issue will be included in a future service pack or update rollup
Deployment
Installing without user interventionInternet Explorer 7 in all supported 32-bit editions of Windows Vista:
Windows6.0-KB938127-x86.msu /quiet
Internet Explorer 7 in all supported 64-bit editions of Windows Vista:
Windows6.0-KB938127-x64.msu /quiet
Installing without restartingInternet Explorer 7 in all supported 32-bit editions of Windows Vista:
Windows6.0-KB938127-x86.msu /quiet /norestart
Internet Explorer 7 in all supported 64-bit editions of Windows Vista:
Windows6.0-KB938127-x64.msu /quiet /norestart
Update log fileKB938127.log
Further informationSee the subsection, Detection and Deployment Tools and Guidance
Restart Requirement
Restart requiredIn some cases, this update does not require a restart. If the required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart
HotpatchingNot applicable.
Removal InformationWUSA.exe does not support uninstall of updates. To uninstall an update installed by WUSA, click Control Panel, click Security, then under Windows Update, click View installed updates and select from the list of updates.
File InformationSee the heading, File Information, below for the full file manifest

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 Internet Explorer 7 in all supported 32-bit editions of Windows Vista:

File NameVersionDateTimeSizeFolder
vgx.dll7.0.6000.1651327-Jun-200702:23765,952Windows6.0-KB938127-x86\x86_microsoft-windows-ie-vgx_31bf3856ad364e35_6.0.6000.16513_none_eb4901d0eb99d160
vgx.dll7.0.6000.2062827-Jun-200702:18765,952Windows6.0-KB938127-x86\x86_microsoft-windows-ie-vgx_31bf3856ad364e35_6.0.6000.20628_none_ebccd02204bb0bce

Note For a complete list of supported versions and 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.

For Internet Explorer 7 in all supported x64 editions of Windows Vista:

File NameVersionDateTimeSizeCPUFolder
vgx.dll7.0.6000.1651327-Jun-200703:311,104,384X64Windows6.0-KB938127-x64\amd64_microsoft-windows-ie-vgx_31bf3856ad364e35_6.0.6000.16513_none_47679d54a3f74296
vgx.dll7.0.6000.2062827-Jun-200703:241,104,384X64Windows6.0-KB938127-x64\amd64_microsoft-windows-ie-vgx_31bf3856ad364e35_6.0.6000.20628_none_47eb6ba5bd187d04
vgx.dll7.0.6000.1651327-Jun-200702:23765,952X86Windows6.0-KB938127-x64\x86_microsoft-windows-ie-vgx_31bf3856ad364e35_6.0.6000.16513_none_eb4901d0eb99d160
vgx.dll7.0.6000.2062827-Jun-200702:18765,952X86Windows6.0-KB938127-x64\x86_microsoft-windows-ie-vgx_31bf3856ad364e35_6.0.6000.20628_none_ebccd02204bb0bce

Note For a complete list of supported versions and 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 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. 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.

Supported Security Update Installation Switches
SwitchDescription
/?, /h, /helpDisplays help on supported switches.
/quietSuppresses the display of status or error messages.
/norestartWhen 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 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

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

    1. Click Start and then enter an update file name in Start Search.
    2. When the file appears under Programs, right-click on the file name and click Properties.
    3. Under the General tab, compare the file size with the file information tables provided earlier in this section.
    4. You may also click on the Details tab and compare information, such as file version and date modified, with the file information tables provided earlier in this section.
    5. 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

Acknowledgments

Microsoft thanks the following for working with us to help protect customers:

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 (August 14, 2007): Bulletin published.
  • V1.1 (August 15, 2007): Bulletin revised to correct file information for Microsoft Internet Explorer 7 for Windows 2003.
  • V1.2 (August 22, 2007): Bulletin revised to correct Registry Key Verification for Internet Explorer 7 for all supported 32-bit editions, 64-bit editions, and Itanium-based editions of Windows Server 2003.
  • V2.0 (August 26, 2008): Bulletin revised to include Internet Explorer 7 for Windows XP Service Pack 3.

Built at 2014-04-16T02:39:51Z-07:00

Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft. All rights reserved.