View Cookie Policy for full details. This module exploits a stack-based buffer overflow in the handling of the 'pFragments' shape property within the Microsoft Word RTF parser. All versions of Microsoft Office , , , and XP prior to the release of the MS bulletin are vulnerable. This module does not attempt to exploit the vulnerability via Microsoft Outlook. With the release of Office , Microsoft began using the Word RTF parser, by default, to handle rich-text messages within Outlook as well.
It was possible to configure Outlook and earlier to use the Microsoft Word engine too, but it was not a default setting. It appears as though Microsoft Office is not vulnerable. It is unlikely that Microsoft will confirm or deny this since Office has reached its support cycle end-of-life.
An attacker who successfully exploited this vulnerability could run arbitrary code as the logged-on user. If a user is logged on with administrative user rights, an attacker 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 PowerPoint 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 PowerPoint 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 convince them to visit the Web site, typically by getting them to click a link that takes them to the attacker's site, and then convince them to open the specially crafted PowerPoint file. What systems are primarily at risk from the vulnerability? Systems where Microsoft PowerPoint is used, including workstations and terminal servers, 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 addresses the vulnerability by changing the way that Microsoft PowerPoint parses specially crafted PowerPoint files. When this security bulletin was issued, had this vulnerability been publicly disclosed?
Microsoft received information about this vulnerability through coordinated vulnerability disclosure. When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited?
Microsoft had not received any information to indicate that this vulnerability had been publicly used to attack customers when this security bulletin was originally issued. To help protect yourself from the e-mail attack vector, read e-mail messages in plain text format.
Microsoft Office Outlook users who have applied Office XP Service Pack 1 or a later version can enable this setting and view in plain text only those e-mail messages that are not digitally signed or e-mail messages that are not encrypted.
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 how to enable this setting in Outlook , see Microsoft Knowledge Base Article E-mail messages that are viewed in plain text format will not contain pictures, specialized fonts, animations, or other rich content. Users who have configured the File Block policy and have not configured a special exempt directory or have not moved files to a trusted location as discussed in Microsoft Knowledge Base Article will be unable to open RTF files in Office or Microsoft Office System.
For Microsoft Office , RTF files will either be blocked from opening or will be opened in protected mode depending on the open behavior that was selected. When Microsoft Office software parses specially crafted RTF-formatted data, system memory may be corrupted in such a way that an attacker could execute arbitrary code. What is RTF? Rich Text Format RTF is a method of encoding formatted text and graphics for use within applications and for transfer between applications.
Users often depend on special translation software to move word-processing documents between various applications developed by different companies. RTF serves as both a standard of data transfer between word processing software, document formatting, and a means of migrating content from one operating system to another.
An attacker who successfully exploited this vulnerability could cause arbitrary code to run with the privileges of the user who opens a specially crafted RTF file or previews or opens a specially crafted RTF e-mail message. If the user is logged on with administrative user rights, an attacker who successfully exploited this vulnerability could take complete control of an affected system.
This vulnerability requires that a user open or preview specially crafted RTF-formatted data with an affected version of Microsoft Office software. In an e-mail attack scenario, an attacker could exploit the vulnerability by sending specially-crafted RTF-formatted data in the contents of an e-mail message. The vulnerability could be exploited when the specially crafted RTF e-mail message is previewed or opened in Outlook while using Word as the e-mail viewer.
An attacker could also exploit the vulnerability by sending a specially-crafted RTF file as an attachment and convincing the user to open the specially crafted RTF file. In a Web-based attack scenario, an attacker could host a Web site that contains an Office file that is used to attempt to exploit this vulnerability. Instead, an attacker would have to convince them to visit the Web site, typically by getting them to click a link that takes them to the attacker's site, and then convince them to open the specially crafted Office file.
How is Microsoft Office affected by this vulnerability? Although the known attack vectors can only leverage Microsoft Word, the vulnerable code exists in a shared component of Microsoft Office. Systems where Microsoft Office software is used, including workstations and terminal servers, are primarily at risk. The update addresses the vulnerability by modifying the way that Microsoft Office parses RTF-formatted data. A remote code execution vulnerability exists in the way that Microsoft Office software parses specially crafted Office files.
Use Microsoft Office File Block policy to block the opening of Office and earlier documents in Microsoft Word from unknown or untrusted sources and locations. For Microsoft Office and Microsoft Office , users who have configured the File Block policy and have not configured a special exempt directory or have not moved files to a trusted location as discussed in Microsoft Knowledge Base Article will be unable to open Office files or earlier versions.
For Microsoft Office , Office files or earlier versions will either be blocked from opening or will be opened in protected mode depending on the open behavior that was selected. Use Microsoft Office File Block policy to block the opening of Office and earlier documents in Microsoft Excel from unknown or untrusted sources and locations. Use Microsoft Office File Block policy to block the opening of Office and earlier documents in Microsoft PowerPoint from unknown or untrusted sources and locations.
Note In order to use 'FileOpenBlock' with the Microsoft Office system, all of the latest security updates for the Microsoft Office system must be applied. Do not open Office files that you receive from untrusted sources or that you receive unexpectedly from trusted sources. When a user opens a specially crafted Office file, system memory may become corrupted in such a way that an attacker could execute arbitrary code.
If a user is logged-on with administrative user rights, an attacker could take complete control of the affected system. This vulnerability requires that a user open a specially crafted Office file with an affected version of Microsoft Office software.
In an e-mail attack scenario, an attacker could exploit the vulnerability by sending a specially crafted Office file to the user and by convincing the user to open the file. The update addresses the vulnerability by modifying the way that Microsoft Office software parses files.
The update addresses the vulnerability by modifying the way that Microsoft Office parses Office files. The update addresses the vulnerability by modifying the way that Microsoft Office parses files. A remote code execution vulnerability exists in the way that Microsoft Office handles the loading of DLL files.
Note See Microsoft Knowledge Base Article to deploy a workaround tool that allows customers to disable the loading of libraries from remote network or WebDAV shares. This tool can be configured to disallow insecure loading on a per-application or a global system basis.
Customers who are informed by their vendor of an application being vulnerable can use this tool to help protect against attempts to exploit this issue. Note that this Fix it solution does require you to install the workaround tool also described in Microsoft Knowledge Base Article first.
This Fix it solution only deploys the registry key and requires the workaround tool in order to be effective. We recommend that administrators review the KB article closely prior to deploying this Fix it solution. Disabling the WebClient service helps protect affected systems from attempts to exploit this vulnerability by blocking the most likely remote attack vector through the Web Distributed Authoring and Versioning WebDAV client service.
After applying this workaround it is still possible for remote attackers who successfully exploit this vulnerability to cause Microsoft Office Outlook to run programs located on the targeted user's computer or the Local Area Network LAN , but users will be prompted for confirmation before opening arbitrary programs from the Internet.
In addition, any services that explicitly depend on the Web Client service will not start, and an error message will be logged in the System log. For example, WebDAV shares will be inaccessible from the client computer. These ports are used to initiate a connection with the affected component.
Blocking TCP ports and at the firewall will help protect systems that are behind that firewall from attempts to exploit this vulnerability. Microsoft recommends that you block all unsolicited inbound communication from the Internet to help prevent attacks that may use other ports. Several Windows services use the affected ports. Blocking connectivity to the ports may cause various applications or services to not function. Some of the applications or services that could be impacted are listed below:.
Unblock TCP ports and at the firewall. This vulnerability requires a user to open a document contained within the same working directory as a specially crafted DLL file. The specially crafted DLL will be loaded into memory giving the attacker control of the affected system in the security context of the logged-on user. Is this vulnerability related to the issue described in Microsoft Security Advisory ? Yes, this vulnerability is related to the class of vulnerabilities that affect how applications load external libraries described in Microsoft Security Advisory This security bulletin addresses a particular instance of this type of vulnerability.
This vulnerability requires that a user open an office document in the same working directory as a specially crafted DLL file. In an e-mail attack scenario, an attacker could exploit the vulnerability by convincing a user to place an Office file in the same folder as a specially crafted DLL file, and then convincing the user to open the Office file.
When the user opens the Office file the specially crafted DLL file, which is contained in the same directory as the Office file, will be loaded. Systems where Microsoft Office is used, including workstations and terminal servers, are primarily at risk.
Although the known attack vectors can only leverage Microsoft PowerPoint, the vulnerable code exists in a shared component of Microsoft Office. This update addresses the vulnerability by helping to ensure the vulnerable component of Microsoft Office uses a more appropriate and secure search order when loading libraries.
This vulnerability had been publicly disclosed when this security bulletin was originally issued. Manage the software and security updates you need to deploy to the servers, desktop, and mobile systems in your organization.
Security updates are available from Microsoft Update and Windows Update. Security updates are also available from the Microsoft Download Center. You can find them most easily by doing a keyword search for "security update. Finally, security updates can be downloaded from the Microsoft Update Catalog.
The Microsoft Update Catalog provides a searchable catalog of content made available through Windows Update and Microsoft Update, including security updates, drivers and service packs. By searching using the security bulletin number such as, "MS" , you can add all of the applicable updates to your basket including different languages for an update , and download to the folder of your choosing.
Microsoft provides detection and deployment guidance for security updates. This guidance contains recommendations and information that can help IT professionals understand how to use various tools for detection and deployment of security updates. For more information, see Microsoft Knowledge Base Article Microsoft Baseline Security Analyzer MBSA allows administrators to scan local and remote systems for missing security updates as well as common security misconfigurations.
Windows Server Update Services WSUS enables information technology administrators to deploy the latest Microsoft product updates to computers that are running the Windows operating system. For SMS 2. See also Downloads for Systems Management Server 2. See also Downloads for Systems Management Server For more detailed information, see Microsoft Knowledge Base Article : Summary list of monthly detection and deployment guidance articles.
For more information, see the Office Administrative Installation Point heading in this section. If you installed your application from a server location, the server administrator must update the server location with the administrative update and deploy that update to your system. Updates often write to the same files and registry settings required for your applications to run. This can trigger incompatibilities and increase the time it takes to deploy security updates.
You can streamline testing and validating Windows updates against installed applications with the Update Compatibility Evaluator components included with Application Compatibility Toolkit. The Application Compatibility Toolkit ACT contains the necessary tools and documentation to evaluate and mitigate application compatibility issues before deploying Microsoft Windows Vista, a Windows Update, a Microsoft Security Update, or a new version of Windows Internet Explorer in your environment.
For information about the specific security update for your affected software, click the appropriate link:. The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information , in this section.
0コメント