|
Microsoft Security Bulletin MS07-043 - CriticalVulnerability in OLE Automation Could Allow Remote Code Execution (921503)Published: August 14, 2007 Version: 1.0 Executive SummaryThis
critical security update resolves a privately reported vulnerability.
This vulnerability could allow remote code execution if a user viewed a
specially crafted Web page. The vulnerability could be exploited
through attacks on Object Linking and Embedding (OLE). 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. This
is a critical security update for all supported editions of Windows
2000, Windows XP, Office 2004 for Mac, and Visual Basic 6. For other
affected editions of Windows, this update is rated moderate. For more
information, see the subsection, Affected and Non-Affected Software, in this section. This
security update addresses the vulnerability by adding a check on memory
requests within OLE Automation. For more information about the
vulnerability, see the Frequently Asked Questions (FAQ) subsection for
the specific vulnerability entry under the next section, Vulnerability Information. Recommendation: Microsoft recommends that customers apply the update immediately. Known Issues: Microsoft Knowledge Base Article 921503
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 SoftwareIn
the following tables of affected and non-affected software, software
editions that are not listed are past their support lifecycle. To
determine the support lifecycle for your product and edition, visit Microsoft Support Lifecycle. Affected Software Non-Affected Software Windows Vista | Windows Vista x64 Edition |
 | |
What updates does this release replace?
This security update does not replace a prior security update. What are the known issues that customers may experience when they install this security update?
Microsoft Knowledge Base Article 921503
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 edition of the software discussed in this security bulletin. What should I do?
Theaffected
software listed in this bulletin has been tested to determine which
editions are affected. Other editions are past their support life
cycle. To determine the support life cycle for your product and
edition, visit Microsoft Support Lifecycle. It
should be a priority for customers who have older editions of the
software to migrate to supported editions 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 operating system editions, 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. |
Windows 2000 Service Pack 4 | Critical Remote Code Execution | Critical | Windows XP Service Pack 2 | Critical Remote Code Execution | Critical | Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2 | Critical Remote Code Execution | Critical | Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2 | Moderate Remote Code Execution | Moderate | Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2 | Moderate Remote Code Execution | Moderate | Windows Server 2003 with SP1 for Itanium-based Systems and Windows Server 2003 with SP2 for Itanium-based Systems | Moderate Remote Code Execution | Moderate | Microsoft Office 2004 for Mac | Critical Remote Code Execution | Critical | Microsoft Visual Basic 6.0 Service Pack 6 | Critical Remote Code Execution | Critical |
| |
A
remote code execution vulnerability exists in Object linking and
embedding (OLE) Automation that could allow an attacker who
successfully exploited this vulnerability to make changes to the system
with the permissions of the logged-on user. If a user is logged on with
administrative user rights, an attacker could take complete control of
the 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. To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2007-2224. | |
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, Web sites that accept or host user-provided content, or
compromised Web sites and advertisement servers could contain specially
crafted content that could exploit this vulnerability. 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. | | • | By
default, all supported editions of Microsoft Outlook and Microsoft
Outlook Express open HTML e-mail messages in the Restricted sites zone.
The Restricted sites zone helps reduce the number of successful attacks
that exploit this vulnerability by preventing Active Scripting and
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. | | • | By default, Internet Explorer on Windows Server 2003 runs in a restricted mode that is known as Enhanced Security Configuration.
This mode sets the security level for the Internet zone to High. This
is a mitigating factor for Web sites that have not been added to
Internet Explorer Trusted sites zone. See the FAQ subsection of this
vulnerability section for more information about Internet Explorer
Enhanced Security Configuration. |
| |
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: | • | Configure
Internet Explorer to prompt before running Active Scripting or to
disable Active Scripting in the Internet and Local intranet security
zone You can help protect against this vulnerability by
changing your settings to prompt before running Active Scripting or to
disable Active Scripting in the Internet and Local intranet security
zone. To do this, follow these steps: 1. | In Internet Explorer, click Internet Options on the Tools menu. | 2. | Click the Security tab. | 3. | Click Internet, and then click Custom Level. | 4. | Under Settings, in the Scripting section, under Active Scripting, click Prompt or Disable, and then click OK. | 5. | Click Local intranet, and then click Custom Level. | 6. | Under Settings, in the Scripting section, under Active Scripting, click Prompt or Disable, and then click OK. | 7. | Click OK two times to return to Internet Explorer. |
Impact of Workaround: Disabling
Active Scripting in the Internet and Local intranet security zones 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. 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
system. Two in particular that you may want to add are
"*.windowsupdate.microsoft.com" and “*.update.microsoft.com” (without
the quotation marks). These are the sites that will host the update,
and it requires an ActiveX Control to install the update. |
| • | 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. 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. 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”. |
| |
What is the scope of the vulnerability?
If
successfully exploited, this remote code execution vulnerability could
allow the attacker to run arbitrary code as the logged-on user. What causes the vulnerability?
Specially crafted script requests may cause memory corruption when using OLE Automation. What is OLE Automation?
Object
linking and embedding (OLE) Automation is a Windows protocol that
allows an application to share data or control another application. OLE
Automation is an industry standard that applications use to expose
their OLE objects to development tools, macro languages, and other
containers that support OLE Automation. What might an attacker use the vulnerability to do?
An
attacker who successfully exploited this vulnerability could make
changes to the system with the permissions of the logged-on user. If a
user is logged on with administrative user rights, an attacker could
take complete control of the 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. 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 Web sites that
accept user-provided content or advertisements, Web sites that host
user-provided content or advertisements, and compromised Web sites.
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 visits a Web site
for any malicious action to occur. Therefore, any systems where
Internet Explorer is used frequently, such as workstations or terminal
servers, are at the most risk from this vulnerability. What does the update do?
The update removes the vulnerability by validating the memory request within OLE Automation. I am running Internet Explorer for Windows Server 2003. Does this mitigate this vulnerability?
Yes. By default, Internet Explorer for Windows Server 2003 runs in a restricted mode that is known as Enhanced Security Configuration.
Enhanced Security Configuration is a group of preconfigured settings in
Internet Explorer that can reduce the likelihood of a user or
administrator downloading and running malicious Web content on a
server. This is a mitigating factor for Web sites that you have not
added to the Internet Explorer Trusted sites zone. See also Managing Internet Explorer Enhanced Security Configuration. I
am a third-party application developer and I use OLE Automation in my
application. Is my application vulnerable and how do I update it?
Visual Basic 6.0 is the only development platform affected by this security update. This Bulletin provides a link to download
an update for the Visual Basic 6.0 Service Pack 6. Developers are
encouraged to follow recommended best practices for using a shared
component. For more information on best practices on shared component
use, please see the Microsoft Knowledge Base Article 835322 on Isolated Applications. If
third-party applications use or install the affected OLE component,
could I still be vulnerable even after I have installed all required
Microsoft security updates?
No, this security update
replaces and re-registers the affected OLE component provided with the
operating system. If third party applications follow the recommended
best practices for using a shared component as a side by side assembly
then they are also not affected. Microsoft Knowledge Base Article 921503
also contains instructions for customers that wish to manually check
for the registered affected OLE component. Customers are encouraged to
contact their third party solutions developer for addition information. 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. | |
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 Analyzerand Enterprise Update Scan Tool (EST) 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. MBSA
1.2.1 does not support detection for some platforms affected by this
security update. The Enterprise Update Scan Tool does, and is what
customers can use instead of MBSA 1.2.1. For download links and more
information about the version of EST that is being released this month,
see Microsoft Knowledge Base Article 894193. SMS customers should also see the heading, Systems Management Server, for more information about SMS and EST. The following table provides the MBSA and EST detection summary for this security update. Windows 2000 Service Pack 4 | Yes | No | Yes | Windows XP Service Pack 1 and Windows XP Service Pack 2 | Yes | No | Yes | Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2 | No | No | Yes | Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2 | Yes | No | Yes | Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2 | No | No | Yes | Windows Server 2003 with SP1 for Itanium-based Systems and Windows Server 2003 with SP2 for Itanium-based Systems | No | No | Yes | Microsoft Office 2004 for Mac | No | No | No | Microsoft Visual Basic 6.0 Service Pack 6 | No | Yes | No |
Note MBSA does not support Microsoft Visual Basic 6.0 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. 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. Windows 2000 Service Pack 4 | Yes | Yes | Windows XP Service Pack 2 | Yes | Yes | Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2 | No | Yes | Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2 | Yes | Yes | Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2 | No | Yes | Windows Server 2003 with SP1 for Itanium-based Systems and Windows Server 2003 with SP2 for Itanium-based Systems | No | Yes | Microsoft Office 2004 for Mac | No | No | Microsoft Visual Basic 6.0 Service Pack 6 | Yes (with EST) | No |
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. 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: | |
Reference Table The
following table contains the security update information for this
software. You can find additional information in the subsection, Deployment Information, in this section. Inclusion in Future Service Packs | The update for this issue may be included in a future update rollup | Deployment | | Installing without user intervention | Windows 2000 Service Pack 4:
Windows2000-KB921503-x86-enu /quiet | Installing without restarting | Windows 2000 Service Pack 4:
Windows2000-KB921503-x86-enu /norestart | Update log file | Windows 2000 Service Pack 4:
KB921503.log | Further information | See the subsection, Detection and Deployment Tools and Guidance | Restart Requirement | | Restart required | Yes, you must restart your system after you apply this security update | Hotpatching | Not applicable | Removal Information | Windows 2000 Service Pack 4:
Use
Add or Remove Programs tool in Control Panel or the Spuninst.exe
utility located in the %Windir%\$NTUninstallKB921503$\Spuninst folder | File Information | See the heading, File Information, below for the full file manifest | Registry Key Verification | For Windows 2000 Service Pack 4:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows 2000\SP5\KB921503\Filelist |
| |
The
English version of this security update has the file attributes that
are listed in the following table. The dates and times for these files
are listed in coordinated universal time (UTC). When you view the file
information, it is converted to local time. To find the difference
between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel. For all supported editions of Windows 2000: Oleaut32.dll | 2.40.4531.0 | 11-Jul-2006 | 19:49 | 631,056 |
Note For a complete list of supported editions, see the Support Lifecycle Index. For a complete list of service packs, see Lifecycle Supported Service Packs. For more information on the support lifecycle policy, see Microsoft Support Lifecycle. | |
Installing the Update When
you install this security update, the installer checks to see if one or
more of the files that are being updated on your system have previously
been updated by a Microsoft hotfix. For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684. This security update supports the following setup switches. |
/help | Displays the command-line options | /passive | Unattended
Setup mode. No user interaction is required, but installation status is
displayed. If a restart is required at the end of Setup, a dialog box
will be presented to the user with a timer warning that the computer
will restart in 30 seconds. | /quiet | Quiet mode. This is the same as unattended mode, but no status or error messages are displayed. | /norestart | Does not restart when installation has completed | /forcerestart | Restarts the computer after installation and force other applications to close at shutdown without saving open files first. | /warnrestart[:x] | Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch. | /promptrestart | Display a dialog box prompting the local user to allow a restart | /overwriteoem | Overwrites OEM files without prompting | /nobackup | Does not back up files needed for uninstall | /forceappsclose | Forces other programs to close when the computer shuts down | /log:path | Allows the redirection of installation log files | /extract[:path] | Extracts files without starting the Setup program | /ER | Enables extended error reporting | /verbose | Enables
verbose logging. During installation, creates %Windir%\CabBuild.log.
This log details the files that are copied. Using this switch may cause
the installation to proceed more slowly. |
Note You
can combine these switches into one command. For backward
compatibility, the security update also supports the setup switches
that the earlier version of the Setup program uses. For more
information about the supported installation switches, see Microsoft Knowledge Base Article 262841. For more information about the Update.exe installer, visit the Microsoft TechNet Web site. Removing the Update This security update supports the following setup switches. |
/help | Displays the command-line options | /passive | Unattended
Setup mode. No user interaction is required, but installation status is
displayed. If a restart is required at the end of Setup, a dialog box
will be presented to the user with a timer warning that the computer
will restart in 30 seconds. | /quiet | Quiet mode. This is the same as unattended mode, but no status or error messages are displayed. | /norestart | Does not restart when installation has completed | /forcerestart | Restarts the computer after installation and force other applications to close at shutdown without saving open files first. | /warnrestart[:x] | Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch. | /promptrestart | Display a dialog box prompting the local user to allow a restart | /forceappsclose | Forces other programs to close when the computer shuts down | /log:path | Allows 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 versions of Microsoft Windows, the following steps
may be different on your computer. If they are, see your product
documentation to complete these steps. 1. | Click Start, and then click Search. | 2. | In the Search Results pane, click All files and folders under Search Companion. | 3. | In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search. | 4. | In the list of files, right-click a file name from the appropriate file information table, and then click Properties. |
Note
Depending on the version of the operating system or programs installed,
some of the files that are listed in the file information table may not
be installed. |
| • | Version
tab, determine the version of the file that is installed on your
computer by comparing it to the version that is documented in the
appropriate file information table. Note Attributes other
than the file version may change during installation. Comparing other
file attributes to the information in the file information table is not
a supported method of verifying that the update has been applied. Also,
in certain cases, files may be renamed during installation. If the file
or version information is not present, use one of the other available
methods to verify update installation. | | • | Registry Key Verification You may also be able to verify the files that this security update has installed by reviewing the registry keys listed in the Reference Table in this section. These
registry keys may not contain a complete list of installed files. Also,
these registry keys may not be created correctly when an administrator
or an OEM integrates or slipstreams this security update into the
Windows installation source files. |
| |
Reference Table The
following table contains the security update information for this
software. You can find additional information in the subsection, Deployment Information, in this section. Inclusion in Future Service Packs | The update for this issue will be included in a future service pack or update rollup | Deployment | | Installing without user intervention | Windows XP Service Pack 2:
WindowsXP-KB921503-x86-enu /quiet | | Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2:
WindowsServer2003.WindowsXP-KB921503-x64-enu /quiet | Installing without restarting | Windows XP Service Pack 2:
WindowsXP-KB921503-x86-enu /norestart | | Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2:
WindowsServer2003.WindowsXP-KB921503-x64-enu /norestart | Update log file | KB921503.log | Further information | See the subsection, Detection and Deployment Tools and Guidance | Restart Requirement | | Restart required | Yes, you must restart your system after you apply this security update | Hotpatching | Not applicable | Removal Information | Use
Add or Remove Programs tool in Control Panel or the Spuninst.exe
utility located in the %Windir%\$NTUninstallKB921503$\Spuninst folder | File Information | See the heading, File Information, below for the full file manifest | Registry Key Verification | For all supported 32-bit editions of Windows XP:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP\SP3\KB921503\Filelist | | For all supported x64 editions of Windows XP:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP Version 2003\SP3\KB921503\Filelist |
| |
The
English version of this security update has the file attributes that
are listed in the following table. The dates and times for these files
are listed in coordinated universal time (UTC). When you view the file
information, it is converted to local time. To find the difference
between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel. For all supported 32-bit editions of Windows XP: Oleaut32.dll | 5.1.2600.3139 | 17-May-2007 | 11:28 | 549,376 | SP2GDR | Oleaut32.dll | 5.1.2600.3139 | 17-May-2007 | 11:25 | 549,888 | SP2QFE |
For all supported editions of Windows XP Professional x64: Oleaut32.dll | 5.2.3790.2955 | 13-Jun-2007 | 20:27 | 1,114,624 | X64 | SP1GDR | Woleaut32.dll | 5.2.3790.2955 | 13-Jun-2007 | 20:27 | 556,544 | X86 | SP1GDR\wow | Oleaut32.dll | 5.2.3790.2955 | 13-Jun-2007 | 20:27 | 1,115,136 | X64 | SP1QFE | Woleaut32.dll | 5.2.3790.2955 | 13-Jun-2007 | 20:27 | 557,056 | X86 | SP1QFE\wow | Oleaut32.dll | 5.2.3790.4098 | 13-Jun-2007 | 20:29 | 1,121,280 | X64 | SP2GDR | Woleaut32.dll | 5.2.3790.4098 | 13-Jun-2007 | 20:29 | 552,960 | X86 | SP2GDR\wow | Oleaut32.dll | 5.2.3790.4098 | 13-Jun-2007 | 20:26 | 1,121,280 | X64 | SP2QFE | Woleaut32.dll | 5.2.3790.4098 | 13-Jun-2007 | 20:26 | 552,960 | X86 | SP2QFE\wow |
Note For a complete list of supported editions, see the Support Lifecycle Index. For a complete list of service packs, see Lifecycle Supported Service Packs. For more information on the support lifecycle policy, see Microsoft Support Lifecycle. | |
Installing the Update When
you install this security update, the installer checks to see if one or
more of the files that are being updated on your system have previously
been updated by a Microsoft hotfix. For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684. This security update supports the following setup switches. |
/help | Displays the command-line options | /passive | Unattended
Setup mode. No user interaction is required, but installation status is
displayed. If a restart is required at the end of Setup, a dialog box
will be presented to the user with a timer warning that the computer
will restart in 30 seconds. | /quiet | Quiet mode. This is the same as unattended mode, but no status or error messages are displayed. | /norestart | Does not restart when installation has completed | /forcerestart | Restarts the computer after installation and force other applications to close at shutdown without saving open files first. | /warnrestart[:x] | Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch. | /promptrestart | Display a dialog box prompting the local user to allow a restart | /overwriteoem | Overwrites OEM files without prompting | /nobackup | Does not back up files needed for uninstall | /forceappsclose | Forces other programs to close when the computer shuts down | /log:path | Allows the redirection of installation log files | /integrate:path | Integrates the update into the Windows source files. These files are located at the path that is specified in the switch. | /extract[:path] | Extracts files without starting the Setup program | /ER | Enables extended error reporting | /verbose | Enables
verbose logging. During installation, creates %Windir%\CabBuild.log.
This log details the files that are copied. Using this switch may cause
the installation to proceed more slowly. |
Note You
can combine these switches into one command. For backward
compatibility, the security update also supports the setup switches
that the earlier version of the Setup program uses. For more
information about the supported installation switches, see Microsoft Knowledge Base Article 262841. For more information about the Update.exe installer, visit the Microsoft TechNet Web site. Removing the Update This security update supports the following setup switches. |
/help | Displays the command-line options | /passive | Unattended
Setup mode. No user interaction is required, but installation status is
displayed. If a restart is required at the end of Setup, a dialog box
will be presented to the user with a timer warning that the computer
will restart in 30 seconds. | /quiet | Quiet mode. This is the same as unattended mode, but no status or error messages are displayed. | /norestart | Does not restart when installation has completed | /forcerestart | Restarts the computer after installation and force other applications to close at shutdown without saving open files first. | /warnrestart[:x] | Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch. | /promptrestart | Display a dialog box prompting the local user to allow a restart | /forceappsclose | Forces other programs to close when the computer shuts down | /log:path | Allows 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 versions of Microsoft Windows, the following steps
may be different on your computer. If they are, see your product
documentation to complete these steps. 1. | Click Start, and then click Search. | 2. | In the Search Results pane, click All files and folders under Search Companion. | 3. | In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search. | 4. | In the list of files, right-click a file name from the appropriate file information table, and then click Properties. |
Note
Depending on the version of the operating system or programs installed,
some of the files that are listed in the file information table may not
be installed. |
| • | Version
tab, determine the version of the file that is installed on your
computer by comparing it to the version that is documented in the
appropriate file information table. Note Attributes other
than the file version may change during installation. Comparing other
file attributes to the information in the file information table is not
a supported method of verifying that the update has been applied. Also,
in certain cases, files may be renamed during installation. If the file
or version information is not present, use one of the other available
methods to verify update installation. | | • | Registry Key Verification You may also be able to verify the files that this security update has installed by reviewing the registry keys listed in the Reference Table in this section. These
registry keys may not contain a complete list of installed files. Also,
these registry keys may not be created correctly when an administrator
or an OEM integrates or slipstreams this security update into the
Windows installation source files. |
| |
Reference Table The
following table contains the security update information for this
software. You can find additional information in the subsection, Deployment Information, in this section. Inclusion in Future Service Packs | The update for this issue will be included in a future service pack or update rollup | Deployment | | Installing without user intervention | Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2:
WindowsServer2003-KB921503-x86-enu /quiet | | Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2:
WindowsServer2003.WindowsXP-KB921503-x64-enu /quiet | | Windows Server 2003 with SP1 for Itanium-based Systems and Windows Server 2003 with SP2 for Itanium-based Systems:
WindowsServer2003-KB921503-ia64-enu /quiet | Installing without restarting | Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2:
WindowsServer2003-KB921503-x86-enu /norestart | | Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2:
WindowsServer2003.WindowsXP-KB921503-x64-enu /norestart | | Windows Server 2003 with SP1 for Itanium-based Systems and Windows Server 2003 with SP2 for Itanium-based Systems:
WindowsServer2003-KB921503-ia64-enu /quiet | Update log file | KB921503.log | Further information | See the subsection, Detection and Deployment Tools and Guidance | Restart Requirement | | Restart required | Yes, you must restart your system after you apply this security update | Hotpatching | This security update does not support HotPatching. For more information about HotPatching see Microsoft Knowledge Base Article 897341. | Removal Information | Windows Server 2003, Windows Server 2003 Service Pack 1, and Windows Server 2003 Service Pack 2:
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%\$NTUninstallKB921503$\Spuninst folder | File Information | See the heading, File Information, below for the full file manifest | Registry Key Verification | For
all supported 32-bit editions, Itanium-based versions, and x64-based
versions of Windows Server 2003, Windows Server 2003 Service Pack 1,
and Windows Server 2003 Service Pack 2:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB921503\Filelist |
| |
The
English version of this security update has the file attributes that
are listed in the following table. The dates and times for these files
are listed in coordinated universal time (UTC). When you view the file
information, it is converted to local time. To find the difference
between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel. For all supported 32-bit versions of Windows Server 2003: Oleaut32.dll | 5.2.3790.2955 | 13-Jun-2007 | 19:17 | 556,544 | SP1GDR | Oleaut32.dll | 5.2.3790.2955 | 13-Jun-2007 | 19:02 | 557,056 | SP1QFE | Oleaut32.dll | 5.2.3790.4098 | 13-Jun-2007 | 19:26 | 552,960 | SP2GDR | Oleaut32.dll | 5.2.3790.4098 | 13-Jun-2007 | 19:47 | 552,960 | SP2QFE |
For all supported versions of Windows Server 2003 x64: Oleaut32.dll | 5.2.3790.2955 | 13-Jun-2007 | 20:27 | 1,114,624 | X64 | SP1GDR | Woleaut32.dll | 5.2.3790.2955 | 13-Jun-2007 | 20:27 | 556,544 | X86 | SP1GDR\wow | Oleaut32.dll | 5.2.3790.2955 | 13-Jun-2007 | 20:27 | 1,115,136 | X64 | SP1QFE | Woleaut32.dll | 5.2.3790.2955 | 13-Jun-2007 | 20:27 | 557,056 | X86 | SP1QFE\wow | Oleaut32.dll | 5.2.3790.4098 | 13-Jun-2007 | 20:29 | 1,121,280 | X64 | SP2GDR | Woleaut32.dll | 5.2.3790.4098 | 13-Jun-2007 | 20:29 | 552,960 | X86 | SP2GDR\wow | Oleaut32.dll | 5.2.3790.4098 | 13-Jun-2007 | 20:26 | 1,121,280 | X64 | SP2QFE | Woleaut32.dll | 5.2.3790.4098 | 13-Jun-2007 | 20:26 | 552,960 | X86 | SP2QFE\wow |
For all supported versions of Windows Server 2003 for Itanium-based Systems: Oleaut32.dll | 5.2.3790.2955 | 13-Jun-2007 | 20:25 | 3,933,696 | IA-64 | SP1GDR | Woleaut32.dll | 5.2.3790.2955 | 13-Jun-2007 | 20:25 | 556,544 | X86 | SP1GDR\wow | Oleaut32.dll | 5.2.3790.2955 | 13-Jun-2007 | 20:25 | 3,935,232 | IA-64 | SP1QFE | Woleaut32.dll | 5.2.3790.2955 | 13-Jun-2007 | 20:25 | 557,056 | X86 | SP1QFE\wow | Oleaut32.dll | 5.2.3790.4098 | 13-Jun-2007 | 20:30 | 3,941,888 | IA-64 | SP2GDR | Woleaut32.dll | 5.2.3790.4098 | 13-Jun-2007 | 20:30 | 552,960 | X86 | SP2GDR\wow | Oleaut32.dll | 5.2.3790.4098 | 13-Jun-2007 | 20:25 | 3,941,888 | IA-64 | SP2QFE | Woleaut32.dll | 5.2.3790.4098 | 13-Jun-2007 | 20:25 | 552,960 | X86 | SP2QFE\wow |
Note For a complete list of supported versions, see the Support Lifecycle Index. For a complete list of service packs, see Lifecycle Supported Service Packs. For more information on the support lifecycle policy, see Microsoft Support Lifecycle. | |
Installing the Update When
you install this security update, the installer checks to see if one or
more of the files that are being updated on your system have previously
been updated by a Microsoft hotfix. For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684. This security update supports the following setup switches. |
/help | Displays the command-line options | /passive | Unattended
Setup mode. No user interaction is required, but installation status is
displayed. If a restart is required at the end of Setup, a dialog box
will be presented to the user with a timer warning that the computer
will restart in 30 seconds. | /quiet | Quiet mode. This is the same as unattended mode, but no status or error messages are displayed. | /norestart | Does not restart when installation has completed | /forcerestart | Restarts the computer after installation and force other applications to close at shutdown without saving open files first. | /warnrestart[:x] | Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch. | /promptrestart | Display a dialog box prompting the local user to allow a restart | /overwriteoem | Overwrites OEM files without prompting | /nobackup | Does not back up files needed for uninstall | /forceappsclose | Forces other programs to close when the computer shuts down | /log:path | Allows the redirection of installation log files | /integrate:path | Integrates the update into the Windows source files. These files are located at the path that is specified in the switch. | /extract[:path] | Extracts files without starting the Setup program | /ER | Enables extended error reporting | /verbose | Enables
verbose logging. During installation, creates %Windir%\CabBuild.log.
This log details the files that are copied. Using this switch may cause
the installation to proceed more slowly. |
Note You
can combine these switches into one command. For backward
compatibility, the security update also supports 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. Removing the Update This security update supports the following setup switches. |
/help | Displays the command-line options | /passive | Unattended
Setup mode. No user interaction is required, but installation status is
displayed. If a restart is required at the end of Setup, a dialog box
will be presented to the user with a timer warning that the computer
will restart in 30 seconds. | /quiet | Quiet mode. This is the same as unattended mode, but no status or error messages are displayed. | /norestart | Does not restart when installation has completed | /forcerestart | Restarts the computer after installation and force other applications to close at shutdown without saving open files first. | /warnrestart[:x] | Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch. | /promptrestart | Display a dialog box prompting the local user to allow a restart | /forceappsclose | Forces other programs to close when the computer shuts down | /log:path | Allows 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 versions of Microsoft Windows, the following steps
may be different on your computer. If they are, see your product
documentation to complete these steps. 1. | Click Start, and then click Search. | 2. | In the Search Results pane, click All files and folders under Search Companion. | 3. | In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search. | 4. | In the list of files, right-click a file name from the appropriate file information table, and then click Properties. |
Note
Depending on the version of the operating system or programs installed,
some of the files that are listed in the file information table may not
be installed. |
| • | Version
tab, determine the version of the file that is installed on your
computer by comparing it to the version that is documented in the
appropriate file information table. Note Attributes other
than the file version may change during installation. Comparing other
file attributes to the information in the file information table is not
a supported method of verifying that the update has been applied. Also,
in certain cases, files may be renamed during installation. If the file
or version information is not present, use one of the other available
methods to verify update installation. | | • | Registry Key Verification You may also be able to verify the files that this security update has installed by reviewing the registry keys listed in the Reference Table in this section. These
registry keys may not contain a complete list of installed files. Also,
these registry keys may not be created correctly when an administrator
or an OEM integrates or slipstreams this security update into the
Windows installation source files. |
| |
Prerequisites | • | The must be installed on your computer. | | • | Mac
OS X 10.2.8 or a later version of Mac OS on 700 MHz native PowerPC G3,
G4, or G5 processor (Intel processors are not supported) | | • | 70
MB of available hard disk space is temporarily required to complete
installation; after installation, the program requires 50 MB of hard
disk space. | | • | Mac OS X user accounts must have administrator privileges to install this security update. |
Installing the Update Download and install the appropriate language version of the Microsoft Office 2004 for Mac 11.3.7 Update from the . Removing the Update This security update cannot be uninstalled. Additional Information If you have technical questions or problems downloading or using this update, visit the Microsoft for Mac Support to learn about the support options that are available to you. | |
Reference Table Inclusion in Future Service Packs | The update for this issue will be included in a future service pack or update rollup | Deployment | | Installing without user intervention | Visual Basic 6.0:
VB6-KB924053-x86-enu /q:a | Installing without restarting | Visual Basic 6.0:
VB6-KB924053-x86-enu /r:n | Update log file | Not applicable | Further information | See the subsection, Detection and Deployment Tools and Guidance | Restart Requirement | | Restart required | No, you do not need to restart your system after you apply this security update | Removal Information | This update cannot be removed | File Information | See the heading, File Information, below for the full file manifest | Registry Key Verification | Not applicable |
| |
The
English version of this security update has the file attributes that
are listed in the following table. The dates and times for these files
are listed in coordinated universal time (UTC). When you view the file
information, it is converted to local time. To find the difference
between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel. For all supported versions of Microsoft Visual Basic 6.0: Oleaut32.dll | 2.40.4519.0 | 31-Jul-2006 | 18:12 | 626,960 | Oleaut32.dll | 2.40.4519.0 | 31-Jul-2006 | 18:44 | 626,960 | Oleaut32.dll | 2.40.4531.0 | 11-Jul-2006 | 19:49 | 631,056 | Oleaut32.dll | 5.2.3790.569 | 28-Jul-2006 | 11:38 | 497,664 | Oleaut32.dll | 5.2.3790.2759 | 28-Jul-2006 | 12:05 | 556,544 | Oleaut32.dll | 5.1.2600.2958 | 22-Jul-2006 | 14:44 | 549,376 |
Note For a complete list of supported versions, see the Support Lifecycle Index. For a complete list of service packs, see Lifecycle Supported Service Packs. For more information on the support lifecycle policy, see Microsoft Support Lifecycle. | |
Installing the Update When
you install this security update, the installer checks to see if one or
more of the files that are being updated on your system have previously
been updated by a Microsoft hotfix. For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684. This security update supports the following setup switches. |
/? | Displays the command-line options. | /q [:u | :a] | /q - Specifies quiet mode, or suppresses prompts. /q:u - Specifies user-quiet mode, which presents some dialog boxes to the user. /q:a - Specifies administrator-quiet mode, which does not present any dialog boxes to the user. | /C | Extracts the files without installing them. If /t: path is not specified, you are prompted for a target folder. | /T:path | Specifies the target folder for extracting files. | /C:path | Specifies the UNC path and name of the Setup.inf or .exe file. | /n:v | No version checking. Install the package over any previous version. | /r:n | Never restarts the system after installation. | /r:i | Prompts the user to restart the system if a restart is required, except when used with /q:a. | /r:a | Always restarts the system after installation. | /r:s | Restarts the computer after installation without prompting the user. |
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 197147. Verifying that the Update Has Been Applied | • | Microsoft Baseline Security Analyzer To
verify that a security update has been applied to an affected system,
you may be able to use the Microsoft Baseline Security Analyzer (MBSA)
tool. See the section, Detection and Deployment Tools and Guidance,
earlier in this bulletin for more information. | | • | File Version Verification Because
there are several versions of Microsoft Windows, the following steps
may be different on your computer. If they are, see your product
documentation to complete these steps. 1. | Click Start, and then click Search. | 2. | In the Search Results pane, click All files and folders under Search Companion. | 3. | In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search. | 4. | In the list of files, right-click a file name from the appropriate file information table, and then click Properties.
Note
Depending on the version of the operating system or programs installed,
some of the files that are listed in the file information table may not
be installed. | 5. | On the Version
tab, determine the version of the file that is installed on your
computer by comparing it to the version that is documented in the
appropriate file information table.
Note Attributes other
than the file version may change during installation. Comparing other
file attributes to the information in the file information table is not
a supported method of verifying that the update has been applied. Also,
in certain cases, files may be renamed during installation. If the file
or version information is not present, use one of the other available
methods to verify update installation. |
|
AcknowledgmentsMicrosoft thanks the following for working with us to help protect customers: | • | An anonymous researcher working with the VeriSign iDefense VCP for reporting the OLE Automation Memory Corruption Vulnerability (CVE-2007-2224). | | • | An anonymous researcher working with the Zero Day Initiative for reporting the OLE Automation Memory Corruption Vulnerability (CVE-2007-2224). |
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. |
DisclaimerThe
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. |
|
