Microsoft Security Bulletin MS16-056 - Critical

Security Update for Windows Journal (3156761)

Published: May 10, 2016

Version: 1.0

Executive Summary

This security update resolves a 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 7, Windows 8.1, Windows RT 8.1, and Windows 10. For more information, see the Affected Software section.

The update addresses the vulnerability by modifying how Windows Journal parses Journal files. For more information about the vulnerability, see the Vulnerability Information section.

For more information about this update, see Microsoft Knowledge Base Article 3156761.

Affected Software and Vulnerability Severity Ratings

The following software versions or editions are affected. Versions or editions that are not listed 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.

The severity ratings indicated for each affected software 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 May bulletin summary.

**Affected Software** [**Windows Journal Memory Corruption Vulnerability – CVE-2016-0182**](http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=cve-2016-0182)

Updates Replaced*

Windows Vista

[Windows Vista Service Pack 2](https://www.microsoft.com/download/details.aspx?familyid=cdd0425e-7697-4c30-8805-8759a6f31733) (3155178) **Critical** Remote Code Execution None
[Windows Vista x64 Edition Service Pack 2](https://www.microsoft.com/download/details.aspx?familyid=93d28098-0dc3-46ae-8041-48c2009d4f36) (3155178) **Critical** Remote Code Execution None
**Windows 7**
[Windows 7 for 32-bit Systems Service Pack 1](https://www.microsoft.com/download/details.aspx?familyid=04531128-2a38-4b9f-b63a-a368fc789f0a) (3155178) **Critical** Remote Code Execution None
[Windows 7 for x64-based Systems Service Pack 1](https://www.microsoft.com/download/details.aspx?familyid=44d46d9c-15be-4d89-9328-0c69eebe6eef) (3155178) **Critical** Remote Code Execution None
**Windows 8.1**
[Windows 8.1 for 32-bit Systems](https://www.microsoft.com/download/details.aspx?familyid=71f0cfd3-5f77-4f74-9659-ea14283f0845) (3155178) **Critical** Remote Code Execution None
[Windows 8.1 for x64-based Systems](https://www.microsoft.com/download/details.aspx?familyid=3cfe2d76-a1dc-4665-9404-4e240e54b0c5) (3155178) **Critical** Remote Code Execution None
**Windows RT 8.1**
Windows RT 8.1[1] (3155178) **Critical** Remote Code Execution None
**Windows 10**
[Windows 10 for 32-bit Systems](https://support.microsoft.com/kb/3156387)[2] (3156387) **Critical** Remote Code Execution [3147461](https://support.microsoft.com/kb/3147461)
[Windows 10 for x64-based Systems](https://support.microsoft.com/kb/3156387)[2] (3156387) **Critical** Remote Code Execution [3147461](https://support.microsoft.com/kb/3147461)
[Windows 10 Version 1511 for 32-bit Systems](https://support.microsoft.com/kb/3156421)[2] (3156421) **Critical** Remote Code Execution [3147458](https://support.microsoft.com/kb/3147458)
[Windows 10 Version 1511 for x64-based Systems](https://support.microsoft.com/kb/3156421)[2] (3156421) **Critical** Remote Code Execution [3147458](https://support.microsoft.com/kb/3147458)
[1]Windows RT 8.1 updates are available only via [Windows Update](http://go.microsoft.com/fwlink/?linkid=21130).

[2]Windows 10 updates are cumulative. The monthly security release includes all security fixes for vulnerabilities that affect Windows 10, in addition to non-security updates. The updates are available via the Microsoft Update Catalog.

*The Updates Replaced column shows only the latest update in any chain of superseded updates. For a comprehensive list of updates replaced, go to the Microsoft Update Catalog, search for the update KB number, and then view update details (updates replaced information is provided on the Package Details tab).

Vulnerability Information

Windows Journal Memory Corruption Vulnerability- CVE-2016-0182

A remote code execution vulnerability exists in Microsoft Windows when a specially crafted Journal file is opened in Windows Journal. 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 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.

For an attack to be successful, 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 then convincing the user to open the file. The update addresses the vulnerability by modifying how Windows Journal parses Journal files.

The following table contains links to the standard entry for each vulnerability in the Common Vulnerabilities and Exposures list:

Vulnerability Title CVE number Publicly disclosed Exploited
Windows Journal Memory Corruption Vulnerability CVE-2016-0182 No No
### Mitigating Factors Microsoft has not identified any [mitigating factors](https://technet.microsoft.com/library/security/dn848375.aspx) for this vulnerability. ### Workarounds The following [workarounds](https://technet.microsoft.com/library/security/dn848375.aspx) may be helpful in your situation: - **Do not open suspicious file attachments** 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. On **WindowsVista** or **Windows 7**: 1. Click **Start**, click **Control Panel** and then click **Programs**. 2. Click **Turn Windows Features on or off**. 3. Uncheck **Tablet PC Components** (**Tablet PC Optional Components** on Windows Vista Systems). 4. Click **OK**. **Impact of workaround.**  Users will be unable to use Windows Journal or other Tablet PC Components. **Note** Windows 8.1 does not provide a mechanism to disable Windows Journal. **How to undo the workaround**. 1. Click **Start**, click **Control Panel** and then click **Programs**. 2. Click **Turn Windows Features on or off**. 3. Check **Tablet PC Components** (**Tablet PC Optional Components** on Windows Vista Systems). 4. Click **OK**. - **Remove the .jnt file type association**
**Interactive Method:**  
**Note** Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk. For information about how to edit the registry, view the "Changing Keys And Values" Help topic in Registry Editor (Regedit.exe) or view the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe.

To remove the .jnt file type association using the interactive method, follow these steps:

1.  Click **Start**, click **Run**, type **regedit**, and then click **OK**.  
2.  Expand **HKEY\_CLASSES\_ROOT**, click **jntfile**, and then click the **File** menu and select **Export**.  
3.  In the **Export Registry File** dialog box, type **jntfile HKCR file association registry backup.reg** and click **Save**. This will create a backup of this registry key in the My Documents folder by default.  
4.  Press the **Delete** key on the keyboard to delete the registry key. When prompted to delete the registry value, click **Yes**.  
5.  Expand **HKEY\_CURRENT\_USER**, then **Software**, then **Microsoft**, then **Windows**, then **CurrentVersion**, then **Explorer**, and then **FileExts**.  
6.  Click **.jnt** and then click the **File** menu and select **Export**.  
7.  In the **Export Registry File** dialog box, type **.jntHKCU file association registry backup.reg** and then click **Save**. This will create a backup of this registry key in the My Documents folder by default.  
8.  Press the **Delete** key on the keyboard to delete the registry key. When prompted to delete the registry value, click **Yes**. 
 

**Using a Managed Script:**    
**Note** Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk. For information about how to edit the registry, view the "Changing Keys And Values" Help topic in Registry Editor (Regedit.exe) or view the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe.

To remove the .jnt file type association using an interactive, managed script, follow these steps:

1.  Make a backup copy of the registry keys using a managed deployment script with the following commands: 

    ```
        Regedit.exe /e jntfile_HKCR_registry_backup.reg HKEY_CLASSES_ROOT\jntfile  
        Regedit.exe /e jnt_HKCU_registry_backup.reg HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.jnt
    ```    

2.  Save the following to a file with a .reg extension (e.g., Delete\_jnt\_file\_association.reg): 

    ```
        Windows Registry Editor Version 5.00  
        [-HKEY_CLASSES_ROOT\jntfile]  
        [-HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.jnt]
    ```

3.  Run the above registry script created in step 2 on the target machine with the following command: 

```
    Regedit.exe /s Delete_jnt_file_association.reg
```     

Impact of workaround. Double-clicking a .jnt file will no longer launch journal.exe.

How to undo the workaround:

Restore the registry key by using Registry Editor to restore the settings saved in the .REG files.  

  • Remove Windows Journal by disabling the Windows feature that installs it
    On Windows Vista and Windows 7 systems, follow these steps:

    1. Click Start, click Control Panel, and then click Programs.
    2. Click Turn Windows Features on or off and then clear the check box for either Tablet PC Optional Components (Windows Vista systems) or Tablet PC Components (Windows 7 systems).
    3. Click OK.  

    Impact of workaround. Windows Journal is removed from the system.

    How to undo the workaround:

    To reinstall Windows Journal on Windows Vista or Windows 7 systems, follow these steps:

    1. Click Start, click Control Panel, and then click Programs.
    2. Click Turn Windows Features on or off and then select the check box for either Tablet PC Optional Components (Windows Vista systems) or Tablet PC Components (Windows 7 systems).
    3. Click OK.  
  • Deny access to Journal.exe
    To deny access to Journal.exe, enter the following commands at an administrative command prompt:

        > takeown.exe /f "%ProgramFiles%\Windows Journal\Journal.exe"  
        > icacls.exe "%ProgramFiles%\Windows Journal\Journal.exe" /deny everyone:(F)
    

    Impact of workaround. Windows Journal becomes inaccessible.

    How to undo the workaround:

    To reinstate access to Journal.exe, enter the following commands at an administrative command prompt:

        > icacls.exe "%ProgramFiles%\Windows Journal\Journal.exe" /remove:d everyone
    

Security Update Deployment

For Security Update Deployment information see the Microsoft Knowledge Base article referenced in the Executive Summary.

Acknowledgments

Microsoft recognizes the efforts of those in the security community who help us protect customers through coordinated vulnerability disclosure. See Acknowledgments for more information.

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 (May 10, 2016): Bulletin published.

Page generated 2016-05-05 17:01-07:00.