Security Bulletin

Microsoft Security Bulletin MS13-078 - Important

Vulnerability in FrontPage Could Allow Information Disclosure (2825621)

Published: September 10, 2013

Version: 1.0

General Information

Executive Summary

This security update resolves a privately reported vulnerability in Microsoft FrontPage. The vulnerability could allow information disclosure if a user opens a specially crafted FrontPage document. The vulnerability cannot be exploited automatically; for an attack to be successful a user must be convinced to open the specially crafted document.

This security update is rated Important for all supported editions of Microsoft FrontPage 2003. For more information, see the subsection, Affected and Non-Affected Software, in this section.

The security update addresses the vulnerability by ensuring that FrontPage properly handles Document Type Definition (DTD) entities. 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. Customers can configure automatic updating to check online for updates from Microsoft Update by using the Microsoft Update service. Customers who have automatic updating enabled and configured to check online for updates from Microsoft Update typically will not need to take any action because this security update will be downloaded and installed automatically. Customers who have not enabled automatic updating need to check for updates from Microsoft Update and install this update manually. For information about specific configuration options in automatic updating, see Microsoft Knowledge Base Article 294871.

For administrators and enterprise installations, or end users who want to install this security update manually, Microsoft recommends that customers apply the update at the earliest opportunity using update management software, or by checking for updates using the Microsoft Update service.

See also the section, Detection and Deployment Tools and Guidance, later in this bulletin.

Knowledge Base Article

Knowledge Base Article 2825621
File information Yes
SHA1/SHA2 hashes Yes
Known issues None

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, see Microsoft Support Lifecycle.

Productivity Software

Affected Software Maximum Security Impact Aggregate Severity Rating Updates Replaced
FrontPage 2003
[Microsoft FrontPage 2003 Service Pack 3]( (2825621) Information Disclosure Important None
**Non-Affected Software**
Office and Other Software
Microsoft SharePoint Designer 2007 Service Pack 3
Microsoft SharePoint Designer 2010 Service Pack 1
Microsoft SharePoint Designer 2010 Service Pack 2
Microsoft SharePoint Designer 2013

Update FAQ

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 has been tested to determine which releases are affected. Other releases are past their support life cycle. For more information about the product lifecycle, see the Microsoft Support Lifecycle website.

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. To determine the support lifecycle for your software release, see Select a Product for Lifecycle Information. For more information about service packs for these software releases, see Service Pack Lifecycle Support Policy.

Customers who require custom support for older software 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, see the Microsoft Worldwide Information website, select the country in the Contact Information list, 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 Microsoft Support Lifecycle Policy FAQ.

Vulnerability Information

Severity Ratings and Vulnerability Identifiers

The following severity ratings assume the potential maximum impact of the vulnerability. For information regarding the likelihood, within 30 days of this security bulletin's release, of the exploitability of the vulnerability in relation to its severity rating and security impact, please see the Exploitability Index in the September bulletin summary. For more information, see Microsoft Exploitability Index.

Vulnerability Severity Rating and Maximum Security Impact by Affected Software
Affected Software XML Disclosure Vulnerability - CVE-2013-3137 Aggregate Severity Rating
FrontPage 2003
Microsoft FrontPage 2003 Service Pack 3 **Important** Information Disclosure **Important**

XML Disclosure Vulnerability – CVE-2013-3137

An information disclosure vulnerability exists in FrontPage that could allow an attacker to disclose the contents of a file on a target system.

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

Mitigating Factors

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:

  • The vulnerability cannot be exploited automatically through email. For an attack to be successful a user must open an attachment that is sent in an email message.
  • In a web-based attack scenario, an attacker could host a website that contains a webpage that is used to exploit the vulnerability. In addition, compromised websites and websites that accept or host user-provided content or advertisements could contain specially crafted content that could exploit the vulnerability. In all cases, however, an attacker would have no way to force users to visit these websites. Instead, an attacker would have to convince users to visit the website, typically by getting them to click a link in an email message or Instant Messenger message that takes users to the attacker's website, and then convince them to open a specially crafted FrontPage file.


Microsoft has not identified any workarounds for this vulnerability.


What is the scope of the vulnerability?
This is an information disclosure vulnerability.

What causes the vulnerability?
The vulnerability is caused when Microsoft FrontPage improperly parses the DTD of an XML file.

What is DTD?
DTD, standing for document type definition, is a file format type that is used in XML and other markup languages to identify the markup to be used to format a document.

What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could disclose the contents of a local file on a target system.

How could an attacker exploit the vulnerability?
In an attack scenario, the attacker could convince a user to open a specially crafted FrontPage document.

What systems are primarily at risk from the vulnerability?
Any systems running the affected edition of FrontPage are affected by this vulnerability.

What does the update do?
The update addresses the vulnerability by ensuring that FrontPage properly handles DTD entities.

When this security bulletin was issued, had this vulnerability been publicly disclosed?
No. 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?
No. 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.

Update Information

Detection and Deployment Tools and Guidance

Several resources are available to help administrators deploy security updates.

  • Microsoft Baseline Security Analyzer (MBSA) lets administrators scan local and remote systems for missing security updates and common security misconfigurations.
  • Windows Server Update Services (WSUS), Systems Management Server (SMS), and System Center Configuration Manager help administrators distribute security updates.
  • The Update Compatibility Evaluator components included with Application Compatibility Toolkit aid in streamlining the testing and validation of Windows updates against installed applications.

For more information about these tools and guidance in deploying security updates across networks, see Security Tools for IT Pros.

Security Update Deployment

Affected Software

For information about the specific security update for your affected software, click the appropriate link:

FrontPage 2003 (all editions)

Reference Table

The following table contains the security update information for this software.

Security update file name office2003-kb2825621-fullfile-enu.exe
Installation switches See Microsoft Knowledge Base Article 197147
Restart requirement In some cases, this update does not require a restart. If the required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart.

To help reduce the chance that a restart will be required, stop all affected services and close all applications that may use the affected files prior to installing the security update. For more information about the reasons why you may be prompted to restart, see Microsoft Knowledge Base Article 887012.
Removal information Use Add or Remove Programs item in Control Panel.

Note When you remove this update, you may be prompted to insert the Microsoft Office 2003 CD in the CD drive. Additionally, you may not have the option to uninstall the update from the Add or Remove Programs item in Control Panel. There are several possible causes for this issue. For more information about the removal, see Microsoft Knowledge Base Article 903771.
File information See Microsoft Knowledge Base Article 2825621
Registry key verification Not applicable
### Other Information #### Acknowledgments Microsoft [thanks]( the following for working with us to help protect customers: - Timur Yunusov of [Positive Technologies]( for reporting the XML Disclosure Vulnerability (CVE-2013-3137) #### Microsoft Active Protections Program (MAPP) To improve security protections for customers, Microsoft provides vulnerability information to major security software providers in advance of each monthly security update release. Security software providers can then use this vulnerability information to provide updated protections to customers via their security software or devices, such as antivirus, network-based intrusion detection systems, or host-based intrusion prevention systems. To determine whether active protections are available from security software providers, please go to the active protections websites provided by program partners, listed in [Microsoft Active Protections Program (MAPP) Partners]( #### Support **How to obtain help and support for this security update** - Help installing updates: [Support for Microsoft Update]( - Security solutions for IT professionals: [TechNet Security Troubleshooting and Support]( - Help protect your computer that is running Windows from viruses and malware: [Virus Solution and Security Center]( - Local support according to your country: [International Support]( #### 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. #### Revisions - V1.0 (September 10, 2013): Bulletin published. *Built at 2014-04-18T13:49:36Z-07:00*