Export (0) Print
Expand All

Microsoft Security Bulletin MS14-038 - Critical

Vulnerability in Windows Journal Could Allow Remote Code Execution (2975689)

Published: July 8, 2014

Version: 1.0

General Information

Executive Summary

This security update resolves a privately reported vulnerability in Microsoft Windows. The vulnerability could allow remote code execution if a user opens a specially crafted Journal file. 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.

This security update is rated Critical for all supported editions of Windows Vista, Windows Server 2008 (excluding Itanium), Windows 7, Windows Server 2008 R2 (excluding Itanium), Windows 8, Windows Server 2012, Windows RT, Windows 8.1, Windows Server 2012 R2, and Windows RT 8.1. For more information, see the Affected and Non-Affected Software section.

The security update addresses the vulnerability by modifying the way that Windows Journal parses Journal files. For more information about the vulnerability, see the Frequently Asked Questions (FAQ) subsection for the specific vulnerability later in this bulletin.

Recommendation.  Most customers have automatic updating enabled and will not need to take any action because this security update will be downloaded and installed automatically. For information about specific configuration options in automatic updating, see Microsoft Knowledge Base Article 294871. For customers who do not have automatic updating enabled, the steps in Turn automatic updating on or off can be used to enable automatic updating.

For enterprise installations, or administrators and end users who want to install this security update manually (including customers who have not enabled automatic updating), Microsoft recommends that customers apply the update immediately using update management software, or by checking for updates using the Microsoft Update service. The updates are also available via the download links in the Affected Software table later in this bulletin.

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

Knowledge Base Article

  • Knowledge Base Article: 2975689
  • File Information: Yes
  • SHA1/SHA2 hashes: Yes
  • Known issues: None

 

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.

Affected Software 

Operating System

Maximum Security Impact

Aggregate Severity Rating

Updates Replaced

Windows Vista

Windows Vista Service Pack 2
(Journal)
(2971850)

Remote Code Execution

Critical

2835364 in MS13-054

Windows Vista x64 Edition Service Pack 2
(Journal)
(2971850)

Remote Code Execution

Critical

2835364 in MS13-054

Windows Server 2008

Windows Server 2008 for 32-bit Systems Service Pack 2
(Journal)
(2971850)

Remote Code Execution

Critical

2835364 in MS13-054

Windows Server 2008 for x64-based Systems Service Pack 2
(Journal)
(2971850)

Remote Code Execution

Critical

2835364 in MS13-054

Windows 7

Windows 7 for 32-bit Systems Service Pack 1
(Journal)
(2971850)

Remote Code Execution

Critical

2835364 in MS13-054

Windows 7 for x64-based Systems Service Pack 1
(Journal)
(2971850)

Remote Code Execution

Critical

2835364 in MS13-054

Windows Server 2008 R2

Windows Server 2008 R2 for x64-based Systems Service Pack 1
(Journal)
(2971850)

Remote Code Execution

Critical

2835364 in MS13-054

Windows 8 and Windows 8.1

Windows 8 for 32-bit Systems
(Journal)
(2971850)

Remote Code Execution

Critical

2835364 in MS13-054

Windows 8 for x64-based Systems
(Journal)
(2971850)

Remote Code Execution

Critical

2835364 in MS13-054

Windows 8.1 for 32-bit Systems [1]
(Journal)
(2971850)

Remote Code Execution

Critical

None

Windows 8.1 for 32-bit Systems[2]
(Journal)
(2974286)

Remote Code Execution

Critical

None

Windows 8.1 for x64-based Systems [1]
(Journal)
(2971850)

Remote Code Execution

Critical

None

Windows 8.1 for x64-based Systems[2]
(Journal)
(2974286)

Remote Code Execution

Critical

None

Windows Server 2012 and Windows Server 2012 R2

Windows Server 2012
(Journal)
(2971850)

Remote Code Execution

Critical

2835364 in MS13-054

Windows Server 2012 R2 [1]
(Journal)
(2971850)

Remote Code Execution

Critical

None

Windows Server 2012 R2[2]
(Journal)
(2974286)

Remote Code Execution

Critical

None

Windows RT and Windows RT 8.1

Windows RT[3]
(Journal)
(2971850)

Remote Code Execution

Critical

2835364 in MS13-054

Windows RT 8.1[1][3]
(Journal)
(2971850)

Remote Code Execution

Critical

None

[1]This update is for systems that have the 2919355 update installed. See the Update FAQ for more information.

[2]This update is for systems that do not have the 2919355 update installed. This update is not available via the Microsoft Download Center. See the Update FAQ for more information.

[3]This update is available via Windows Update.

 

Non-Affected Software

Operating System

Windows Server 2003 Service Pack 2

Windows Server 2003 x64 Edition Service Pack 2

Windows Server 2003 with SP2 for Itanium-based Systems

Windows Server 2008 for Itanium-based Systems Service Pack 2

Windows Server 2008 R2 for Itanium-based Systems Service Pack 1

Server Core installation option

Windows Server 2008 for 32-bit Systems Service Pack 2 (Server Core installation)

Windows Server 2008 for x64-based Systems Service Pack 2 (Server Core installation

Windows Server 2008 R2 for x64-based Systems Service Pack 1 (Server Core installation

Windows Server 2012 (Server Core installation)

Windows Server 2012 R2 (Server Core installation)

 

There are multiple update packages listed for Windows 8.1 and Windows Server 2012 R2. Do I need to install all the updates listed in the Affected Software table for the software? 
No. Depending on how your system is configured to receive updates, only one of the updates for Windows 8.1 or Windows Server 2012 will apply.

For systems running 8.1 or Windows Server 2012 R2:

  • Update 2971850 is for systems that already have the 2919355 (Windows 8.1 Update) update installed.
  • Update 2974286 is for systems without the 2919355 update installed. Note that the 2974286 update is only available for customers managing updates using Windows Server Update Services (WSUS), Windows Intune, or System Center Configuration Manager.

For Windows 8.1, Windows Server 2012 R2, and Windows RT 8.1 are there any prerequisites for the 2971850 update? 
Yes. Customers running Windows 8.1, Windows Server 2012 R2, or Windows RT 8.1 must first install the 2919355 (Windows 8.1 Update) update released in April, 2014 before installing the 2971850 update. For more information about the prerequisite update, see Microsoft Knowledge Base Article 2919355.

I am running one of the operating systems that is listed in the affected software table. Why am I not being offered the Journal update? 
The update will only be offered to systems on which the affected component (Journal) is installed.

Note On supported editions of Windows Server 2008, Journal is not installed by default. On this operating system, the update for Journal only applies if Desktop Experience feature is enabled.

Note On supported editions of Windows Server 2008 R2 the update for Journal only applies if the Ink and Handwriting Services feature is enabled.

Note On supported editions of Windows Server 2012 the update for Journal only applies if the Ink and Handwriting Services feature is enabled.

Note On supported editions of Windows Server 2012 R2 the update for Journal only applies if the Ink and Handwriting Services feature is enabled.

How are Server Core installations affected by the vulnerabilities addressed in this bulletin? 
The vulnerabilities addressed by this update do not affect supported editions of Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, or Windows Server 2012 R2 as indicated in the Non-Affected Software table, when installed using the Server Core installation option. For more information on this installation option, see the TechNet articles, Managing a Server Core Installation: Overview, Servicing a Server Core Installation, and Server Core and Full Server Integration Overview.

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.

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 July bulletin summary. For more information, see Microsoft Exploitability Index.

Vulnerability Severity Rating and Maximum Security Impact by Affected Software

Affected Software

Windows Journal Remote Code Execution Vulnerability - CVE-2014-1824

Aggregate Severity Rating

Windows Vista

Windows Vista Service Pack 2

Critical 
Remote Code Execution

Critical

Windows Vista x64 Edition Service Pack 2

Critical 
Remote Code Execution

Critical

Windows Server 2008

Windows Server 2008 for 32-bit Systems Service Pack 2

Critical 
Remote Code Execution

Critical

Windows Server 2008 for x64-based Systems Service Pack 2

Critical 
Remote Code Execution

Critical

Windows 7

Windows 7 for 32-bit Systems Service Pack 1

Critical 
Remote Code Execution

Critical

Windows 7 for x64-based Systems Service Pack 1

Critical 
Remote Code Execution

Critical

Windows Server 2008 R2

Windows Server 2008 R2 for x64-based Systems Service Pack 1

Critical 
Remote Code Execution

Critical

Windows 8 and Windows 8.1

Windows 8 for 32-bit Systems

Critical 
Remote Code Execution

Critical

Windows 8 for x64-based Systems

Critical 
Remote Code Execution

Critical

Windows 8.1 for 32-bit systems

Critical 
Remote Code Execution

Critical

Windows 8.1 for x64-based systems

Critical 
Remote Code Execution

Critical

Windows Server 2012 and Windows Server 2012 R2

Windows Server 2012

Critical 
Remote Code Execution

Critical

Windows Server 2012 R2

Critical 
Remote Code Execution

Critical

Windows RT and Windows RT 8.1

Windows RT

Critical 
Remote Code Execution

Critical

Windows RT 8.1

Critical 
Remote Code Execution

Critical

 

A remote code execution vulnerability exists in the way that Windows Journal parses specially crafted files. The vulnerability could lead to remote code execution if a user opens a specially crafted Journal file. If a user is logged on with administrative 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 impacted than users who operate with administrative user rights.

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

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:

  • 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.

Workarounds

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:

  • Do not open Windows Journal (.jnt) files that you receive from untrusted sources or that you receive unexpectedly from trusted sources

    Do not open Windows Journal (.jnt) 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

What is the scope of the vulnerability? 
This is a remote code execution vulnerability.

What causes the vulnerability? 
The vulnerability is caused when a specially crafted Journal file is opened in Windows Journal. The subsequent parsing of the file causes the Journal program to crash in 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 cause arbitrary code to execute in the context of the current user. 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 Journal file with an affected version of Windows Journal.

In an email attack scenario, an attacker could exploit the vulnerability by sending a specially crafted Journal 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 website that contains a Journal file that is used to attempt to exploit this vulnerability. In addition, compromised websites and websites 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 website that contains a specially crafted Journal file. Instead, an attacker would have to convince them to visit the website, 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 Journal file.

What systems are primarily at risk from the vulnerability? 
Systems where Windows Journal 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? 
The update addresses the vulnerability by modifying the way that Windows Journal parses Journal files.

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.

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 information about these and other tools that are available, see Security Tools for IT Pros

Windows Vista (all editions)

Reference Table

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

Security update file names

For all supported 32-bit editions of Windows Vista:
Windows6.0-KB2971850-x86.msu

 

For all supported x64-based editions of Windows Vista:
Windows6.0-KB2971850-x64.msu

Installation switches

See Microsoft Knowledge Base Article 934307

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.

Removal information

WUSA.exe does not support uninstall of updates. To uninstall an update installed by WUSA, click Control Panel, and then click Security. Under Windows Update, click View installed updates and select from the list of updates.

File information

See Microsoft Knowledge Base Article 2971850

Registry key verification

Note A registry key does not exist to validate the presence of this update.

 

Windows Server 2008 (all editions)

Reference Table

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

Security update file names

For all supported 32-bit editions of Windows Server 2008:
Windows6.0-KB2971850-x86.msu

 

For all supported x64-based editions of Windows Server 2008:
Windows6.0-KB2971850-x64.msu

Installation switches

See Microsoft Knowledge Base Article 934307

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.

Removal information

WUSA.exe does not support uninstall of updates. To uninstall an update installed by WUSA, click Control Panel, and then click Security. Under Windows Update, click View installed updates and select from the list of updates.

File information

See Microsoft Knowledge Base Article 2971850

Registry key verification

Note A registry key does not exist to validate the presence of this update.

 

Windows 7 (all editions)

Reference Table

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

Security update file name

For all supported 32-bit editions of Windows 7:
Windows6.1-KB2971850-x86.msu

 

For all supported x64-based editions of Windows 7:
Windows6.1-KB2971850-x64.msu

Installation switches

See Microsoft Knowledge Base Article 934307

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.

Removal information

To uninstall an update installed by WUSA, use the /Uninstall setup switch or click Control Panel, click System and Security, and then under Windows Update, click View installed updates and select from the list of updates.

File information

See Microsoft Knowledge Base Article 2971850

Registry key verification

Note A registry key does not exist to validate the presence of this update.

 

Windows Server 2008 R2 (all editions)

Reference Table

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

Security update file name

For all supported x64-based editions of Windows Server 2008 R2:
Windows6.1-KB2971850-x64.msu

Installation switches

See Microsoft Knowledge Base Article 934307

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.

Removal information

To uninstall an update installed by WUSA, use the /Uninstall setup switch or click Control Panel, click System and Security, and then under Windows Update, click View installed updates and select from the list of updates.

File information

See Microsoft Knowledge Base Article 2971850

Registry key verification

Note A registry key does not exist to validate the presence of this update.

 

Windows 8 and Windows 8.1 (all editions)

Reference Table

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

Security update file name

For all supported 32-bit editions of Windows 8:
Windows8-RT-KB2971850-x86.msu


For all supported x64-based editions of Windows 8:
Windows8-RT-KB2971850-x64.msu


For all supported 32-bit editions of Windows 8.1:
Windows8.1-KB2971850-x86.msu


For all supported x64-based editions of Windows 8.1:
Windows8.1-KB2971850-x64.msu

Installation switches

See Microsoft Knowledge Base Article 934307

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.

Removal information

To uninstall an update installed by WUSA, use the /Uninstall setup switch or click Control Panel, click System and Security, click Windows Update, and then under See also, click Installed updates and select from the list of updates.

File information

See Microsoft Knowledge Base Article 2971850

Registry key verification

Note A registry key does not exist to validate the presence of this update.

 

Windows Server 2012 and Windows Server 2012 R2 (all editions)

Reference Table

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

Security update file name

For all supported editions of Windows Server 2012:
Windows8-RT-KB2971850-x64.msu

 

For all supported editions of Windows Server 2012 R2:
Windows8.1-KB2971850-x64.msu

Installation switches

See Microsoft Knowledge Base Article 934307

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.

Removal information

To uninstall an update installed by WUSA, use the /Uninstall setup switch or click Control Panel, click System and Security, click Windows Update, and then under See also, click Installed updates and select from the list of updates.

File information

See Microsoft Knowledge Base Article 2971850

Registry key verification

Note A registry key does not exist to validate the presence of this update.

 

Windows RT and Windows RT 8.1 (all editions)

Reference Table

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

Deployment

These updates are available via Windows Update only.

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.

Removal Information

Click Control Panel, click System and Security, click Windows Update, and then under See also, click Installed updates and select from the list of updates.

File Information

See Microsoft Knowledge Base Article 2971850

 

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

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

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 (July 8, 2014): Bulletin published.

Page generated 2014-07-01 16:02Z-07:00.
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2015 Microsoft