|
|
|
|
| |
Credit:
The information has been provided by Microsoft Security.
The original article can be found at: http://www.microsoft.com/technet/security/Bulletin/MS06-039.mspx
|
| |
Vulnerable Systems:
* Microsoft Office 2003 Service Pack 1 or Service Pack 2 - Download the update (KB914455)
* Microsoft Project 2003
* OneNote 2003
* Microsoft Office XP Service Pack 3 - Download the update (KB914796)
* Microsoft Office 2000 Service Pack 3 - Download the update (KB914797)
* Microsoft Project 2002 - Download the update (KB920102)
* Microsoft Project 2000 - Download the update (KB920101)
* Microsoft Works Suites:
* Microsoft Works Suite 2004 -Download the update (KB914796) (same as the Microsoft Office XP update)
* Microsoft Works Suite 2005 -Download the update (KB914796) (same as the Microsoft Office XP update)
* Microsoft Works Suite 2006 -Download the update (KB914796) (same as the Microsoft Office XP update)
Immune Systems:
* Microsoft Office Viewers
* Microsoft Office 2004 for Mac
* Microsoft Office v. X for Mac
Microsoft Office Remote Code Execution Using a Malformed PNG Vulnerability- CVE-2006-0033:
A remote code execution vulnerability exists in Office and could be exploited when Office opened a malformed PNG file. An attacker could exploit the vulnerability by constructing a specially crafted PNG 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 Office Remote Code Execution Using a Malformed PNG Vulnerability - CVE-2006-0033:
* An attacker who successfully exploited this vulnerability could gain the same user rights as the local user. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.
* The vulnerability can not 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.
* On Office XP and Office 2003, this vulnerability could not be exploited automatically through a Web-based attack scenario. An attacker would have to host a Web site that contains an Office file that is used to attempt 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.
* The default PNG filter provided by the operating system without Office installed is not affected by this vulnerability.
Note Office 2000 does not prompt the user to Open, Save, or Cancel before opening a document.
Workarounds for Microsoft Office Remote Code Execution Using a Malformed PNG Vulnerability - CVE-2006-0033:
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 PNG files that you receive from un-trusted sources or that you received unexpectedly from trusted sources.
This vulnerability could be exploited when a user opens a PNG file.
FAQ for Office Remote Code Execution Using a Malformed PNG Vulnerability - CVE-2006-0033:
What is the scope of the vulnerability?
A remote code execution vulnerability exists in Office and could be exploited when a user opened a malformed PNG file. An attacker could exploit the vulnerability by constructing a specially crafted PNG 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 the Office PNG filter file opens a malformed PNG 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 a Web-based attack scenario, an attacker could host a Web site that contains a PNG file that is used to exploit this vulnerability. In addition, compromised Web sites and Web sites that accept or host user-provided content or advertisements could contain specially crafted content that could exploit this vulnerability. In all cases, however, an attacker would have no way to force users to visit these Web sites. Instead, an attacker would have to persuade users to visit the Web site, typically by getting them to click a link in an e-mail message or instant messenger message that takes users to the attacker's Web site.
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.
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 Office parses a PNG file before it passes it 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.
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 Office Remote Code Execution Using a Malformed GIF Vulnerability- CVE-2006-0007:
A remote code execution vulnerability exists in Office and could be exploited when a user opened a malformed GIF file. An attacker could exploit the vulnerability by constructing a specially crafted GIF file that could allow remote code execution.
If a user is logged on with administrative user rights, an attacker who successfully exploited this vulnerability could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less affected than users who operate with administrative user rights.
Mitigating Factors for Microsoft Office Remote Code Execution Using a Malformed GIF Vulnerability - CVE-2006-0007:
* An attacker who successfully exploited this vulnerability could gain the same user rights as the local user. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.
* The vulnerability can not 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.
* On Office XP and Office 2003, this vulnerability could not be exploited automatically through a Web-based attack scenario. An attacker would have to host a Web site that contains an Office file that is used to attempt 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.
* The default GIF filter provided by the operating system without Office installed is not affected by this vulnerability.
Note Office 2000 does not prompt the user to Open, Save, or Cancel before opening a document.
Workarounds for Microsoft Office Remote Code Execution Using a Malformed GIF Vulnerability - CVE-2006-0007:
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 GIF files that you receive from un-trusted sources or that you received unexpectedly from trusted sources.
This vulnerability could be exploited when a user opens a GIF file.
FAQ for Office Remote Code Execution Using a Malformed GIF Vulnerability - CVE-2006-0007:
What is the scope of the vulnerability?
A remote code execution vulnerability exists in Office, and could be exploited when a malformed string included in an Office file was parsed by any of the affected Office applications. Such a string might be included in an email attachment processed by one of the affected applications or hosted on a malicious web site. Viewing or previewing a malformed email 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 Office 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 Office opens a specially crafted GIF 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 a Web-based attack scenario, an attacker could host a Web site that contains a GIF file that is used to exploit this vulnerability. In addition, compromised Web sites and Web sites that accept or host user-provided content or advertisements could contain specially crafted content that could exploit this vulnerability. In all cases, however, an attacker would have no way to force users to visit these Web sites. Instead, an attacker would have to persuade users to visit the Web site, typically by getting them to click a link in an e-mail message or instant messenger message that takes users to the attacker's Web site.
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.
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 Office parses a PNG file before it passes it 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.
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.
|
|
|
|
|
