Computer Security
[EN] securityvulns.ru no-pyccku


Related information

  Microsoft Works / Microsoft Office multiple security vulnerabilities

  iDefense Security Advisory 02.12.08: Microsoft Office Works Converter Stack-based Buffer Overflow Vulnerability

  iDefense Security Advisory 02.12.08: Microsoft Office Works Converter Heap Overflow Vulnerability

From:MICROSOFT <secure_(at)_microsoft.com>
Date:13.02.2008
Subject:Microsoft Security Bulletin MS08-011 – Important Vulnerabilities in Microsoft Works File Converter Could Allow Remote Code Execution (947081)

Microsoft Security Bulletin MS08-011 – Important
Vulnerabilities in Microsoft Works File Converter Could Allow Remote Code Execution (947081)
Published: February 12, 2008

Version: 1.0
General Information
Executive Summary

This important security update resolves three privately reported vulnerabilities in the Microsoft Works File Converter. These vulnerabilities could allow remote code execution if a user opens a specially crafted Works (.wps) file with an affected version of Microsoft Office, Microsoft Works, or Microsoft Works Suite. 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.

This is an important security update for all supported editions of Microsoft Works Converter. For more information, see the subsection, Affected and Non-Affected Software, in this section.

The security update addresses these vulnerabilities by replacing the vulnerable version of the Works Converter on a system. 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 947081 documents the currently known issues that customers may experience when they install this security update. The article also documents recommended solutions for these issues.
Top of sectionTop of section
Affected and Non-Affected Software

The following software has been tested to determine which versions or editions are affected. Other versions or editions are either past their support life cycle or are not affected. To determine the support life cycle for your software version or edition, visit Microsoft Support Lifecycle.

Affected Software
Office Suite and Other Affected Software Component Maximum Security Impact Aggregate Severity Rating Bulletins Replaced by this Update

Microsoft Office 2003 Service Pack 2


Microsoft Works 6 File Converter
(KB943973)


Remote Code Execution


Moderate


None

Microsoft Office 2003 Service Pack 3


Microsoft Works 6 File Converter
(KB943973)


Remote Code Execution


Moderate


None

Microsoft Works 8.0


Microsoft Works 6 File Converter
(KB943973)


Remote Code Execution


Important


None

Microsoft Works Suite 2005


Microsoft Works 6 File Converter
(KB943973)


Remote Code Execution


Important


None

Non-Affected Software
Office Suite

Microsoft Works 8.5

Microsoft Works 9.0

Microsoft Works Suite 2006

2007 Microsoft Office System

Microsoft Office 2000

Microsoft Office XP
Top of sectionTop of section

Frequently Asked Questions (FAQ) Related to This Security Update

What is the Microsoft Works File Converter used for?
The Microsoft Works File Converter is aset of converters that allows Microsoft Office applications to open, edit, and save files in the Works file format supported by Works versions 6, 7, 8, and 9.

What does this update do to address the vulnerabilities discussed in this bulletin?
This update replaces the vulnerable version of the Works File Converter on an affected system with a non-affected version of the converter. However, after this update is installed and the first time a user attempts to open a .wps file, they will be prompted to download the Microsoft Works 6 - 9 Converter from the Microsoft Download Center. Once the Microsoft Works 6 - 9 Converter is installed on a system, the user will not be prompted to install the Microsoft Works 6 - 9 Converter again.

Why doesn’t this update install the Microsoft Works 6–9 File Converter with this bulletin?
The Microsoft Works 6–9 File Converter binaries were not offered through the standard security bulletin process to allow customers the choice of installing the updated version of the converter if they required its functionality.

Will my system be protected if I only install this update and not the Microsoft Works 6–9 File Converter?
Yes, once this update is applied to an affected system, it will be protected from the vulnerabilities discussed in this bulletin regardless if the Microsoft Works 6–9 File Converter is installed.

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

Why does this update address several reported security vulnerabilities?
This update contains updates for several vulnerabilities because the root cause of the issues are similarly related. Instead of having to install several updates that are almost the same, customers need to install this update only.

I am using an older release of the software discussed in this security bulletin. What should I do?
The affected software listed in this bulletin have been tested to determine which releases are affected. Other releases are past their support life cycle. To determine the support life cycle for your software release, visit Microsoft Support Lifecycle.

It should be a priority for customers who have older releases of the software to migrate to supported releases to prevent potential exposure to vulnerabilities. For more information about the Windows Product Lifecycle, visit Microsoft Support Lifecycle. For more information about the extended security update support period for these software versions or editions, visit Microsoft Product Support Services.

Customers who require custom support for older releases 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 Microsoft Worldwide Information, 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.
Top of sectionTop of section
Vulnerability Information

Severity Ratings and Vulnerability Identifiers
Vulnerability Severity Rating and Maximum Security Impact by Affected Software
Office Suite and Other Affected Software Microsoft Works File Converter Input Validation Vulnerability - CVE-2007-0216 Microsoft Works File Converter Index Table Vulnerability - CVE-2008-0105 Microsoft Works File Converter Field Length Vulnerability - CVE-2008-0108 Aggregate Severity Rating

Microsoft Works 6 File Converter on Microsoft Office 2003


Moderate
Remote Code Execution


Moderate
Remote Code Execution


Moderate
Remote Code Execution


Moderate

Microsoft Works 6 File Converter on Microsoft Works 8.0


Important
Remote Code Execution


Important
Remote Code Execution


Important
Remote Code Execution


Important

Microsoft Works 6 File Converter on Microsoft Works Suite 2005


Important
Remote Code Execution


Important
Remote Code Execution


Important
Remote Code Execution


Important
Top of sectionTop of section

Microsoft Works File Converter Input Validation Vulnerability - CVE-2007-0216

A remote code execution vulnerability exists in Microsoft Works File Converter due to the way that it improperly validates section length headers with the .wps format. 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.

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

Mitigating Factors for Microsoft Works File Converter Input Validation Vulnerability - CVE-2008-0216

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:


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 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. Instead, an attacker would have to persuade users to visit the Web site, typically by getting them to click a link in an e-mail message or Instant Messenger message that takes users to the attacker's Web site.


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.
Top of sectionTop of section

Workarounds for Microsoft Works File Converter Input Validation Vulnerability - CVE-2007-0216

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:


Disable installed copies of the Works File Converter by restricting access to WKCVQD01.DLL

To manually restrict access to the WKCVQD01.DLL, run the following commands from the command line:

Note You will need administrator privileges to set these file restrictions.

For Windows XP:

Echo y| cacls "%ProgramFiles%\Common Files\Microsoft shared\TextConv\wkcvqd01.dll" /E /P everyone:N

For Windows Vista:

Takeown.exe /f "%ProgramFiles%\Common Files\Microsoft Shared\TextConv\wkcvqd01.dll"

Icacls.exe "%ProgramFiles%\Common Files\Microsoft Shared\TextConv\wkcvqd01.dll" /save %TEMP%\wkcvqd01 _ACL.TXT

Icacls.exe "%ProgramFiles%\Common Files\Microsoft Shared\TextConv\wkcvqd01.dll" /deny everyone:(F)

Impact of workaround: After applying these changed, users will no longer be able to open Microsoft Works files in Microsoft Office.

Rollback: Run the following commands from a command prompt:

For Windows XP:

cacls "%ProgramFiles%\Common Files\Microsoft Shared\TextConv\wkcvqd01.dll" /E /R everyone

For Windows Vista:

icacls "%ProgramFiles%\Common Files\Microsoft Shared\TextConv\wkcvqd01.dll" /grant everyone:(F)

icacls "%ProgramFiles%\Common Files\Microsoft Shared\TextConv" /restore %TEMP%\wkcvqd01_ACL.TXT


Prevent WKCVQD01.DLL from being installed

To manually restrict WKCVQD01.DLL from being installed, run the following commands from the command line:

Note You will need administrator privileges to set these file restrictions.

For Windows XP:

md "%ProgramFiles%\Common Files\Microsoft Shared\TextConv\"

echo Placeholder > "%ProgramFiles%\Common Files\Microsoft Shared\TextConv\wkcvqd01.dll"

Echo y| cacls "%ProgramFiles%\Common Files\Microsoft Shared\TextConv\wkcvqd01.dll" /E /P everyone:N

For Windows Vista:

md "%ProgramFiles%\Common Files\Microsoft Shared\TextConv\"

echo Placeholder > "%ProgramFiles%\Common Files\Microsoft Shared\TextConv\wkcvqd01.dll"

Icacls.exe "%ProgramFiles%\Common Files\Microsoft Shared\TextConv\wkcvqd01.dll" /deny everyone:(F)

Impact of Workaround: After applying these changes, users will no longer be able to install Microsoft Works File Converters nor open Microsoft Works files in Microsoft Office.

Rollback: Run the following commands from a command prompt:

For Windows XP:

cacls "%ProgramFiles%\Common Files\Microsoft Shared\TextConv\wkcvqd01.dll" /E /R everyone

echo y| del "%ProgramFiles%\Common Files\Microsoft Shared\TextConv\wkcvqd01.dll"

For Windows Vista:

icacls "%ProgramFiles%\Common Files\Microsoft Shared\TextConv\wkcvqd01.dll" /grant everyone:(F)

echo y| del "%ProgramFiles%\Common Files\Microsoft Shared\TextConv\wkcvqd01.dll"


Do not open or save Microsoft Works files that you receive from untrusted sources or that you receive unexpectedly from trusted sources. This vulnerability could be exploited when a user opens a specially crafted file.
Top of sectionTop of section

FAQ for Microsoft Works File Converter Input Validation Vulnerability - CVE-2007-0216

What is the scope of the vulnerability?
This is a remote code execution vulnerability. An attacker who successfully exploited this vulnerability could take complete control of an affected system.

What causes the vulnerability?
The vulnerability is caused by the way that Microsoft Works does not properly validate section length headers in files with the .wps file format.

What might an attacker use the vulnerability to do?
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. 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?
This vulnerability requires that a user open a specially crafted .wps file with an affected version of Microsoft Office, Microsoft Works, or Microsoft Works Suite.

In an e-mail attack scenario, an attacker could exploit the vulnerability by sending a specially-crafted file to the user and by convincing 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 these Web sites. 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 that have affected versions of Microsoft Office, Microsoft Works Suite, or Microsoft Works installed are primarily at risk. Servers could be at more risk if administrators allow users to log on to servers and to run programs. However, best practices strongly discourage allowing this.

What does the update do?
This update replaces the vulnerable version of the Works File Converter on an affected system with a non-affected version of the converter.

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.
Top of sectionTop of section
Top of sectionTop of section

Microsoft Works File Converter Index Table Vulnerability - CVE-2008-0105

A remote code execution vulnerability exists in Microsoft Works File Converter due to the way that it improperly validates section header index table information with the .wps file format. 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.

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

Mitigating Factors for Microsoft Works File Converter Index Table Vulnerability - CVE-2008-0105

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:


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 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. Instead, an attacker would have to persuade users to visit the Web site, typically by getting them to click a link in an e-mail message or Instant Messenger message that takes users to the attacker's Web site.


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.
Top of sectionTop of section

Workarounds for Microsoft Works File Converter Index Table Vulnerability - CVE-2008-0105

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:


Disable installed copies of the Works File Converter by restricting access to WKCVQD01.DLL

To manually restrict access to the WKCVQD01.DLL, run the following commands from the command line:

Note You will need administrator privileges to set these file restrictions.

For Windows XP:

Echo y| cacls "%ProgramFiles%\Common Files\Microsoftshared\TextConv\wkcvqd01.dll" /E /P everyone:N

For Windows Vista:

Takeown.exe /f "%ProgramFiles%\Common Files\Microsoft Shared\TextConv\wkcvqd01.dll"

Icacls.exe "%ProgramFiles%\Common Files\Microsoft Shared\TextConv\wkcvqd01.dll" /save %TEMP%\wkcvqd01 _ACL.TXT

Icacls.exe "%ProgramFiles%\Common Files\Microsoft Shared\TextConv\wkcvqd01.dll" /deny everyone:(F)

Impact of workaround: After applying these changed, users will no longer be able to open Microsoft Works files in Microsoft Office.

Rollback: Run the following commands from a command prompt:

For Windows XP:

cacls "%ProgramFiles%\Common Files\Microsoft Shared\TextConv\wkcvqd01.dll" /E /R everyone

For Windows Vista:

icacls "%ProgramFiles%\Common Files\Microsoft Shared\TextConv\wkcvqd01.dll" /grant everyone:(F)

icacls "%ProgramFiles%\Common Files\Microsoft Shared\TextConv" /restore %TEMP%\wkcvqd01_ACL.TXT


Prevent WKCVQD01.DLL from being installed

To manually restrict WKCVQD01.DLL from being installed, run the following commands from the command line:

Note You will need administrator privileges to set these file restrictions.

For Windows XP:

md "%ProgramFiles%\Common Files\Microsoft Shared\TextConv\"

echo Placeholder > "%ProgramFiles%\Common Files\Microsoft Shared\TextConv\wkcvqd01.dll"

Echo y| cacls "%ProgramFiles%\Common Files\Microsoft Shared\TextConv\wkcvqd01.dll" /E /P everyone:N

For Windows Vista:

md "%ProgramFiles%\Common Files\Microsoft Shared\TextConv\"

echo Placeholder > "%ProgramFiles%\Common Files\Microsoft Shared\TextConv\wkcvqd01.dll"

Icacls.exe "%ProgramFiles%\Common Files\Microsoft Shared\TextConv\wkcvqd01.dll" /deny everyone:(F)

Impact of Workaround: After applying these changes, users will no longer be able to install Microsoft Works File Converters nor open Microsoft Works files in Microsoft Office.

Rollback: Run the following commands from a command prompt:

For Windows XP:

cacls "%ProgramFiles%\Common Files\Microsoft Shared\TextConv\wkcvqd01.dll" /E /R everyone

echo y| del "%ProgramFiles%\Common Files\Microsoft Shared\TextConv\wkcvqd01.dll"

For Windows Vista:

icacls "%ProgramFiles%\Common Files\Microsoft Shared\TextConv\wkcvqd01.dll" /grant everyone:(F)

echo y| del "%ProgramFiles%\Common Files\Microsoft Shared\TextConv\wkcvqd01.dll"

Impact of Workaround: After applying these changes, users will not longer be able to install Microsoft Works File Converters nor open Microsoft Works files in Microsoft Office.


Do not open or save Works files that you receive from untrusted sources or that you receive unexpectedly from trusted sources. This vulnerability could be exploited when a user opens a specially crafted file.
Top of sectionTop of section

FAQ for Microsoft Works File Converter Index Table Vulnerability - CVE-2008-0105

What is the scope of the vulnerability?
This is a remote code execution vulnerability. An attacker who successfully exploited this vulnerability could take complete control of an affected system.

What causes the vulnerability?
The vulnerability is caused by the way that Microsoft Works does not properly validate header index table information with the .wps file format.

What might an attacker use the vulnerability to do?
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. An attacker could then install programs or view, change, or delete data; or create new accounts with full user rights.

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 convincing the user to open the file.

In a Web-based attack scenario, an attacker would have to host a Web site that contains a Office 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 specially crafted 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 that have affected versions of Microsoft Office, Microsoft Works, or Microsoft Works installed are primarily at risk. Servers could be at more risk if administrators allow users to log on to servers and to run programs. However, best practices strongly discourage allowing this.

What does the update do?
This update replaces the vulnerable version of the Works File Converter on an affected system with a non-affected version of the converter.

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.
Top of sectionTop of section
Top of sectionTop of section

Microsoft Works File Converter Field Length Vulnerability - CVE-2008-0108

A remote code execution vulnerability exists in Microsoft Works File Converter due to the way that it improperly validates various filed lengths information with the .wps file format. 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.

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

Mitigating Factors for Microsoft Works File Field Length Vulnerability - CVE-2008-0108

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:


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 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. Instead, an attacker would have to persuade users to visit the Web site, typically by getting them to click a link in an e-mail message or Instant Messenger message that takes users to the attacker's Web site.


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.
Top of sectionTop of section

Workarounds for Microsoft Works File Converter Field Length Vulnerability - CVE-2008-0108

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:


Disabled installed copies of the Works File Converter by restricting access to WKCVQD01.DLL.

To manually restrict access to the WKCVQD01.DLL, run the following commands from the command line:

Note You will need administrator privileges to set these file restrictions.

For Windows XP

Echo y| cacls "%ProgramFiles%\Common Files\Microsoftshared\TextConv\wkcvqd01.dll" /E /P everyone:N

For Windows Vista

Takeown.exe /f "%ProgramFiles%\Common Files\Microsoft Shared\TextConv\wkcvqd01.dll"

Icacls.exe "%ProgramFiles%\Common Files\Microsoft Shared\TextConv\wkcvqd01.dll" /save %TEMP%\wkcvqd01 _ACL.TXT

Icacls.exe "%ProgramFiles%\Common Files\Microsoft Shared\TextConv\wkcvqd01.dll" /deny everyone:(F)

Rollback:

For Windows XP

cacls "%ProgramFiles%\Common Files\Microsoft Shared\TextConv\wkcvqd01.dll" /E /R everyone

For Windows Vista

icacls "%ProgramFiles%\Common Files\Microsoft Shared\TextConv\wkcvqd01.dll" /grant everyone:(F)

icacls "%ProgramFiles%\Common Files\Microsoft Shared\TextConv" /restore %TEMP%\wkcvqd01_ACL.TXT

Impact of Workaround: After applying these changed, users will no longer be able to open Microsoft Works files in Microsoft Office.


Prevent WKCVQD01.DLL from being installed.

To manually restrict WKCVQD01.DLL from being installed, run the following commands from the command line:

Note You will need administrator privileges to set these file restrictions.

For Windows XP

md "%ProgramFiles%\Common Files\Microsoft Shared\TextConv\"

echo Placeholder > "%ProgramFiles%\Common Files\Microsoft Shared\TextConv\wkcvqd01.dll"

Echo y| cacls "%ProgramFiles%\Common Files\Microsoft Shared\TextConv\wkcvqd01.dll" /E /P everyone:N

For Windows Vista

md "%ProgramFiles%\Common Files\Microsoft Shared\TextConv\"

echo Placeholder > "%ProgramFiles%\Common Files\Microsoft Shared\TextConv\wkcvqd01.dll"

Icacls.exe "%ProgramFiles%\Common Files\Microsoft Shared\TextConv\wkcvqd01.dll" /deny everyone:(F)

Rollback:

For Windows XP

cacls "%ProgramFiles%\Common Files\Microsoft Shared\TextConv\wkcvqd01.dll" /E /R everyone

echo y| del "%ProgramFiles%\Common Files\Microsoft Shared\TextConv\wkcvqd01.dll"

For Windows Vista

icacls "%ProgramFiles%\Common Files\Microsoft Shared\TextConv\wkcvqd01.dll" /grant everyone:(F)

echo y| del "%ProgramFiles%\Common Files\Microsoft Shared\TextConv\wkcvqd01.dll"

Impact of Workaround: After applying these changes, users will not longer be able to install Microsoft Works File Converters nor open Microsoft Works files in Microsoft Office.


Do not open or save Works files that you receive from untrusted sources or that you receive unexpectedly from trusted sources. This vulnerability could be exploited when a user opens a specially crafted file.
Top of sectionTop of section

FAQ for Microsoft Works File Converter Field Length Vulnerability - CVE-2008-0108

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

What causes the vulnerability?
The vulnerability is caused by the way that Microsoft Works improperly validates field length information with the .wps file format.

What might an attacker use the vulnerability to do?
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. An attacker could then install programs or view, change, or delete data; or create new accounts with full user rights.

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 convincing the user to open the file.

In a Web-based attack scenario, an attacker would have to host a Web site that contains a Office 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 specially crafted 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 that have affected versions of Microsoft Office, Microsoft Works, or Microsoft Works installed are primarily at risk. Servers could be at more risk if administrators allow users to log on to servers and to run programs. However, best practices strongly discourage allowing this.

What does the update do?
This update replaces the vulnerable version of the Works File Converter on an affected system with a non-affected version of the converter.

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.

Other Information
Acknowledgments

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


VeriSign iDefense VCP for reporting the Microsoft Works Converter Overrun Vulnerability (CVE-2008-0108).


Damian Put working with VeriSign iDefense VCP for reporting the Microsoft Works Heap Corruption Vulnerability (CVE-2007-0216).


IBM Internet Security Systems X-Force for reporting the Microsoft Works File Converter Index Table Vulnerability (CVE-2008-0105).
Top of sectionTop of section
Support


Customers in the U.S. and Canada can receive technical support from Microsoft Product Support Services at 1-866-PCSAFETY. There is no charge for support calls that are associated with security updates.


International customers can receive support from their local Microsoft subsidiaries. There is no charge for support that is associated with security updates. For more information about how to contact Microsoft for support issues, visit the International Support Web site.

Disclaimer

The information provided in the Microsoft Knowledge Base is provided "as is" without warranty of any kind. Microsoft disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Microsoft Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Microsoft Corporation or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply.
Top of sectionTop of section
Revisions


V1.0 (February 12, 2008): Bulletin published.

About | Terms of use | Privacy Policy
© SecurityVulns, 3APA3A, Vladimir Dubrovin
Nizhny Novgorod