Description of the security update for Outlook 2013: June 12, 2018

Applies to: Microsoft Office 2013 Service Pack 1


This security update resolves vulnerabilities in Microsoft Office that could allow remote code execution if a user opens a specially crafted Office file. To learn more about these vulnerabilities, see Microsoft Common Vulnerabilities and Exposures CVE-2018-8244.

Note To apply this security update, you must have the release version of Service Pack 1 for Microsoft Office 2013 installed on the computer.

Be aware that the update in the Microsoft Download Center applies to the Microsoft Installer (.msi)-based edition of Office 2013. It doesn't apply to the Office 2013 Click-to-Run editions, such as Microsoft Office 365 Home (see Determining your Office version).

Improvements and fixes

This security update contains improvements and fixes for the following nonsecurity issues:
  • If the PR_EMSMDB_CRED_USERNAME property is not present in user profiles, some users may experience too many calls to the user principal name (UPN) lookup. To fix this issue, follow the instructions in KB 4022165.
  • This update adds AES 256 encryption as a supported scheme when Outlook 2013 is in FIPS compliant mode.

  • When you use Outlook 2013 to forward a meeting request that is created in Outlook 2016, the attachment is missing if the AllowHTMLCalendarContent registry key value is set to 1.

  • After you install or update an Outlook add-in in Outlook 2013, multiple network calls (getAppManifest calls) are made to retrieve Exchange add-in manifest data.

  • This update adds translations in all languages for the fix of an issue that caused recipients to be unable to see attachments on meeting requests sent with attachments.

How to get and install the update

Method 1: Microsoft Update

This update is available from Microsoft Update. When you turn on automatic updating, this update will be downloaded and installed automatically. For more information about how to get security updates automatically, see Windows Update: FAQ.

Method 2: Microsoft Update Catalog

To get the stand-alone package for this update, go to the Microsoft Update Catalog website.

Method 3: Microsoft Download Center

You can get the stand-alone update package through the Microsoft Download Center. Follow the installation instructions on the download page to install the update.

More Information

Changes to KB 4022169

Security update deployment information

For deployment information about this update, see security update deployment information: June 12, 2018.

Security update replacement information

This security update replaces previously released security update KB 4011697.

File hash information

File name SHA1 hash SHA256 hash
outlook2016-kb4022160-fullfile-x86-glb.exe 41A03401ADF30D52F7D2E1B5E4AAB8699D77F1AA 34C63C72D86F8D1A1520F9D2F4281ADE4A1CE9B2BE74ABD8BF982477135759EB
outlook2016-kb4022160-fullfile-x64-glb.exe D130E5ED1390B5835BB0C1F532970C7942AB1C92 2AFDFC5D5A1D61C57A5A4F9144C3971AB03A623532DF30F38DC68AEF2A19FA1F


File information

The English (United States) version of this software update installs files that have the attributes that are listed in the following tables. The dates and times for these files are listed in Coordinated Universal Time (UTC). The dates and times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and times may change when you perform certain operations on the files.

How to get help and support for this security update

How to get help and support for this security update

Help for installing updates: Windows Update: FAQ

Security solutions for IT professionals: TechNet Security Support and Troubleshooting

Help for protecting your Windows-based computer from viruses and malware: Microsoft Secure

Local support according to your country: International Support

ERROR: at System.Diagnostics.Process.GetProcessHandle(Int32 access, Boolean throwIfExited) at System.Diagnostics.Process.Kill() at Microsoft.Support.SEOInfrastructureService.PhantomJS.PhantomJSRunner.WaitForExit(Process process, Int32 waitTime, StringBuilder dataBuilder, Boolean isTotalProcessTimeout)New URL: about:blank