|
|
|
|
| |
Credit:
The information has been provided by MS07-030.
The original article can be found at:
Microsoft Security Bulletin MS07-030 - Important
|
| |
Affected Software:
* Microsoft Office 2003
* Microsoft Visio 2003 Service Pack 2
Non-Affected Software:
*2007 Microsoft Office System
*Microsoft Office Visio 2007
Version Number Memory Corruption Vulnerability - CVE-2007-0934:
A remote code execution vulnerability exists in the way Microsoft Visio handles a specially crafted version number in a Visio (.VSD, VSS, or .VST) file. An attacker could exploit this vulnerability when Visio does not correctly validate the version number field when processing the contents of a file. Such a specially crafted file might be included as an e-mail attachment, or hosted on a malicious or compromised Web site.
To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2007-0934.
Mitigating Factors for Version Number Memory Corruption Vulnerability - CVE-2007-0934:
Mitigation refers to a setting, common configuration, or general best-practice, existing in a default state, that could reduce the severity of exploitation of a vulnerability. The following mitigating factors may be helpful in your situation:
* In a Web-based attack scenario, an attacker could host a Web site that contains a Web page that is used to exploit this vulnerability In addition, Web sites that accept or host user-provided content, or compromised Web sites and advertisement servers could contain specially crafted content that could exploit this vulnerability. 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.
* 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 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.
* Microsoft Office Visio 2007 is not affected by this vulnerability.
Workarounds for Version Number Memory Corruption Vulnerability - CVE-2007-0934:
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:
* Use Microsoft Visio Viewer 2003 or Microsoft Visio Viewer 2007 to open and view files. Microsoft Visio Viewer 2003 and Microsoft Visio Viewer 2007 are not affected by the issue. Users can download the Microsoft Visio Viewer 2003 and Microsoft Visio Viewer 2007 from the Microsoft Download Center.
* Do not open or save Microsoft Visio files that you receive from untrusted sources or that you receive unexpectedly from trusted sources.
FAQ for Version Number Memory Corruption Vulnerability - CVE-2007-0934
What is the scope of the vulnerability?
A remote code execution vulnerability exists in Microsoft Visio. An attacker could exploit this vulnerability could remotely 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 impacted than users who operate with administrative user rights.
What causes the vulnerability?
Microsoft Visio does not correctly validate the version number field when processing version related data of a file.
What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could run arbitrary code on a user s system. This could allow an attacker to take complete control of the affected system.
How could an attacker exploit the vulnerability?
This vulnerability requires that a user open a specially crafted Visio file with an affected version of Microsoft Visio.
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 Visio 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 Microsoft Visio 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?
The update removes the vulnerability by modifying the way that Microsoft Visio handles the validation of Visio file version related data.
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.
Visio Document Packaging Vulnerability - CVE-2007-0936:
A remote code execution vulnerability exists in Microsoft Visio as a result of the way it incorrectly handles the parsing of packed objects within the Visio file format. An attacker could exploit this vulnerability by constructing a malicious Visio (.VSD, VSS, or .VST) file that could potentially allow remote code execution if a user visited a malicious Web site or opened a specially crafted Visio attachment included in an e-mail message. An attacker who successfully exploited this vulnerability could take complete control of an affected system.
To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2007-0936.
Mitigating Factors for Visio Document Packaging Vulnerability - CVE-2007-0936:
Mitigation refers to a setting, common configuration, or general best-practice, existing in a default state, that could reduce the severity of exploitation of a vulnerability. The following mitigating factors may be helpful in your situation:
* In a Web-based attack scenario, an attacker could host a Web site that contains a Web page that is used to exploit this vulnerability In addition, Web sites that accept or host user-provided content, or compromised Web sites and advertisement servers could contain specially crafted content that could exploit this vulnerability. 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.
* 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 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.
* Microsoft Office Visio 2007 is not affected by this vulnerability.
Workarounds for Visio Document Packaging Vulnerability - CVE-2007-0936:
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:
* Use Microsoft Visio Viewer 2003 or Microsoft Visio Viewer 2007 to open and view files. Microsoft Visio Viewer 2003 and Microsoft Visio Viewer 2007 are not affected by the issue. Users can download the Microsoft Visio Viewer 2003 and Microsoft Visio Viewer 2007 from the Microsoft Download Center.
* Do not open or save Microsoft Visio 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.
FAQ for Visio Document Packaging Vulnerability - CVE-2007-0936:
What is the scope of the vulnerability?
A remote code execution vulnerability exists in Microsoft Visio. An attacker who successfully exploited this vulnerability could remotely 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 impacted than users who operate with administrative user rights.
What causes the vulnerability?
Visio incorrectly handles the parsing of a packed object resulting in memory corruption.
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?
This vulnerability requires that a user open a specially crafted Visio file with an affected version of Microsoft Visio.
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 Visio 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 Microsoft Visio 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?
The update removes the vulnerability by modifying the way that Visio validates packaging and parsing related data in a Visio file (.VSS, .VSD, or .VST) file.
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.
|
|
|
|
|
