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

Microsoft Security Bulletin MS05-037 - Critical

Vulnerability in JView Profiler Could Allow Remote Code Execution (903235)

Published: July 12, 2005 | Updated: July 20, 2005

Version: 1.1

Summary

Who should read this document: Customers who use Microsoft Windows

Impact of Vulnerability: Remote Code Execution

Maximum Severity Rating: Critical

Recommendation: Customers should apply the update immediately.

Security Update Replacement: None

Caveats: None

Tested Software and Security Update Download Locations:

Affected Software:

  • Microsoft Windows 2000 Service Pack 4
  • Microsoft Windows XP Service Pack 1 and Microsoft Windows XP Service Pack 2
  • Microsoft Windows XP Professional x64 Edition
  • Microsoft Windows Server 2003
  • Microsoft Windows Server 2003 Service Pack 1
  • Microsoft Windows Server 2003 for Itanium-based Systems
  • Microsoft Windows Server 2003 with SP1 for Itanium-based Systems
  • Microsoft Windows Server 2003 x64 Edition
  • Microsoft Windows 98, Microsoft Windows 98 Second Edition (SE), and Microsoft Windows Millennium Edition (ME)

Tested Microsoft Windows Components:

Affected Components:

  • JView Profiler
  • Internet Explorer 5.01 Service Pack 4 on Microsoft Windows 2000 Service Pack 4 – Download the update
  • Internet Explorer 6 Service Pack 1 on Microsoft Windows 2000 Service Pack 4, or on Microsoft Windows XP Service Pack 1 – Download the update
  • Internet Explorer 6 for Microsoft Windows XP Service Pack 2 – Download the update
  • Internet Explorer 6 for Microsoft Windows Server 2003 and Microsoft Windows Server 2003 Service Pack 1 – Download the update
  • Microsoft Windows Server 2003 for Itanium-based Systems and Microsoft Windows Server 2003 with SP1 for Itanium-based Systems – Download the update
  • Internet Explorer 6 for Microsoft Windows Server 2003 x64 Edition – Download the update
  • Internet Explorer 6 for Microsoft Windows XP Professional x64 Edition – Download the update
  • Internet Explorer 5.5 Service Pack 2 on Microsoft Windows Millennium Edition – – Review the FAQ section of this bulletin for details about these operating systems.
  • Internet Explorer 6 Service Pack 1 on Microsoft Windows 98, on Microsoft Windows 98 SE or on Microsoft Windows Millennium Edition – Review the FAQ section of this bulletin for details about these operating systems.

The software in this list has been tested to determine whether the versions are affected. Other versions either no longer include security update support or may not be affected. To determine the support life cycle for your product and version, visit the Microsoft Support Lifecycle Web site.

General Information

Executive Summary:

This update resolves a newly-discovered, public vulnerability. A COM object, the JView Profiler (Javaprxy.dll), when instantiated in Internet Explorer, contains a remote code execution vulnerability that could allow an attacker to take complete control of an affected system. Since the JView Profiler COM object was not designed to be accessed through Internet Explorer, this update sets the kill bit for the JView Profiler (Javaprxy.dll) COM object. The vulnerability is documented in the “Vulnerability Details” section of this bulletin.

If a user is logged on with administrative user rights, an attacker who successfully exploited this vulnerability could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. 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.

We recommend that customers apply the update immediately.

Severity Ratings and Vulnerability Identifiers:

Vulnerability IdentifiersImpact of VulnerabilityInternet Explorer 5.01 Service Pack 4Internet Explorer 5.5 Service Pack 2 on Windows MEInternet Explorer 6 Service Pack 1 (All supported operating system versions earlier than Windows Server 2003)Internet Explorer 6 for Windows Server 2003 and Windows Server 2003 Service Pack 1Internet Explorer 6 for Windows XP Service Pack 2
JView Profiler Vulnerability - CAN-2005-2087Remote Code ExecutionCriticalCriticalCriticalModerateCritical

This assessment is based on the types of systems that are affected by the vulnerability, their typical deployment patterns, and the effect that exploiting the vulnerability would have on them.

Note The severity ratings for non-x86 operating system versions map to the x86 operating systems versions as follows:

  • The Internet Explorer 6 for Windows XP Professional x64 Edition severity rating is the same as the Internet Explorer 6 Service Pack 1 (All supported operating system versions earlier than Windows Server 2003) severity rating.
  • The Internet Explorer 6 for Microsoft Windows Server 2003 for Itanium-based Systems and Windows Server 2003 x64 Edition severity rating is the same as the Internet Explorer 6 for Windows Server 2003 severity rating.

If I have applied the update available from the Microsoft Download Center for the JView Profiler advisory, do I need to apply this security update?
No. If you have applied the download available from the advisory update issued on July 5, 2005, you do not need to apply this security update.

Does this update contain any changes to functionality?
No. Since the JView Profiler COM object was not designed to be accessed through Internet Explorer, this update sets the kill bit for the JView Profiler (Javaprxy.dll) COM object. To help protect customers who have this object installed, this update prevents it from being instantiated in Internet Explorer. For more information about kill bits, see Microsoft Knowledge Base Article 240797. The class identifier (CLSID) for this object is ‘03D9F3F2-B0E3-11D2-B081-006008039BF0’.

How does the extended support for Windows 98, Windows 98 Second Edition, and Windows Millennium Edition affect the release of security updates for these operating systems?
Microsoft will only release security updates for critical security issues. Non-critical security issues are not offered during this support period. For more information about the Microsoft Support Lifecycle policies for these operating systems, visit the following Web site.

For more information about severity ratings, visit the following Web site.

Note Critical security updates for these operating systems may not be available at the same time as the other security updates that are included with this security bulletin. They will be made available as soon as possible following the release. When these security updates are available, you will be able to download them only from the Windows Update Web site.

Are Windows 98, Windows 98 Second Edition, or Windows Millennium Edition critically affected by one or more of the vulnerabilities that are addressed in this security bulletin?
Yes. Windows 98, Windows 98 Second Edition, and Windows Millennium Edition are critically affected by this vulnerability. These security updates are available for download from the Windows Update Web site. For more information about severity ratings, visit the following Web site.

Note Updates for localized versions of Microsoft Windows Millennium Edition that are not supported by Windows Update are available for download at the following download locations:

Extended security update support for Microsoft Windows NT Workstation 4.0 Service Pack 6a and Windows 2000 Service Pack 2 ended on June 30, 2004. Extended security update support for Microsoft Windows NT Server 4.0 Service Pack 6a ended on December 31, 2004. Extended security update support for Microsoft Windows 2000 Service Pack 3 ended on June 30, 2005. I am still using one of these operating systems, what should I do?
Windows NT Workstation 4.0 Service Pack 6a, Windows NT Server 4.0 Service Pack 6a, Windows 2000 Service Pack 2, and Windows 2000 Service Pack 3 have reached the end of their life cycles. It should be a priority for customers who have these operating system versions to migrate to supported versions to prevent potential exposure to vulnerabilities. For more information about the Windows Product Lifecycle, visit the following Microsoft Support Lifecycle Web site. For more information about the extended security update support period for these operating system versions, visit the Microsoft Product Support Services Web site.

Customers who require additional support for Windows NT 4.0 SP6a 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.

Security update support for Microsoft Windows XP 64-Bit Edition Service Pack 1 (Itanium) and Microsoft Windows XP 64-Bit Edition Version 2003 (Itanium) ended on June 30, 2005. I am still using one of these operating systems, what should I do?
With the release of Windows XP Professional x64 Edition, Microsoft Windows XP 64-Bit Edition Service Pack 1 (Itanium) and Microsoft Windows XP 64-Bit Edition Version 2003 (Itanium) will no longer receive security update support. It should be a priority for customers who have these operating system versions to migrate to supported versions to prevent potential exposure to vulnerabilities. Microsoft will continue to fully support Windows Server 2003 for Itanium-based systems, Windows XP Professional x64 Edition, and Windows Server 2003 x64 Editions for 64-bit computing requirements. Microsoft continues to license and support Windows Server 2003 Enterprise and Datacenter editions for Itanium-based systems, and the 64-bit version of SQL Server 2000 Enterprise Edition. In the future, we will expand Itanium support to Visual Studio 2005, .NET Framework 2005, and SQL Server 2005.

Customers who require additional assistance about this issue must contact their Microsoft account team representative, their Technical Account Manager, or the appropriate Microsoft partner representative for information about the available migration 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.

Can I use the Microsoft Baseline Security Analyzer (MBSA) 1.2.1 to determine whether this update is required?
Yes. MBSA 1.2.1 will determine whether this update is required. For more information about MBSA, visit the MBSA Web site.

Can I use the Microsoft Baseline Security Analyzer (MBSA) 2.0 to determine whether this update is required?
Yes. MBSA 2.0 will determine whether this update is required. MBSA 2.0 can detect security updates for products that Microsoft Update supports. For more information about MBSA, visit the MBSA Web site.

Can I use Systems Management Server (SMS) to determine whether this update is required?
Yes. SMS can help detect and deploy this security update. For information about SMS, visit the SMS Web site.

JView Profiler Vulnerability - CAN-2005-2087:

A remote code execution vulnerability exists in JView Profiler. An attacker could exploit the vulnerability by constructing a malicious Web page that could potentially allow remote code execution if a user visited the malicious Web site. An attacker who successfully exploited this vulnerability could take complete control of an affected system.

Mitigating Factors for JView Profiler Vulnerability - CAN-2005-2087:

  • In a Web-based attack scenario, an attacker would have to host a Web site that contains a Web page that is used to exploit this vulnerability. An attacker would have no way to force users to visit a malicious Web site. Instead, an attacker would have to persuade them to visit the Web site, typically by getting them to click a link that takes them 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.
  • The Microsoft Java Virtual Machine is not included in the following software by default:
    • Windows XP Service Pack 1a and Windows XP Service Pack 2
    • Windows Server 2003 and Windows Server 2003 Service Pack 1

    However, the Microsoft Java Virtual Machine may have been installed by an application. It could also be present as a result of upgrading the operating system. Customers can use the MSJVM Diagnostic Tool, which is available from the Microsoft Java Virtual Machine Support page. Customers can use this tool to perform remote and local scans to detect for the presence of MSJVM and MSJVM-related software. See the “How do I know if I have the Javaprxy.dll on my system?” question in the FAQ section of this document for more information.

  • The Restricted sites zone helps reduce attacks that could try to exploit this vulnerability by preventing ActiveX controls from being used when reading HTML e-mail. However, if a user clicks on a link within an e-mail they could still be vulnerable to this issue through the Web-based attack scenario described previously.

Workarounds for JView Profiler Vulnerability - CAN-2005-2087:

Microsoft has tested the following workarounds. While these workarounds will not correct the underlying vulnerability, they help block known attack vectors. The workarounds are mutually exclusive so users need only apply one to be secure. When a workaround reduces functionality, it is identified in the following section.

  • Set Internet and Local intranet security zone settings to “High” to prompt before running ActiveX controls 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.

    Repeat steps 1 through 3 for the Local intranet security zone by clicking on the Local intranet icon.

    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: User will be prompted prior to running ActiveX controls unless the Web site is in the user’s list of trusted sites.

  • Configure Internet Explorer to prompt before running ActiveX controls or disable ActiveX controls in the Internet and Local intranet security zone

    You can help protect against this vulnerability by changing your settings to prompt before running ActiveX controls or disable ActiveX controls in the Internet and Local intranet security zone. To do this, 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. Click Custom Level.
    4. Under Settings, in the ActiveX controls and plug-ins section, under Run ActiveX controls and plug-ins, click Prompt or Disable, and then click OK.
    5. Click Local intranet, and then click Custom Level.
    6. Under Settings, in the ActiveX controls and plug-ins section, under Run ActiveX controls and plug-ins, click Prompt or Disable, and then click OK.
    7. Click OK two times to return to Internet Explorer.

    Impact of Workaround: There are side effects to prompting before running ActiveX controls. Many Web sites that are on the Internet or on an intranet use ActiveX 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 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.

  • Un-register the Javaprxy.dll COM Object

    To un-register Javaprxy.dll, follow these steps:

    1. Click Start, click Run, type "regsvr32 /u javaprxy.dll" (without the quotation marks), 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.
    3. Close Internet Explorer, and reopen it for the changes to take effect.

    Impact of Workaround: Applications that require the Microsoft Java Virtual Machine may no longer function correctly.

    To undo this change, re-register Javaprxy.dll by following the above steps. Replace the text in Step 1 with “regsvr32 %windir%\system32\javaprxy.dll” (without the quotation marks).

  • Modify the Access Control List on Javaprxy.dll to be more restrictive

    To modify the Access Control List (ACL) on Javaprxy.dll to be more restrictive, follow these steps:

    1. Click Start, click Run, type "cmd" (without the quotation marks), and then click OK.
    2. Type the following command at a command prompt. Make a note of the current ACLs that are on the file (including inheritance settings) for future reference in case you have to undo this modification:

      cacls %windir%\system32\javaprxy.dll

    3. Type the following command at a command prompt to deny the ‘everyone’ group access to this file:

      cacls %windir%\system32\javaprxy.dll /d everyone

    4. Close Internet Explorer, and reopen it for the changes to take effect.

    Impact of Workaround: Applications that require the Microsoft Java Virtual Machine may no longer function correctly.

  • Restrict access to Javaprxy.dll in Internet Explorer by using a Software Restriction Policy

    To restrict access to Javaprxy.dll in Internet Explorer on Windows XP and later versions you can create a Software Restriction Policy. To create this policy, use a registry script or create a Group Policy setting to block the loading of the Javaprxy.dll.

    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.

    We recommend that you back up the registry before you edit it.

    Use the following text to create a .reg file to un-register Javaprxy.dll in Internet Explorer. You can copy the following text, paste it into a text editor such as Notepad, and then save the file with the .reg file name extension. Run the .reg file on the vulnerable client.

    Windows Registry Editor Version 5.00

    [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Safer\CodeIdentifiers]
    "TransparentEnabled"=dword:00000002

    [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Safer\CodeIdentifiers\0\Paths\{09687f8a-0ca9-4639-b295-a3f5b5be8fc5}]
    "LastModified"=hex(b):50,09,1f,b1,04,4a,c5,01
    "Description"="Block javaprxy.dll"
    "SaferFlags"=dword:00000000
    "ItemData"=hex(2):25,00,77,00,69,00,6e,00,64,00,69,00,72,00,25,00,5c,00,73,00,\
    79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,6a,00,61,00,76,00,61,00,70,\
    00,72,00,78,00,79,00,2e,00,64,00,6c,00,6c,00,00,00

    Impact of Workaround: Applications that require the Microsoft Java Virtual Machine may no longer function correctly.

  • Remove the Microsoft Java Virtual Machine from your system using the Java Removal Tool

    Customers can use the MSJVM Diagnostic Tool, available from the Microsoft Java Virtual Machine Support page, to perform remote and local scans to detect for the presence of MSJVM and MSJVM-related software.

    Customers can then use the Java Removal Tool to permanently remove the Microsoft Java Virtual Machine from their system. For more information about how to qualify for access to the Java Removal Tool from Microsoft Product Support Services, see Microsoft Knowledge Base Article 826878.

    Warning: Removing the Microsoft Java Virtual Machine from your system is permanent. Microsoft cannot provide Windows operating system recovery media to you that includes the MSJVM for reinstallation. Microsoft no longer includes the MSJVM in Windows operating system products.

    Impact of Workaround: Applications that require the Microsoft Java Virtual Machine will no longer function correctly.

FAQ for JView Profiler Vulnerability - CAN-2005-2087:

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

What causes the vulnerability?
When Internet Explorer tries to instantiate the JView Profiler (Javaprxy.dll) COM object as an ActiveX control, it may corrupt system memory in such a way that an attacker could execute arbitrary code.

What is JView Profiler?
JView Profiler is a debugger interface for Microsoft Java Virtual Machine (MSJVM). For more information about the Microsoft Java Virtual Machine (MSJVM), visit the Microsoft Java Virtual Machine Web site

How do I know if I have Javaprxy.dll on my system?
Customers can either search for this file or they can use the Microsoft Java Virtual Machine (MSJVM) Diagnostic Tool. This tool is available from the Microsoft Java Virtual Machine Support page, and can be used to perform remote and local scans to detect for the presence of MSJVM and MSJVM-related software.

What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could take complete control of the affected system. In a Web-based attack scenario, an attacker would host a Web site that exploits this vulnerability. An attacker would have no way to force users to visit a malicious Web site. Instead, an attacker would have to persuade them to visit the Web site, typically by getting them to click a link that takes them to the attacker's site. It could also be possible to display malicious Web content by using banner advertisements or by using other methods to deliver Web content to affected systems.

How could an attacker exploit the vulnerability?
An attacker could host a malicious Web site that is designed to exploit this vulnerability through Internet Explorer and then persuade a user to view the Web site.

What systems are primarily at risk from the vulnerability?
This vulnerability requires that a user is logged on and reading e-mail messages or by 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.

Are Windows 98, Windows 98 Second Edition or Windows Millennium Edition critically affected by this vulnerability?
Yes. Windows 98, Windows 98 Second Edition, and Windows Millennium Edition are critically affected by this vulnerability. The security updates are available from the Windows Update Web site. For more information about severity ratings, visit the following Web site.

What does the update do?
Since the JView Profiler COM object was not designed to be accessed through Internet Explorer, this update sets the kill bit for the JView Profiler (Javaprxy.dll) COM object. To help protect customers who have this object installed, this update prevents it from being instantiated in Internet Explorer. For more information about kill bits, see Microsoft Knowledge Base Article 240797. The class identifier (CLSID) for this object is ‘03D9F3F2-B0E3-11D2-B081-006008039BF0’.

When this security bulletin was issued, had this vulnerability been publicly disclosed?
Yes. This vulnerability has been publicly disclosed. It has been assigned Common Vulnerability and Exposure number CAN-2005-2087.

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.

Does applying this security update help protect customers from the code that has been published publicly that attempts to exploit this vulnerability?
Yes. This security update addresses the vulnerability that is being exploited. The vulnerability that has been addressed has been assigned the Common Vulnerability and Exposure number CAN-2005-2087.

Affected Software:

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

Internet Explorer 6 for Windows Server 2003 (all versions), Microsoft Windows Server 2003 x64 Edition, and for Microsoft Windows XP Professional x64 Edition

Prerequisites
This security update requires Internet Explorer 6 on Windows Server 2003, on Windows Server 2003 Service Pack 1, on Microsoft Windows Server 2003 x64 Edition, or on Microsoft Windows XP Professional x64 Edition

Inclusion in Future Service Packs:
The update for this issue will be included in a future Service Pack or Update Rollup.

Installation Information

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. For more information about the Update.exe installer, visit the Microsoft TechNet Web site.

Deployment Information

To install the security update without any user intervention, use the following command at a command prompt for the corresponding version of the Operating System:

Windows Server 2003 and Windows Server 2003 Service Pack 1:

Windowsserver2003-KB903235-x86-ENU.exe/quiet

Windows Server 2003 x64 Edition:

Windowsserver2003-KB903235-x64-ENU.exe /quiet

Microsoft Windows XP Professional x64 Edition:

WindowsXP-KB903235-x64-ENU.exe /quiet

Note Use of the /quiet switch will suppress all messages. This includes suppressing failure messages. Administrators should use one of the supported methods to verify the installation was successful when they use the /quiet switch. Administrators should also review the KB903235.log file for any failure messages when they use this switch.

For information about how to deploy this security update by using Software Update Services, visit the Software Update Services Web site. For information about how to deploy this security update using Windows Server Update Services, visit the Windows Server Update Services Web site. This security update will also be available through the Microsoft Update Web site.

Restart Requirement

This update does not require a restart.

Removal Information

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

System administrators can also use the Spuninst.exe utility to remove this security update. The Spuninst.exe utility is located in the %Windir%\$NTUninstallKB903235$\Spuninst folder.

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. MBSA allows administrators to scan local and remote systems for missing security updates and for common security misconfigurations. For more information about MBSA, visit the Microsoft Baseline Security Analyzer Web site.

  • Registry Key Verification

    You may also be able to verify the files that this security update has installed by reviewing the following registry keys.

    Windows Server 2003, Web Edition; Windows Server 2003, Standard Edition; Windows Server 2003, Enterprise Edition; Windows Server 2003, Datacenter Edition; Windows Small Business Server 2003; Windows Server 2003, Web Edition with SP1; Windows Server 2003, Standard Edition with SP1; Windows Server 2003, Enterprise Edition with SP1; and Windows Server 2003, Datacenter Edition with SP1:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility\{03D9F3F2-B0E3-11D2-B081-006008039BF0}

    Windows Server 2003, Enterprise Edition for Itanium-based Systems; Windows Server 2003, Datacenter Edition for Itanium-based Systems; Windows Server 2003, Enterprise Edition with SP1 for Itanium-based Systems; Windows Server 2003, Datacenter Edition with SP1 for Itanium-based Systems; Windows Server 2003, Standard x64 Edition; Windows Server 2003, Enterprise x64 Edition; Windows Server 2003, Datacenter x64 Edition; and Microsoft Windows XP Professional x64 Edition:

    • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility\{03D9F3F2-B0E3-11D2-B081-006008039BF0}
    • HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Internet Explorer\ActiveX Compatibility\{03D9F3F2-B0E3-11D2-B081-006008039BF0}

Internet Explorer 6 for Windows XP Service Pack 2

Prerequisites
This update requires Internet Explorer 6 on Windows XP Service Pack 2. For more information, see Microsoft Knowledge Base Article 322389.

Inclusion in Future Service Packs:
The update for this issue will be included in a future Service Pack or Update Rollup.

Installation Information

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. For more information about the Update.exe installer, visit the Microsoft TechNet Web site.

Deployment Information

To install the security update without any user intervention, use the following command at a command prompt for Windows XP Service Pack 2:

Windowsxp-kb903235-x86-ENU.exe /quiet

Note Use of the /quiet switch will suppress all messages. This includes suppressing failure messages. Administrators should use one of the supported methods to verify the installation was successful when they use the /quiet switch. Administrators should also review the KB903235.log file for any failure messages when they use this switch.

For information about how to deploy this security update by using Software Update Services, visit the Software Update Services Web site. For information about how to deploy this security update using Windows Server Update Services, visit the Windows Server Update Services Web site. This security update will also be available through the Microsoft Update Web site.

Restart Requirement

This update does not require a restart.

Removal Information

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

System administrators can also use the Spuninst.exe utility to remove this security update. The Spuninst.exe utility is located in the %Windir%\$NTUninstallKB903235$\Spuninst folder.

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. MBSA allows administrators to scan local and remote systems for missing security updates and for common security misconfigurations. For more information about MBSA, visit the Microsoft Baseline Security Analyzer Web site.

  • Registry Key Verification

    You may also be able to verify the files that this security update has installed by reviewing the following registry keys.

    For Windows XP Home Edition Service Pack 2, Windows XP Professional Service Pack 2, Windows XP Tablet PC Edition 2005, and Windows XP Media Center Edition 2005:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility\{03D9F3F2-B0E3-11D2-B081-006008039BF0}

Internet Explorer 6 Service Pack 1 for Windows XP Service Pack 1 and Windows 2000 Service Pack 4

Prerequisites
To install the Internet Explorer 6 Service Pack 1 (SP1) version of this update, you must be running Internet Explorer 6 SP1 (version 6.00.2800.1106) on one of the following versions of Windows:

  • Microsoft Windows 2000 Service Pack 4
  • Microsoft Small Business Server 2000 Service Pack 1a (SP1a) or Small Business Server 2000 running with Windows 2000 Server Service Pack 4 (SP4)
  • Microsoft Windows XP Service Pack 1

The software that is listed has been tested to determine whether the versions are affected. Other versions either no longer include security update support or may not be affected. To determine the support life cycle for your product and version, visit the Microsoft Support Lifecycle Web site.

For more information about how to obtain the latest service pack, see Microsoft Knowledge Base Article 260910.

Inclusion in Future Service Packs:
The update for this issue may be included in a future Update Rollup.

Installation Information

This update uses the IExpress installer technology. For more information on IExpress, please see Microsoft Knowledge Base Article 197147.

This security update supports the following setup switches.

Supported Security Update Installation Switches
SwitchDescription
Setup Modes
/qSpecifies quiet mode, or suppresses prompts, when files are being extracted.
/q:uSpecifies user-quiet mode, which presents some dialog boxes to the user.
/q:aSpecifies administrator-quiet mode, which does not present any dialog boxes to the user.
Restart Options
/r:nNever restarts the computer after installation.
/r:iPrompts the user to restart the computer if a restart is required, except when used with /q:a.
/r:aAlways restarts the computer after installation.
/r:sRestarts the computer after installation without prompting the user.
Special Options
/t:<full path>Specifies the target folder for extracting files.
/cExtracts the files without installing them. If /T: path is not specified, user will be prompted for a target folder.
/c:<Cmd>Override Install Command defined by author. Specifies the path and name of the Setup .inf or .exe file.

Note These switches do not necessarily work with all updates. If a switch is not available, then that functionality is necessary for the correct installation of the update. Also, the use of the /N:V switch is unsupported and may result in an unbootable system. If the installation is unsuccessful, you should consult your support professional to understand why it failed to install.

For additional information about the supported setup switches, see Microsoft Knowledge Base Article 197147.

Deployment Information

To install the security update without any user intervention, use the following command at a command prompt for Windows XP Service Pack 1:

IE-KB903235-x86-ENU.exe /q:a

For information about how to deploy this security update by using Software Update Services, visit the Software Update Services Web site. For information about how to deploy this security update using Windows Server Update Services, visit the Windows Server Update Services Web site. This security update will also be available through the Microsoft Update Web site.

Restart Requirement

This update does not require a restart.

Removal Information

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

System administrators can use the Ieuninst.exe utility to remove this update. This security update installs the Ieuninst.exe utility in the %Windir% folder. This utility supports the following setup switches:

Supported Ieuninst.exe Switches
SwitchDescription
/?Displays the command-line options
Setup Modes
/qQuiet mode. No user interaction is required.
Restart Options
/zDoes not restart when installation is complete.

For example, to remove this update quietly, use the following command:

c:\windows\ieuninst /q c:\windows\inf\q903235.inf

Note This command assumes that Windows is installed in the C:\Windows folder.

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. MBSA allows administrators to scan local and remote systems for missing security updates and for common security misconfigurations. For more information about MBSA, visit the Microsoft Baseline Security Analyzer Web site.

  • Registry Key Verification

    You may also be able to verify the files that this security update has installed by reviewing the following registry key.

    For Windows XP Home Edition Service Pack 1, Windows XP Professional Service Pack 1, Windows XP Tablet PC Edition, Windows XP Media Center Edition, Windows 2000 Service Pack 4 and Small Business Server 2000:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility\{03D9F3F2-B0E3-11D2-B081-006008039BF0}

Internet Explorer 5.01 for Windows 2000 Service Pack 4

Prerequisites
To install the Internet Explorer 5.01 version of this update, you must be running Internet Explorer 5.01 Service Pack 4 (version 5.00.3700.1000) on Windows 2000 (all versions).

For Small Business Server 2000, this security update requires Small Business Server 2000 Service Pack 1a (SP1a) or Small Business Server 2000 running with Windows 2000 Server Service Pack 4 (SP4).

Note Versions of Windows and versions of Internet Explorer that are not listed in this article are no longer supported. Although you can install some of the update packages that are described in this article on these unlisted versions of Windows and of Internet Explorer, Microsoft has not tested them to assess whether they are affected by these vulnerabilities. Microsoft has also not tested these versions to confirm that the update that this bulletin describes addresses these vulnerabilities. We recommend that you upgrade to a supported version of Windows and of Internet Explorer, and then install the appropriate update.

The software that is listed has been tested to determine whether the versions are affected. Other versions either no longer include security update support or may not be affected. To determine the support life cycle for your product and version, visit the Microsoft Support Lifecycle Web site.

For more information about how to obtain the latest service pack, see Microsoft Knowledge Base Article 260910.

Inclusion in Future Service Packs:
The update for this issue may be included in a future Update Rollup.

Installation Information

This update uses the IExpress installer technology. For more information on IExpress, please see Microsoft Knowledge Base Article 197147.

This security update supports the following setup switches.

Supported Security Update Installation Switches
SwitchDescription
Setup Modes
/qSpecifies quiet mode, or suppresses prompts, when files are being extracted.
/q:uSpecifies user-quiet mode, which presents some dialog boxes to the user.
/q:aSpecifies administrator-quiet mode, which does not present any dialog boxes to the user.
Restart Options
/r:nNever restarts the computer after installation.
/r:iPrompts the user to restart the computer if a restart is required, except when used with /q:a.
/r:aAlways restarts the computer after installation.
/r:sRestarts the computer after installation without prompting the user.
Special Options
/t:<full path>Specifies the target folder for extracting files.
/cExtracts the files without installing them. If /T: path is not specified, user will be prompted for a target folder.
/c:<Cmd>Override Install Command defined by author. Specifies the path and name of the Setup .inf or .exe file.

Note These switches do not necessarily work with all updates. If a switch is not available, then that functionality is necessary for the correct installation of the update. Also, the use of the /N:V switch is unsupported and may result in an unbootable system. If the installation is unsuccessful, you should consult your support professional to understand why it failed to install.

For additional information about the supported setup switches, see Microsoft Knowledge Base Article 197147.

Deployment Information

To install the security update without any user intervention, use the following command at a command prompt for Windows 2000 Service Pack 4:

IE-KB903235-x86-ENU.exe /q:a

For information about how to deploy this security update by using Software Update Services, visit the Software Update Services Web site. For information about how to deploy this security update using Windows Server Update Services, visit the Windows Server Update Services Web site. This security update will also be available through the Microsoft Update Web site.

Restart Requirement

This update does not require a restart.

Removal Information

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

System administrators can use the Ieuninst.exe utility to remove this update. This security update installs the Ieuninst.exe utility in the %Windir% folder. This utility supports the following setup switches:

Supported Ieuninst.exe Switches
SwitchDescription
/?Displays the command-line options
Setup Modes
/qQuiet mode. No user interaction is required.
Restart Options
/zDoes not restart when installation is complete.

For example, to remove this update quietly, use the following command:

c:\windows\ieuninst /q c:\windows\inf\q903235.inf

Note This command assumes that Windows is installed in the C:\Windows folder.

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. MBSA allows administrators to scan local and remote systems for missing security updates and for common security misconfigurations. For more information about MBSA, visit the Microsoft Baseline Security Analyzer Web site.

  • Registry Key Verification

You may also be able to verify the files that this security update has installed by reviewing the following registry keys:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility\{03D9F3F2-B0E3-11D2-B081-006008039BF0}

Other Information

Obtaining Other Security Updates:

Updates for other security issues are available at the following locations:

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.

Security Resources:

Software Update Services:

By using Microsoft Software Update Services (SUS), administrators can quickly and reliably deploy the latest critical updates and security updates to Windows 2000 and Windows Server 2003-based servers, and to desktop systems that are running Windows 2000 Professional or Windows XP Professional.

For more information about how to deploy this security update by using Software Update Services, visit the Software Update Services Web site.

Windows Server Update Services:

By using Windows Server Update Services (WSUS), administrators can quickly and reliably 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:

Microsoft Systems Management Server (SMS) delivers a highly-configurable enterprise solution for managing updates. By using SMS, administrators can identify Windows-based systems that require security updates and can perform controlled deployment of these updates throughout the enterprise with minimal disruption to end users. For more information about how administrators can use SMS 2003 to deploy security updates, visit the SMS 2003 Security Patch Management Web site. SMS 2.0 users can also use Software Updates Service Feature Pack to help deploy security updates. For information about SMS, visit the SMS Web site.

Note SMS uses the Microsoft Baseline Security Analyzer, the Microsoft Office Detection Tool, and the Enterprise Update Scanning Tool to provide broad support for security bulletin update detection and deployment. Some software updates may not be detected by these tools. Administrators can use the inventory capabilities of the SMS in these cases to target updates to specific systems. For more information about this procedure, visit the following Web site. Some security updates require administrative rights following a restart of the system. Administrators can use the Elevated Rights Deployment Tool (available in the SMS 2003 Administration Feature Pack and in the SMS 2.0 Administration Feature Pack) to install these updates.

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 (July 12, 2005): Bulletin published
  • V1.1 (July 20, 2005): Added section in JView Profiler FAQ about how to detect if Javaprxy.dll is on a computer. Updated title in Security Update section to reflect all supported versions of Windows 2000.

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.