[NT] Vulnerabilities in Microsoft Word Allows Code Execution (MS06-060)

The following security advisory is sent to the securiteam mailing list, and can be found at the SecuriTeam web site: http://www.securiteam.com
- - promotion

The SecuriTeam alerts list - Free, Accurate, Independent.

Get your security news from a reliable source.
http://www.securiteam.com/mailinglist.html

- - - - - - - - -



Vulnerabilities in Microsoft Word Allows Code Execution (MS06-060)
------------------------------------------------------------------------


SUMMARY

Several vulnerabilities discovered in different versions of Microsoft Word
that allow remote attackers to cause the product to execute arbitrary
code.

DETAILS

Affected Software:
* Microsoft Office 2000 Service Pack 3 -
<http://www.microsoft.com/downloads/details.aspx?FamilyId=CFC85449-4941-4DA5-A919-1DA388054E83> Download the update (KB920910)
* Microsoft Office XP Service Pack 3 -
<http://www.microsoft.com/downloads/details.aspx?FamilyId=5652303E-04B3-4713-AF2E-2C8D2450468D> Download the update (KB920817)
* Microsoft Office 2003 Service Pack 1 or Service Pack 2 -
<http://www.microsoft.com/downloads/details.aspx?FamilyId=30C516EB-BD63-4248-A34D-47AF7E9EA55A> Download the update (KB923094)
* Microsoft Office Word 2003 Viewer -
<http://www.microsoft.com/downloads/details.aspx?FamilyId=EB230319-14A5-4206-A601-CF9DDE89352A> Download the update (KB923276)
* Microsoft Works Suite 2004 -
<http://www.microsoft.com/downloads/details.aspx?FamilyId=5652303E-04B3-4713-AF2E-2C8D2450468D> Download the update (KB920817) (same as the Microsoft Word 2002 update)
* Microsoft Works Suite 2005 -
<http://www.microsoft.com/downloads/details.aspx?FamilyId=5652303E-04B3-4713-AF2E-2C8D2450468D> Download the update (KB920817) (same as the Microsoft Word 2002 update)
* Microsoft Works Suite 2006 -
<http://www.microsoft.com/downloads/details.aspx?FamilyId=5652303E-04B3-4713-AF2E-2C8D2450468D> Download the update (KB920817) (same as the Microsoft Word 2002 update)
* Microsoft Office 2004 for Mac - <http://www.microsoft.com/mac/>
Download the update (KB924999)
* Microsoft Office v. X for Mac- <http://www.microsoft.com/mac/>
Download the update (KB924998)

Microsoft Word Vulnerability -
<http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-3647>
CVE-2006-3647:
A remote code execution vulnerability exists in Word. An attacker could
exploit this vulnerability when Word parsed a file that contains a
malformed string. Such a specially crafted file might be included as an
e-mail attachment or hosted on a malicious web site. Viewing or previewing
a malformed e-mail message in Outlook could not lead to exploitation of
this vulnerability.

If a user were logged on with administrative user rights, an attacker who
successfully exploited this vulnerability could take complete control of
an affected system. An attacker could then install programs; view, change,
or delete data; or create new accounts with full user rights. Users whose
accounts are configured to have fewer user rights on the system could be
less affected than users who operate with administrative user rights.

Mitigating Factors for Microsoft Word Vulnerability -
<http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-3647>
CVE-2006-3647:
* An attacker who successfully exploited this vulnerability could gain
the same user rights as the local user. Users whose accounts are
configured to have fewer user rights on the system could be less impacted
than users who operate with administrative user rights.

* In a Web-based attack scenario, an attacker would have to host a Web
site that contains a Word file that is used to attempt to exploit this
vulnerability. In addition, compromised Web sites and Web sites that
accept or host user-provided content could contain specially crafted
content that could 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.

* The vulnerability cannot be exploited automatically through e-mail. For
an attack to be successful a user must open an attachment that is sent in
an e-mail message.

* Users who have installed and are using the
<http://www.microsoft.com/downloads/details.aspx?familyid=8B5762D2-077F-4031-9EE6-C9538E9F2A2F> Office Document Open Confirmation Tool for Office 2000 will be prompted with Open, Save, or Cancel before opening a document. The features of the Office Document Open Confirmation Tool are incorporated in Office XP and Office 2003.

Workarounds for Microsoft Word Vulnerability -
<http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-3647>
CVE-2006-3647:
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
in the following section.

Do not open or save Microsoft Word files that you receive from untrusted
sources or that you received unexpectedly from trusted sources. This
vulnerability could be exploited when a user opens a file.

FAQ for Microsoft Word Vulnerability -
<http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-3647>
CVE-2006-3647:
What is the scope of the vulnerability?
A remote code execution vulnerability exists in Word. An attacker could
exploit this vulnerability when Word parses a file that contains a
malformed string.

If a user were logged on with administrative user rights, an attacker who
successfully exploited this vulnerability could take complete control of
an affected system. An attacker could then install programs; view, change,
or delete data; or create new accounts with full user rights. Users whose
accounts are configured to have fewer user rights on the system could be
less affected than users who operate with administrative user rights.

What causes the vulnerability?
When Microsoft Word opens a specially crafted Word file, it may corrupt
system memory in such a way that an attacker could execute arbitrary code.

What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could take
complete control of the affected system.

How could an attacker exploit the vulnerability?
In an e-mail attack scenario, an attacker could exploit the vulnerability
by sending a specially-crafted file to the user and by persuading the user
to open the file.

In a Web-based attack scenario, an attacker would have to host a Web site
that contains a Word file that is used to attempt to exploit this
vulnerability. In addition, compromised Web sites and Web sites that
accept or host user-provided content could contain specially crafted
content that could 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.

What systems are primarily at risk from the vulnerability?
Workstations and terminal servers are primarily at risk. Servers could be
at more risk if users who have sufficient administrative permissions are
given the ability to log on to servers and to run programs. However, best
practices strongly discourage allowing this.

What does the update do?
The update removes the vulnerability by modifying the way that Microsoft
Word parses the file and validates the string before it passes the message
to the allocated buffer.

When this security bulletin was issued, had this vulnerability been
publicly disclosed?
No. Microsoft received information about this vulnerability through
responsible disclosure. Microsoft had not received any information to
indicate that this vulnerability had been publicly disclosed when this
security bulletin was originally issued. This security bulletin addresses
the privately disclosed vulnerability as well as additional issues
discovered through internal investigations.

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.

Microsoft Word Mail Merge Vulnerability -
<http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-3651>
CVE-2006-3651:
A remote code execution vulnerability exists in Microsoft Word, and could
be exploited when Word opens a specially crafted mail merge file. Such a
specially crafted file might be included as an e-mail attachment or hosted
on a malicious web site. Viewing or previewing a malformed e-mail message
in an affected version of Outlook could not lead to exploitation of this
vulnerability. An attacker could exploit the vulnerability by constructing
a specially crafted Word file that could allow remote code execution.

If a user were logged on with administrative user rights, an attacker who
successfully exploited this vulnerability could take complete control of
an affected system. An attacker could then install programs; view, change,
or delete data; or create new accounts with full user rights. Users whose
accounts are configured to have fewer user rights on the system could be
less affected than users who operate with administrative user rights.

Mitigating Factors for Microsoft Word Mail Merge Vulnerability -
<http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-3651>
CVE-2006-3651:
* An attacker who successfully exploited this vulnerability could gain
the same user rights as the local user. Users whose accounts are
configured to have fewer user rights on the system could be less impacted
than users who operate with administrative user rights.

* In a Web-based attack scenario, an attacker would have to host a Web
site that contains a Word file that is used to attempt to exploit this
vulnerability. In addition, compromised Web sites and Web sites that
accept or host user-provided content could contain specially crafted
content that could 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.

* The vulnerability cannot be exploited automatically through e-mail. For
an attack to be successful a user must open an attachment that is sent in
an e-mail message.

* Users who have installed and are using the
<http://www.microsoft.com/downloads/details.aspx?familyid=8B5762D2-077F-4031-9EE6-C9538E9F2A2F> Office Document Open Confirmation Tool for Office 2000 will be prompted with Open, Save, or Cancel before opening a document. The features of the Office Document Open Confirmation Tool are incorporated in Office XP and Office 2003.

Workarounds for Microsoft Word Mail Merge Vulnerability -
<http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-3651>
CVE-2006-3651:
Do not open or save Microsoft Word files that you receive from untrusted
sources or that you received unexpectedly from trusted sources. This
vulnerability could be exploited when a user opens a file.

FAQ for Microsoft Word Mail Merge Vulnerability -
<http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-3651>
CVE-2006-3651:
What is the scope of the vulnerability?
A remote code execution vulnerability exists in Microsoft Word, and could
be exploited when Word opens a specially crafted mail merge file. Such a
specially crafted file might be included as an e-mail attachment or hosted
on a malicious web site. Viewing or previewing a malformed e-mail message
in an affected version of Outlook could not lead to exploitation of this
vulnerability. An attacker could exploit the vulnerability by constructing
a specially crafted Word file that could allow remote code execution.

If a user were logged on with administrative user rights, an attacker who
successfully exploited this vulnerability could take complete control of
an affected system. An attacker could then install programs; view, change,
or delete data; or create new accounts with full user rights. Users whose
accounts are configured to have fewer user rights on the system could be
less affected than users who operate with administrative user rights.

What causes the vulnerability?
When Microsoft Word opens a specially crafted Word mail merge file, it may
corrupt system memory in such a way that an attacker could execute
arbitrary code.

What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could cause
arbitrary code to run with the privileges of the user who opened the file.

How could an attacker exploit the vulnerability?
In an e-mail attack scenario, an attacker could exploit the vulnerability
by sending a specially-crafted file to the user and by persuading the user
to open the file.

In a Web-based attack scenario, an attacker would have to host a Web site
that contains a Word file that is used to attempt to exploit this
vulnerability. In addition, compromised Web sites and Web sites that
accept or host user-provided content could contain specially crafted
content that could 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.

What systems are primarily at risk from the vulnerability?
Workstations and terminal servers are primarily at risk. Servers could be
at more risk if users who have sufficient administrative permissions are
given the ability to log on to servers and to run programs. However, best
practices strongly discourage allowing this.

What does the update do?
The update removes the vulnerability by modifying the way that Microsoft
Word parses the length of a mail merge record before it passes the message
to the allocated buffer.

When this security bulletin was issued, had this vulnerability been
publicly disclosed?
No. Microsoft received information about this vulnerability through
responsible disclosure. Microsoft had not received any information to
indicate that this vulnerability had been publicly disclosed when this
security bulletin was originally issued. This security bulletin addresses
the privately disclosed vulnerability as well as additional issues
discovered through internal investigations.

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.

Microsoft Word Malformed Stack Vulnerability -
<http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-4534>
CVE-2006-4534:
A remote code execution vulnerability exists in Microsoft Word, and could
be exploited when Word opens a specially crafted file. Such a specially
crafted file might be included as an e-mail attachment or hosted on a
malicious web site. Viewing or previewing a malformed e-mail message in an
affected version of Outlook could not lead to exploitation of this
vulnerability. An attacker could exploit the vulnerability by constructing
a specially crafted Word file that could allow remote code execution.

If a user were logged on with administrative user rights, an attacker who
successfully exploited this vulnerability could take complete control of
an affected system. An attacker could then install programs; view, change,
or delete data; or create new accounts with full user rights. Users whose
accounts are configured to have fewer user rights on the system could be
less affected than users who operate with administrative user rights.

Mitigating Factors for Microsoft Word Malformed Stack Vulnerability -
<http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-4534>
CVE-2006-4534:
* An attacker who successfully exploited this vulnerability could gain
the same user rights as the local user. Users whose accounts are
configured to have fewer user rights on the system could be less impacted
than users who operate with administrative user rights.

* In a Web-based attack scenario, an attacker would have to host a Web
site that contains a Word file that is used to attempt to exploit this
vulnerability. In addition, compromised Web sites and Web sites that
accept or host user-provided content could contain specially crafted
content that could 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.

* The vulnerability cannot be exploited automatically through e-mail. For
an attack to be successful a user must open an attachment that is sent in
an e-mail message.

* Users who have installed and are using the
<http://www.microsoft.com/downloads/details.aspx?familyid=8B5762D2-077F-4031-9EE6-C9538E9F2A2F> Office Document Open Confirmation Tool for Office 2000 will be prompted with Open, Save, or Cancel before opening a document. The features of the Office Document Open Confirmation Tool are incorporated in Office XP and Office 2003.

Workarounds for Microsoft Word Malformed Stack Vulnerability -
<http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-4534>
CVE-2006-4534:
Do not open or save Microsoft Word files that you receive from untrusted
sources or that you received unexpectedly from trusted sources. This
vulnerability could be exploited when a user opens a file.

FAQ for Microsoft Word Malformed Stack Vulnerability -
<http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-4534>
CVE-2006-4534:
What is the scope of the vulnerability?
A remote code execution vulnerability exists in Microsoft Word, and could
be exploited when Word opens a specially crafted file. Such a specially
crafted file might be included as an e-mail attachment or hosted on a
malicious web site. Viewing or previewing a malformed e-mail message in an
affected version of Outlook could not lead to exploitation of this
vulnerability. An attacker could exploit the vulnerability by constructing
a specially crafted Word file that could allow remote code execution.

If a user were logged on with administrative user rights, an attacker who
successfully exploited this vulnerability could take complete control of
an affected system. An attacker could then install programs; view, change,
or delete data; or create new accounts with full user rights. Users whose
accounts are configured to have fewer user rights on the system could be
less affected than users who operate with administrative user rights.

What causes the vulnerability?
When Microsoft Word opens a specially crafted Word file, it may corrupt
system memory in such a way that an attacker could execute arbitrary code.

What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could cause
arbitrary code to run with the privileges of the user who opened the file.

How could an attacker exploit the vulnerability?
In an e-mail attack scenario, an attacker could exploit the vulnerability
by sending a specially-crafted file to the user and by persuading the user
to open the file.

In a Web-based attack scenario, an attacker would have to host a Web site
that contains a Word file that is used to attempt to exploit this
vulnerability. In addition, compromised Web sites and Web sites that
accept or host user-provided content could contain specially crafted
content that could 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.

What systems are primarily at risk from the vulnerability?
Workstations and terminal servers are primarily at risk. Servers could be
at more risk if users who have sufficient administrative permissions are
given the ability to log on to servers and to run programs. However, best
practices strongly discourage allowing this.

What does the update do?
The update removes the vulnerability by modifying the way that Microsoft
Word parses the length of a record before it passes the message to the
allocated buffer.

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 CVE-2006-4534.

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
<http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-4534>
CVE-2006-4534

Microsoft Word for Mac Vulnerability -
<http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-4693>
CVE-2006-4693:
A remote code execution vulnerability exists in Word for Mac. An attacker
could exploit this vulnerability when Word for Mac parses a specially
crafted file that contains a malformed string. Such a specially crafted
file might be included as an e-mail attachment or hosted on a malicious
web site. Viewing or previewing a malformed e-mail message in Outlook
could not lead to exploitation of this vulnerability. An attacker could
exploit the vulnerability by constructing a specially crafted Word file
that could allow remote code execution.

If a user were logged on with administrative user rights, an attacker who
successfully exploited this vulnerability could take complete control of
an affected system. An attacker could then install programs; view, change,
or delete data; or create new accounts with full user rights. Users whose
accounts are configured to have fewer user rights on the system could be
less affected than users who operate with administrative user rights.

Mitigating Factors for Microsoft Word for Mac Vulnerability -
<http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-4693>
CVE-2006-4693:
* An attacker who successfully exploited this vulnerability could gain
the same user rights as the local user. Users whose accounts are
configured to have fewer user rights on the system could be less impacted
than users who operate with administrative user rights.

* In a Web-based attack scenario, an attacker would have to host a Web
site that contains a Word file that is used to attempt to exploit this
vulnerability. In addition, compromised Web sites and Web sites that
accept or host user-provided content could contain specially crafted
content that could 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.

* The vulnerability cannot be exploited automatically through e-mail. For
an attack to be successful a user must open an attachment that is sent in
an e-mail message.

Workarounds for Microsoft Word for Mac Vulnerability -
<http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-4693>
CVE-2006-4693:
Do not open or save Microsoft Word files that you receive from untrusted
sources or that you received unexpectedly from trusted sources. This
vulnerability could be exploited when a user opens a file.

FAQ for Microsoft Word for Mac Vulnerability -
<http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-4693>
CVE-2006-4693:
What is the scope of the vulnerability?
A remote code execution vulnerability exists in Word for Mac. An attacker
could exploit this vulnerability when Word for Mac parses a file that
contains a malformed string.

If a user were logged on with administrative user rights, an attacker who
successfully exploited this vulnerability could take complete control of
an affected system. An attacker could then install programs; view, change,
or delete data; or create new accounts with full user rights. Users whose
accounts are configured to have fewer user rights on the system could be
less affected than users who operate with administrative user rights.

What causes the vulnerability?
When Microsoft Word for Mac opens a specially crafted Word file, it may
corrupt system memory in such a way that an attacker could execute
arbitrary code.

What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could take
complete control of the affected system.

How could an attacker exploit the vulnerability?
In an e-mail attack scenario, an attacker could exploit the vulnerability
by sending a specially-crafted file to the user and by persuading the user
to open the file.

In a Web-based attack scenario, an attacker would have to host a Web site
that contains a Word file that is used to attempt to exploit this
vulnerability. In addition, compromised Web sites and Web sites that
accept or host user-provided content could contain specially crafted
content that could 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.

What systems are primarily at risk from the vulnerability?
Workstations are primarily at risk. Servers could be at more risk if users
who have sufficient administrative permissions are given the ability to
log on to servers and to run programs. However, best practices strongly
discourage allowing this.

What does the update do?
The update removes the vulnerability by modifying the way that Microsoft
Word for Mac parses the file and validates the string.

When this security bulletin was issued, had this vulnerability been
publicly disclosed?
No. Microsoft received information about this vulnerability through
responsible disclosure. Microsoft had not received any information to
indicate that this vulnerability had been publicly disclosed when this
security bulletin was originally issued. This security bulletin addresses
the privately disclosed vulnerability as well as additional issues
discovered through internal investigations.

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.


ADDITIONAL INFORMATION

The information has been provided by Microsoft Security Bulletin.
The original article can be found at:
<http://www.microsoft.com/technet/security/bulletin/ms06-060.mspx>
http://www.microsoft.com/technet/security/bulletin/ms06-060.mspx



========================================


This bulletin is sent to members of the SecuriTeam mailing list.
To unsubscribe from the list, send mail with an empty subject line and body to: list-unsubscribe@xxxxxxxxxxxxxx
In order to subscribe to the mailing list, simply forward this email to: list-subscribe@xxxxxxxxxxxxxx


====================
====================

DISCLAIMER:
The information in this bulletin is provided "AS IS" without warranty of any kind.
In no event shall we be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages.

Relevant Pages