[SECURITY-L] CAIS-Alerta: Vulnerabilidade no HTML Help (840315)
CSIRT - UNICAMP
security em unicamp.br
Qua Jul 14 10:42:22 -03 2004
----- Forwarded message from Centro de Atendimento a Incidentes de Seguranca <cais em cais.rnp.br> -----
From: Centro de Atendimento a Incidentes de Seguranca <cais em cais.rnp.br>
Subject: CAIS-Alerta: Vulnerabilidade no HTML Help (840315)
To: rnp-alerta em cais.rnp.br, rnp-seg em cais.rnp.br
Date: Tue, 13 Jul 2004 19:26:59 -0300 (BRST)
-----BEGIN PGP SIGNED MESSAGE-----
Prezados,
O CAIS esta' repassando o alerta da Microsoft intitulado "Microsoft
Security Bulletin MS04-023: Vulnerability in HTML Help Could Allow Code
Execution (840315)", que trata da correcao de duas vulnerabilidades que
afetam o HTML Help.
Microsoft HTML Help e' o sistema on-line de ajuda padrao da plataforma
Windows. A vulnerabilidade descrita em CAN-2003-1041 esta no processamento
de uma URL showHelp criada por um atacante que permite a execucao de
codigo malicioso na Zona Local do Internet Explorer, considerada
confiavel. Ja' a vulnerabilidade descrita em CAN-2004-0201 esta' na
validacao dos dados de entrada no HTML Help, permitindo execucao remota de
codigo por um atacante contra usuarios com privilegios administrativos. A
exploracao de ambas as vulnerabilidades resulta em total controle do
atacante sob o sistema comprometido.
Sistemas afetados:
. Microsoft Windows 2000 Service Pack 2
. Microsoft Windows 2000 Service Pack 3
. Microsoft Windows 2000 Service Pack 4
. Microsoft Windows XP
. Microsoft Windows XP Service Pack 1
. Microsoft Windows XP 64-Bit Edition Service Pack 1
. Microsoft Windows XP 64-Bit Edition Version 2003
. Microsoft Windows Server 2003
. Microsoft Windows Server 2003 64-Bit Edition
. Microsoft Windows 98
. Microsoft Windows 98 Second Edition (SE)
. Microsoft Windows Millennium Edition (Me)
Correcoes disponiveis:
Recomenda-se fazer a atualizacao para as versoes disponiveis em:
. Microsoft Windows 2000 Service Pack 2, 3 e 4
http://www.microsoft.com/downloads/details.aspx?FamilyId=3F2F1A7D-5CF2-4791-A7EE-07F20F75796C&displaylang=en
. Microsoft Windows XP and Microsoft Windows XP Service Pack 1
http://www.microsoft.com/downloads/details.aspx?FamilyId=8B412C7F-44AD-4E77-8973-FD3E84CC496A&displaylang=en
. Microsoft Windows XP 64-Bit Edition Service Pack 1
http://www.microsoft.com/downloads/details.aspx?FamilyId=0042DB67-C58B-412C-A24F-9D2AA8071897&displaylang=en
. Microsoft Windows XP 64-Bit Edition Version 2003
http://www.microsoft.com/downloads/details.aspx?FamilyId=DF0C5C4E-D986-4AD5-95E0-E87106D7C019&displaylang=en
. Microsoft Windows Server 2003
http://www.microsoft.com/downloads/details.aspx?FamilyId=8B53C35D-E9ED-46AD-936C-30C8E3A7E606&displaylang=en
. Microsoft Windows Server 2003 64-Bit Edition
http://www.microsoft.com/downloads/details.aspx?FamilyId=DF0C5C4E-D986-4AD5-95E0-E87106D7C019&displaylang=en
. Microsoft Windows 98, 98 Second Edition (SE) e Millennium Edition (Me) -
consultar o FAQ do boletim original
Mais informacoes:
. Microsoft Security Bulletin MS04-023
Vulnerability in HTML Help Could Allow Code Execution (840315)
http://www.microsoft.com/technet/security/bulletin/MS04-023.mspx
. Microsoft Brasil - Security
http://www.microsoft.com/brasil/security
. Technet Brasil - Central de Seguranca
http://www.technetbrasil.com.br/seguranca
Identificadores CVE: CAN-2004-0201 e CAN-2003-1041 (http://cve.mitre.org)
O CAIS recomenda aos administradores de plataformas Microsoft que
mantenham seus sistemas e aplicativos sempre atualizados.
Os Alertas do CAIS tambem sao oferecidos no formato RSS/RDF:
http://www.rnp.br/cais/alertas/rss.xml
Atenciosamente,
################################################################
# CENTRO DE ATENDIMENTO A INCIDENTES DE SEGURANCA (CAIS) #
# Rede Nacional de Ensino e Pesquisa (RNP) #
# #
# cais em cais.rnp.br http://www.cais.rnp.br #
# Tel. 019-37873300 Fax. 019-37873301 #
# Chave PGP disponivel http://www.rnp.br/cais/cais-pgp.key #
################################################################
Microsoft Security Bulletin MS04-023
Vulnerability in HTML Help Could Allow Code Execution (840315)
Issued: July 13, 2004
Version: 1.0
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: Windows NT Workstation 4.0, Windows NT Server 4.0 and Windows NT
4.0 Terminal Server Edition are not affected by default. However if you
have installed Internet Explorer 5.5 Service Pack 2 or Internet Explorer
6.0 Service Pack 1 you will have the vulnerable component on your system.
Tested Software and Security Update Download Locations:
Affected Software:
Microsoft Windows 2000 Service Pack 2, Microsoft Windows 2000 Service Pack
3, Microsoft Windows 2000 Service Pack 4 Download the update
Microsoft Windows XP and Microsoft Windows XP Service Pack 1 Download
the update
Microsoft Windows XP 64-Bit Edition Service Pack 1 Download the update
Microsoft Windows XP 64-Bit Edition Version 2003 Download the update
Microsoft Windows Server 2003 Download the update
Microsoft Windows Server 2003 64-Bit Edition Download the update
Microsoft Windows 98, Microsoft Windows 98 Second Edition (SE), and
Microsoft Windows Millennium Edition (Me) Review the FAQ section of this
bulletin for details about these operating systems.
Non-Affected Software:
Microsoft Windows NT® Workstation 4.0 Service Pack 6a
Microsoft Windows NT Server 4.0 Service Pack 6a
Microsoft Windows NT Server 4.0 Terminal Server Edition Service Pack 6
Tested Microsoft Windows Components:
Affected Components:
Internet Explorer 6.0 Service Pack 1 when installed on Windows NT 4.0 SP6a
(Workstation, Server, or Terminal Server Edition) - Download the update
The software in this list has been tested to determine if the versions are
affected. Other versions either no longer include security update support
or may not be affected. To determine the support lifecycle for your
product and version, visit the following Microsoft Support Lifecycle Web
site.
Top of section
General Information
Executive Summary
Executive Summary:
This update resolves two newly-discovered vulnerabilities. The HTML Help
vulnerability was privately reported and the showHelp vulnerability is
public. Each vulnerability is documented in this bulletin in its own
Vulnerability Details section.
If a user is logged on with administrative privileges, an attacker who
successfully exploited the most severe of these vulnerabilities could take
complete control of an affected system, including installing programs;
viewing, changing, or deleting data; or creating new accounts that have
full privileges. Users whose accounts are configured to have fewer
privileges on the system would be at less risk than users who operate with
administrative privileges.
We recommend that customers apply the update immediately.
Severity Ratings and Vulnerability Identifiers:
Vulnerability Identifiers Impact of Vulnerability Windows 98, 98 SE,
Me Windows NT 4.0 Windows 2000 Windows XP Windows Server
2003
showHelp Vulnerability - CAN-2003-1041
Remote Code Execution
Not Critical
Important
Important
Important
Important
HTML Help Vulnerability - CAN-2004-0201
Remote Code Execution
Critical
Critical
Critical
Critical
Critical
Aggregate Severity of All Vulnerabilities
Critical
Critical
Critical
Critical
Critical
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.
Top of section
Frequently asked questions (FAQ) related to this security update
Does this update contain any other changes?
Yes. In addition to the changes that are listed in the Vulnerability
Details section of this bulletin, this update includes the following
change. After applying this update only files that have the extension
".chm" can be used as compiled HTML Help files. Applications that use
other extensions for compiled HTML Help files will no longer display
content using HTML Help. For more information, see Knowledge Base article
840315.
I'm still using Microsoft Windows NT 4.0 Workstation Service Pack 6a or
Windows 2000 Service Pack 2, but extended security update support ended on
June 30, 2004. However, this bulletin has a security update for these
operating system versions. Why is that?
Windows NT 4.0 Workstation Service Pack 6a and Windows 2000 Service Pack 2
have reached the end of their life cycles as previously documented, and
Microsoft extended this support to June 30, 2004. However, the end-of-life
for the extended support period occurred very recently. In this case, the
majority of the steps that are required to address this vulnerability were
completed before June 30, 2004. Therefore, we have decided to release
security updates for these operating system versions as part of this
security bulletin. We do not anticipate doing this for future
vulnerabilities affecting these operating system versions, but we reserve
the right to produce updates and to make these updates available when
necessary.
It should be a priority for customers who have these operating system
versions to migrate to supported versions to prevent potential exposure to
future vulnerabilities. For more information about the Windows Product
Life Cycle, 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 following Microsoft Product
Support Services Web site.
Customers who require additional support for Windows NT Workstation 4.0
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 phone numbers. When
you call, ask to speak with the local Premier Support sales manager.
For more information, see the Windows Operating System FAQ.
Why does this update address several reported security vulnerabilities?
This update contains support for several vulnerabilities because the
modifications that are required to address these issues are located in the
same file. Instead of having to install several updates that are almost
the same, customers can install only this update.
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 platforms may not be available
concurrently with the other security updates provided as part of 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 any of the vulnerabilities that are addressed in
this security bulletin?
Yes. Security updates 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.
Is Windows NT 4.0 Service Pack 6a affected by the vulnerability that is
addressed in this security bulletin?
By default, this operating system does not natively provide a version of
the vulnerable component and is not affected. However, the vulnerable
component is installed on this operating system when you install Internet
Explorer 5.5 Service Pack 2 or Internet Explorer 6 Service Pack 1. If you
use this version of Internet Explorer on this operating system, you should
install the provided security update for Windows NT 4.0.
Can I use the Microsoft Baseline Security Analyzer (MBSA) to determine if
this update is required?
Yes. MBSA will determine if this update is required. For more information
about MBSA, visit the MBSA Web site.
Note After April 20, 2004, the Mssecure.xml file that is used by MBSA
1.1.1 and earlier versions is no longer being updated with new security
bulletin data. Therefore, scans that are performed after that date with
MBSA 1.1.1 or earlier will be incomplete. All users should upgrade to MBSA
1.2 because it provides more accurate security update detection and
supports additional products. Users can download MBSA 1.2 from the MBSA
Web site. For more information about MBSA support, visit the following
Microsoft Baseline Security Analyzer 1.2 Q&A Web site.
Can I use Systems Management Server (SMS) to determine if this update is
required?
Yes. SMS can help detect and deploy this security update. For information
about SMS, visit the SMS Web site
Top of section
Vulnerability Details
showHelp Vulnerability - CAN-2003-1041:
A remote code execution vulnerability exists in the processing of a
specially crafted showHelp URL. The vulnerability could allow malicious
code to run in the Local Machine security zone in Internet Explorer, which
could allow an attacker to take complete control of an affected system.
Mitigating Factors for showHelp Vulnerability - CAN-2003-1041:
To exploit this vulnerability an attacker would have to use a specially
crafted file that is at a known location on the target system.
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 site. After they click the link, they would be prompted to
perform several actions. An attack could only occur after they performed
these actions.
An attacker who successfully exploited this vulnerability could gain the
same privileges as the user. Users whose accounts are configured to have
fewer privileges on the system would be at less risk than users who
operate with administrative privileges.
By default, Outlook Express 6, Outlook 2002, and Outlook 2003 open HTML
e-mail messages in the Restricted sites zone. Additionally, Outlook 98 and
Outlook 2000 open HTML e-mail messages in the Restricted sites zone if the
Outlook E-mail Security Update has been installed. The Restricted sites
zone helps reduce attacks that could attempt to exploit this
vulnerability.
The risk of attack from the HTML e-mail vector can be significantly
reduced if you meet all the following conditions:
Apply the update that is included with Microsoft Security Bulletin
MS03-040 or a later Cumulative Security Update for Internet Explorer.
Use Internet Explorer 6 or later.
Use the Microsoft Outlook E-mail Security Update, use Microsoft Outlook
Express 6 or later, or use Microsoft Outlook 2000 Service Pack 2 or later
in its default configuration.
Top of section
Workarounds for showHelp Vulnerability - CAN-2003-1041:
Microsoft has tested the following workarounds. While these workarounds
will not correct the underlying vulnerability, they help block known
attack vectors. When a workaround reduces functionality, it is identified
below.
Strengthen the security settings for the Local Machine zone in Internet
Explorer
Because this vulnerability permits an attacker to run HTML code in the
Local Machine security zone, users can reduce the impact of this
vulnerability by restricting the default settings in this zone. For more
information about these settings, and for more information about the
potential impacts of changing these default settings, see Microsoft
Knowledge Base Article 833633.
Warning: Microsoft recommends that customers consider these changes to
Internet Explorer security settings as a last resort only. If you make
these changes, you may lose some functionality for some Windows programs
and components. Before you make these changes in a production environment,
test the changes extensively to verify that mission-critical programs
continue to work correctly for all users.
~U
Unregister HTML Help
To unregister the HTML Help protocol, follow these steps:
1.
Click Start, click Run, type "regsvr32 /u %windir%\system32\itss.dll"
(without the quotation marks), and then click OK.
Note On Windows 98 and Windows Me, replace "system32" with "system" in
this command.
2.
A dialog box appears to confirm that the unregistration process has
succeeded. Click OK to close the dialog box.
Impact of Workaround: All HTML Help functionality will be unavailable.
This will affect the online Help in Windows or any application that uses
HTML Help functionality.
Read e-mail messages in plain text format if you are using Outlook 2002 or
later, or Outlook Express 6 SP1 or later, to help protect yourself from
the HTML e-mail attack vector.
Microsoft Outlook 2002 users who have applied Office XP Service Pack 1 or
later and Microsoft Outlook Express 6 users who have applied Internet
Explorer 6 Service Pack 1 can enable this setting and view e-mail messages
that are not digitally signed or e-mail messages that are not encrypted in
plain text only.
Digitally signed e-mail messages or encrypted e-mail messages are not
affected by the setting and may be read in their original formats. For
more information about enabling this setting in Outlook 2002, see
Microsoft Knowledge Base Article 307594.
For information about this setting in Outlook Express 6, see Microsoft
Knowledge Base Article 291387.
Impact of Workaround: E-mail messages that are viewed in plain text format
will not contain pictures, specialized fonts, animations, or other rich
content. In addition:
The changes are applied to the preview pane and to open messages.
Pictures become attachments so that they are not lost.
Because the message is still in Rich Text or HTML format in the store, the
object model (custom code solutions) may behave unexpectedly.
Top of section
FAQ for showHelp Vulnerability - CAN-2003-1041:
What is the scope of the vulnerability?
This is a remote code execution vulnerability. If a user is logged on with
administrative privileges, an attacker who successfully exploited this
vulnerability could take complete control of an affected system. An
attacker could then install programs; viewing, changing, or deleting data;
or creating new accounts with full privileges. Users whose accounts are
configured to have fewer privileges on the system would be at less risk
than users who operate with administrative privileges. In order to exploit
this vulnerability an attacker would have to make use of a specially
crafted file that is at a known location on the target system.
What causes the vulnerability?
The HTML Help protocol does not correctly validate .chm files.
What is the HTML protocol?
The HTML protocol is used to open compiled HTML Help files. For more
information about this protocol, visit the following Web site.
What is HTML Help?
Microsoft HTML Help is the standard help system for the Windows platform.
Authors can use HTML Help to create online Help files for a software
application or to create content for a multimedia title or for a Web site.
For more information about how to create online Help files, visit the
following Web site.
What is showHelp?
The showHelp method is used to display an HTML page that contains help
content. For more information about the showHelp method, visit the
following Web site.
What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could run
malicious code in the Local Machine security zone in Internet Explorer. By
running malicious code in the Local Machine zone, an attacker could gain
complete control over an affected system. An attacker could take any
action on the system, including installing programs, viewing data,
changing data, deleting data, or creating new accounts that have full
administrative credentials. For more information about URL security zones,
visit the following Web site.
What are Internet Explorer security zones?
Internet Explorer security zones are part of a system that divides online
content into categories or zones that are based on the trustworthiness of
the content. Specific Web domains can be assigned to a zone, depending on
how much trust is placed in the content of each domain. The zone then
restricts the capabilities of the Web content, based on the zone's policy.
By default, most Internet domains are treated as part of the Internet
zone. By default, the policy of the Internet zone prevents scripts and
other active code from accessing resources on the local system.
Who could exploit the vulnerability?
Any anonymous user could attempt to exploit this vulnerability.
How could an attacker exploit the vulnerability?
An attacker would have to host a Web site and then persuade a user to view
that Web site.
An attacker could also create an HTML e-mail message that contains a
specially crafted link, and then persuade a user to view the HTML e-mail
message and then click the link.
What systems are primarily at risk from the vulnerability?
Any system where Internet Explorer and mail clients are actively used is
primarily at risk from this vulnerability.
Are Windows 98, Windows 98 Second Edition or Windows Millennium Edition
critically affected by this vulnerability?
No. Although Windows 98, Windows 98 Second Edition and Windows Millennium
Edition do contain the affected component, the vulnerability is not
critical. For more information about severity ratings, visit the following
Web site.
Could the vulnerability be exploited over the Internet?
Yes. An attacker may be able to exploit this vulnerability over the
Internet.
What does the update do?
The update removes the vulnerability by making sure that the HTML Help
protocol only opens valid .chm files.
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-2003-1041.
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 currently
being exploited. The vulnerability that has been addressed has been
assigned the Common Vulnerability and Exposure number CAN-2003-1041.
Top of section
Top of section
HTML Help Vulnerability ~V CAN-2004-0201
A remote code execution vulnerability exists in HTML Help that could allow
remote code execution on an affected system. If a user is logged on with
administrative privileges, 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 privileges. Users whose accounts are
configured to have fewer privileges on the system would be at less risk
than users who operate with administrative privileges
Mitigating Factors for HTML Help Vulnerability - CAN-2004-0201:
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 site.
An attacker who successfully exploited this vulnerability could gain the
same privileges as the user. Users whose accounts are configured to have
fewer privileges on the system would be at less risk than users who
operate with administrative privileges.
Top of section
Workarounds for HTML Help Vulnerability - CAN-2004-0201:
Microsoft has tested the following workarounds. While these workarounds
will not correct the underlying vulnerability, they help block known
attack vectors. When a workaround reduces functionality, it is identified
below.
Unregister HTML Help
To unregister the HTML Help protocol, follow these steps:
1.
Click Start, click Run, type "regsvr32 /u %windir%\system32\itss.dll"
(without the quotation marks), and then click OK.
Note On Windows 98 and Windows Me, replace "system32" with "system" in
this command.
2.
A dialog box appears to confirm that the unregistration process has
succeeded. Click OK to close the dialog box.
Impact of Workaround: All HTML Help functionality will be unavailable.
This will affect the online Help in Windows or in any application that use
HTML Help functionality.
Read e-mail messages in plain text format if you are using Outlook 2002 or
later, or Outlook Express 6 SP1 or later, to help protect yourself from
the HTML e-mail attack vector.
Microsoft Outlook 2002 users who have applied Office XP Service Pack 1 or
later and Microsoft Outlook Express 6 users who have applied Internet
Explorer 6 Service Pack 1 can enable this setting and view e-mail messages
that are not digitally signed or e-mail messages that are not encrypted in
plain text only.
Digitally signed e-mail messages or encrypted e-mail messages are not
affected by the setting and may be read in their original formats. For
more information about enabling this setting in Outlook 2002, see
Microsoft Knowledge Base Article 307594.
For information about this setting in Outlook Express 6, see Microsoft
Knowledge Base Article 291387.
Impact of Workaround: E-mail messages that are viewed in plain text format
will not contain pictures, specialized fonts, animations, or other rich
content. In addition:
The changes are applied to the preview pane and to open messages.
Pictures become attachments so that they are not lost.
Because the message is still in Rich Text or HTML format in the store, the
object model (custom code solutions) may behave unexpectedly.
Top of section
FAQ for HTML Help Vulnerability - CAN-2004-0201:
What is the scope of the vulnerability?
This is a remote code execution vulnerability. If a user is logged on with
administrative privileges, 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 privileges. Users whose accounts are
configured to have fewer privileges on the system would be at less risk
than users who operate with administrative privileges.
What causes the vulnerability?
The vulnerability occurs because HTML Help does not completely validate
input data.
What is HTML Help?
Microsoft HTML Help is the standard help system for the Windows platform.
Authors can use HTML Help to create online Help files for a software
application or to create content for a multimedia title or for a Web site.
For more information about how to create online Help files, visit the
following Web site.
What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could gain the
same privileges as the user. Users whose accounts are configured to have
fewer privileges on the system would be at less risk than users who
operate with administrative privileges.
Who could exploit the vulnerability?
Any anonymous user could attempt to exploit this vulnerability.
How could an attacker exploit the vulnerability?
To exploit this vulnerability, an attacker would have to host a malicious
Web site and then persuade a user to view that Web site. An attacker could
also create an HTML e-mail message that contains a specially crafted link,
and then persuade a user to view the HTML e-mail message and then click
the link.
What systems are primarily at risk from the vulnerability?
Any system where Internet Explorer and mail clients are actively used is
primarily at risk from this vulnerability.
Are Windows 98, Windows 98 Second Edition or Windows Millennium Edition
critically affected by this vulnerability?
Yes. Updates 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
Could the vulnerability be exploited over the Internet?
Yes. An attacker may be able to exploit this vulnerability over the
Internet.
What does the update do?
The update removes the vulnerability by modifying the way that HTML Help
validates the contents of a Help file.
How does this vulnerability relate to the Help and SupportCenter issues
that are addressed by MS04-011 and MS04-015?
They are not related. Both the previous vulnerabilities were in the Help
and Support Center. However, this update corrects a new vulnerability in
HTML Help.
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 indicating 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.
Top of section
Top of section
Top of section
Security Update Information
Installation Platforms and Prerequisites:
For information about the specific security update for your platform,
click the appropriate link:
Windows Server 2003 (all versions)
Prerequisites
This security update requires a release version of Windows Server 2003.
Inclusion in Future Service Packs:
The update for this issue will be included in Windows Server 2003 Service
Pack 1.
Installation Information
This security update supports the following setup switches:
/help Displays the command line options
Setup Modes
/quiet Quiet mode (no user interaction or display)
/passive Unattended mode (progress bar only)
/uninstall Uninstalls the package
Restart Options
/norestart Do not restart when installation is complete
/forcerestart Restart after installation
Special Options
/l Lists installed Windows hotfixes or update
packages
/o Overwrite OEM files without prompting
/n Do not backup files needed for uninstall
/f Force other programs to close when the
computer shuts down
/extract Extracts files without starting setup
Note You can combine these switches into one command. For backward
compatibility, the security update also supports the setup switches that
the previous version of the setup utility uses. For more information about
the supported installation switches, see Microsoft Knowledge Base Article
about the supported installation switches, see Microsoft Knowledge Base
Article 262841.
Deployment Information
To install the security update without any user intervention, use the
following command at a command prompt for Windows Server 2003:
Windowsserver2003-kb840315-x86-enu /passive /quiet
To install the security update without forcing the system to restart, use
the following command at a command prompt for Windows Server 2003:
Windowsserver2003-kb840315-x86-enu /norestart
For information about how to deploy this security update with Software
Update Services, visit the Software Update Services Web site.
Restart Requirement
In some cases, this update does not require a restart. The installer stops
the required services, applies the update, and then restarts the services.
However, if the required services cannot be stopped for any reason or if
required files are in use, this update will require a restart. If this
occurs, a message appears that advises you to 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%\$NTUninstallKB840315$\Spuninst folder. The Spuninst.exe utility
supports the following setup switches:
/?: Show the list of installation switches.
/u: Use unattended mode.
/f: Force other programs to quit when the computer shuts down.
/z: Do not restart when the installation is complete.
/q: Use Quiet mode (no user interaction).
File Information
The English version of this update has the file attributes (or later) 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.
Windows Server 2003 Enterprise Edition, Windows Server 2003 Standard
Edition, Windows Server 2003 Web Edition, and Windows Server 2003
Datacenter Edition:
Date Time Version Size File name Folder
- -------------------------------------------------------------------------
23-Jun-2004 00:03 5.2.3790.185 123,392 Itss.dll RTMGDR
23-Jun-2004 00:12 5.2.3790.185 123,392 Itss.dll RTMQFE
Windows Server 2003 64-Bit Enterprise Edition and Windows Server 2003
64-Bit Datacenter Edition:
Date Time Version Size File name Platform Folder
- -------------------------------------------------------------------------
23-Jun-2004 00:05 5.2.3790.185 361,472 Itss.dll IA64 RTMGDR
23-Jun-2004 00:03 5.2.3790.185 123,392 Witss.dll X86 RTMGDR
23-Jun-2004 00:12 5.2.3790.185 361,472 Itss.dll IA64 RTMQFE
23-Jun-2004 00:12 5.2.3790.185 123,392 Witss.dll X86 RTMQFE
Note When you install this security update on Windows Server 2003 or on
Windows XP 64-Bit Edition Version 2003, the installer checks to see if any
of the files that are being updated on your system have previously been
updated by a Microsoft hotfix. If you have previously installed a hotfix
to update one of these files, the installer copies the RTMQFE files to
your system. Otherwise, the installer copies the RTMGDR files to your
system. For more information, see Microsoft Knowledge Base Article 824994.
Verifying Update Installation
Microsoft Baseline Security Analyzer
To verify that a security update is installed on an affected system, you
may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool.
This tool 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.
File Version Verification
Note 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 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 the update installation.
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.
~U
Registry Key Verification
You may also be able to verify the files that this security update has
installed by reviewing the following registry key.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server
2003\SP1\KB840315\Filelist
Note This registry key may not contain a complete list of installed files.
Also, this registry key may not be created correctly if an administrator
or an OEM integrates or slipstreams the 840315 security update into the
Windows installation source files.
Top of section
Windows XP (all versions)
Note For Windows XP 64-Bit Edition Version 2003, this security update is
the same as the Windows Server 2003 64-Bit Edition security update.
Prerequisites
This security update requires the release version of Windows XP or Windows
XP Service Pack 1 (SP1). For more information, see Microsoft Knowledge
Base Article 322389.
Inclusion in Future Service Packs:
The update for this issue will be included in Windows XP Service Pack 2.
Installation Information
This security update supports the following setup switches:
/help Displays the command line options
Setup Modes
/quiet Quiet mode (no user interaction or display)
/passive Unattended mode (progress bar only)
/uninstall Uninstalls the package
Restart Options
/norestart Do not restart when installation is complete
/forcerestart Restart after installation
Special Options
/l Lists installed Windows hotfixes or update
packages
/o Overwrite OEM files without prompting
/n Do not backup files needed for uninstall
/f Force other programs to close when the
computer shuts down
/extract Extracts files without starting setup
Note You can combine these switches into one command. For backward
compatibility, the security update also supports the setup switches that
the previous version of the setup utility uses. For more information about
the supported installation switches, see Microsoft Knowledge Base Article
262841.
Deployment Information
To install the security update without any user intervention, use the
following command at a command prompt for Windows XP:
Windowsxp-kb840315-x86-enu /passive /quiet
To install the security update without forcing the system to restart, use
the following command at a command prompt for Windows XP:
Windowsxp-kb840315-x86-enu /norestart
For more information about how to deploy this security update with
Software Update Services, visit the Software Update Services Web site.
Restart Requirement
In some cases, this update does not require a restart. The installer stops
the required services, applies the update, and then restarts the services.
However, if the required services cannot be stopped for any reason or if
required files are in use, this update will require a restart. If this
occurs, a message appears that advises you to 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 is located in the
%Windir%\$NTUninstallKB840315$\Spuninst folder. The Spuninst.exe utility
supports the following setup switches:
/?: Show the list of installation switches.
/u: Use unattended mode.
/f: Force other programs to quit when the computer shuts down.
/z: Do not restart when the installation is complete.
/q: Use Quiet mode (no user interaction).
File Information
The English version of this update has the file attributes (or later) 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.
Windows XP Home Edition, Windows XP Professional, Windows XP Home Edition
Service Pack 1, Windows XP Professional Service Pack 1, Windows XP Tablet
PC Edition, and Windows XP Media Center Edition:
Date Time Version Size File name Folder
- -------------------------------------------------------------------
23-Jun-2004 00:43 5.2.3790.185 123,392 Itss.dll RTMQFE
23-Jun-2004 00:43 5.2.3790.185 123,392 Itss.dll SP1QFE
Windows XP 64-Bit Edition Service Pack 1:
Date Time Version Size File name Platform Folder
- --------------------------------------------------------------------------
23-Jun-2004 00:49 5.2.3790.185 361,472 Itss.dll IA64 SP1QFE
23-Jun-2004 00:43 5.2.3790.185 123,392 Witss.dll X86 SPIQFE
Windows XP 64-Bit Edition Version 2003:
Date Time Version Size File name Platform Folder
- -------------------------------------------------------------------------
23-Jun-2004 00:05 5.2.3790.185 361,472 Itss.dll IA64 RTMGDR
23-Jun-2004 00:03 5.2.3790.185 123,392 Witss.dll X86 RTMGDR
23-Jun-2004 00:12 5.2.3790.185 361,472 Itss.dll IA64 RTMQFE
23-Jun-2004 00:12 5.2.3790.185 123,392 Witss.dll X86 RTMQFE
Notes The Windows XP and Windows XP 64-Bit Edition Version 2003 versions
of this security update are packaged as dual-mode packages, which contain
files for both the original version of Windows XP and Windows XP Service
Pack 1 (SP1). For more information about dual-mode packages, see Microsoft
Knowledge Base Article 328848.
When you install the Windows XP 64-Bit Edition Version 2003 security
update, the installer checks to see if any of the files that are being
updated on your system have previously been updated by a Microsoft hotfix.
If you have previously installed a hotfix to update one of these files,
the installer copies the RTMQFE files to your system. Otherwise, the
installer copies the RTMGDR files to your system. For more information,
see Microsoft Knowledge Base Article 824994.
Verifying Update Installation
Microsoft Baseline Security Analyzer
To verify that a security update is installed on an affected system, you
may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool.
This tool 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.
File Version Verification
Note 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 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 the update installation.
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 following registry keys.
For Windows XP Home Edition, Windows XP Professional, Windows XP Home
Edition Service Pack 1, Windows XP Professional Service Pack 1, Windows XP
64-Bit Edition Service Pack 1, Windows XP Tablet PC Edition, and Windows
XP Media Center Edition:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows
XP\SP2\KB840315\Filelist
For Windows XP 64-Bit Edition Version 2003:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server
2003\SP1\KB840315\Filelist
Note These registry keys may not contain a complete list of installed
files. Also, these registry keys may not be created correctly if an
administrator or an OEM integrates or slipstreams the 840315 security
update into the Windows installation source files.
Top of section
Windows 2000 (all versions)
Prerequisites
For Windows 2000, this security update requires Service Pack 2 (SP2),
Service Pack 3 (SP3), or Service Pack 4 (SP4).
The software that is listed has been tested to determine if the versions
are affected. Other versions either no longer include security update
support or may not be affected. To determine the support lifecycle 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 will be included in Windows 2000 Service Pack 5.
Installation Information
This security update supports the following setup switches:
/help Displays the command line options
Setup Modes
/quiet Quiet mode (no user interaction or display)
/passive Unattended mode (progress bar only)
/uninstall Uninstalls the package
Restart Options
/norestart Do not restart when installation is complete
/forcerestart Restart after installation
Special Options
/l Lists installed Windows hotfixes or update
packages
/o Overwrite OEM files without prompting
/n Do not backup files needed for uninstall
/f Force other programs to close when the
computer shuts down
/extract Extracts files without starting setup
Note You can combine these switches into one command. For backward
compatibility, the security update also supports the setup switches that
the previous version of the setup utility uses. For more information about
the supported installation switches, see Microsoft Knowledge Base Article
262841.
Deployment Information
To install the security update without any user intervention, use the
following command at a command prompt for Windows 2000 Service Pack 2,
Windows 2000 Service Pack 3, and Windows 2000 Service Pack 4:
Windows2000-kb840315-x86-enu /passive /quiet
To install the security update without forcing the system to restart, use
the following command at a command prompt for Windows 2000 Service Pack 2,
Windows 2000 Service Pack 3, and Windows 2000 Service Pack 4:
Windows2000-kb840315-x86-enu /norestart
For more information about how to deploy this security update with
Software Update Services, visit the Software Update Services Web site.
Restart Requirement
In some cases, this update does not require a restart. The installer stops
the required services, applies the update, and then restarts the services.
However, if the required services cannot be stopped for any reason or if
required files are in use, this update will require a restart. If this
occurs, a message appears that advises you to 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%\$NTUninstallKB840315$\Spuninst folder. The Spuninst.exe utility
supports the following setup switches:
/?: Show the list of installation switches.
/u: Use unattended mode.
/f: Force other programs to quit when the computer shuts down.
/z: Do not restart when the installation is complete.
/q: Use Quiet mode (no user interaction).
File Information
The English version of this update has the file attributes (or later) 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.
Note Date, time, file name, or size information could change during
installation. See the Verifying Update Installation section for details
about how to verify an installation.
Windows 2000 Service Pack 2, Windows 2000 Service Pack 3, and Windows 2000
Service Pack 4:
Date Time Version Size File name
- ------------------------------------------------------
22-Jun-2004 22:42 5.2.3790.185 123,392 Itss.dll
Verifying Update Installation
File Version Verification
Note 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 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 the update installation.
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 following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows
2000\SP5\KB840315\Filelist
Note This registry key may not contain a complete list of installed files.
Also, this registry key may not be created correctly when an administrator
or an OEM integrates or slipstreams the 840315 security update into the
Windows installation source files.
Top of section
Windows NT 4.0 (all versions)
Prerequisites
This security update requires Windows NT Workstation 4.0 Service Pack 6a
(SP6a), Windows NT Server 4.0 Service Pack 6a (SP6a), or Windows NT Server
4.0 Terminal Server Edition Service Pack 6 (SP6) with Internet Explorer 6
Service Pack 1 installed.
The software that is listed has been tested to determine if the versions
are affected. Other versions either no longer include security update
support or may not be affected. To determine the support lifecycle for
your product and version, visit the following Microsoft Support Lifecycle
Web site.
For more information about obtaining the latest service pack, see
Microsoft Knowledge Base Article 152734.
Installation Information
This security update supports the following setup switches:
/q: Specifies quiet mode, or suppresses prompts, when files are being
extracted. This switch does not suppress prompts when Windows Update Setup
is running.
/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:<UNC location> Specifies the path and name of the Setup .inf or .exe
file.
/r:n : Never restarts the computer after installation.
/r:a : Always restarts the computer after installation.
/r:s : Restarts the computer after installation without prompting the
user.
/T:<directory path: Specifies the target folder for extracting files.
Note You can combine these switches into one command. For more information
about the supported installation 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:
Windowsnt4-kb840315-x86-enu /q:a
To install the security update without forcing the system to restart, use
the following command at a command prompt:
Windowsnt4-kb840315-x86-enu /r:n
For more information about how to deploy this security update with
Software Update Services, visit the Software Update Services Web site.
Restart Requirement
In some cases, this update does not require a restart. The installer stops
the needed services, applies the update, and then restarts the services.
However, if the required services cannot be stopped for any reason or if
required files are in use, this update will require a restart. If this
occurs, a message appears that advises you to restart.
Removal Information
To remove this security update, use the Add/Remove Programs tool in
Control Panel.
Or
Click Start, click Run, type "RunDll32 advpack.dll,LaunchINFSectionEx
%Windir%\$NTUninstallQ840315$\840315UP.INF,updfiles,,64" (without the
quotation marks), and then click OK.
File Information
The English version of this update has the file attributes (or later) 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.
Note Date, time, file name, or size information could change during
installation. See the Verifying Update Installation section for details
about how to verify an installation.
Windows NT Workstation 4.0 and Windows NT Server 4.0:
Date Time Version Size File name
- ------------------------------------------------------
22-Jun-2004 18:11 5.2.3790.185 123,392 Itss.dll
Windows NT Server 4.0 Terminal Server Edition:
Date Time Version Size File name
- -------------------------------------------------------
22-Jun-2004 18:11 5.2.3790.185 123,392 Itss.dll
Verifying Update Installation
Microsoft Baseline Security Analyzer
To verify that a security update is installed on an affected system, you
may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool.
This tool 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.
File Version Verification
Note 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 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 the update installation.
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 following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\Hotfix\Q840315
Note This registry key may not contain a complete list of installed files.
Also, this registry key may not be created correctly when an administrator
or an OEM integrates or slipstreams the 840315 security update into the
Windows installation source files.
Top of section
Top of section
Acknowledgments
Microsoft thanks the following for working with us to help protect
customers:
Brett Moore of Security-Assessment.com for reporting the HTML Help
Vulnerability (CAN-2004-0201).
Obtaining Other Security Updates:
Updates for other security issues are available from the following
locations:
Security updates are available from the Microsoft Download Center: You can
find them most easily by doing a keyword search for "security_patch".
Updates for consumer platforms are available from the Windows Update Web
site.
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:
The Microsoft TechNet Security Web site provides additional information
about security in Microsoft products.
Microsoft Software Update Services
Microsoft Baseline Security Analyzer (MBSA)
Windows Update
Windows Update Catalog: For more information about the Windows Update
Catalog, see Microsoft Knowledge Base Article 323166.
Office Update
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 with
Software Update Services, visit the Software 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 to
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, see 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 and the Microsoft
Office Detection 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, see 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 13, 2004): Bulletin published
-----BEGIN PGP SIGNATURE-----
Version: PGP 6.5.8
iQCVAwUBQPRhu+kli63F4U8VAQFWAwP+MbTZNOr6kjT2j9Kvk16jiBAlNf96CMY0
s2vD5fr7Hn0fsrzuJHQZCmn6EKNouavC/TTIvj2yRsgP33rPcgXkrwwJmE5guSHN
Qmgmlxu/9I+taobMt6fzStfVv0gp1UORlbLrojUFFwEAEIZfCPs5uGZuPRfzS2kv
FRrsFknZY/0=
=kvFR
-----END PGP SIGNATURE-----
----- End forwarded message -----
Mais detalhes sobre a lista de discussão SECURITY-L