Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

MS17-014: Description of the security update for SharePoint Foundation 2013: March 14, 2017

View products that this article applies to.


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 Security Bulletin MS17-014.

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

For a complete list of affected versions of Microsoft Office software, see Microsoft Knowledge Base article 4013241.

↑ Back to the top

Improvements and fixes

This security update contains improvements and fixes for the following nonsecurity issues:

  • When you browse to the action links of a question or answer (such as the Edit or Reply link) in a discussions list, no context of that message appear in the action links. Therefore, screen readers can't detect the context of the message that you focus on. The update adds a simple text string to all action links that are part of the message body.
  • In an announcements list, the email attachment of an email item is lost if the attached .eml file title contains specific characters.
  • After you enter and format text in a table of a content editor web part in a site in Internet Explorer, Internet Explorer scrolls the page unexpectedly.
  • If your permission isn't enabled on the Manage Permissions page, you don't receive email notification as expected even if you are granted permissions.
  • When you try to apply a filter to a list view, you receive the following error message if this view is grouped by a calculated column:

SqlError: 'ORDER BY items must appear in the select list if SELECT DISTINCT is specified.

  • After you migrate from classic-mode to claims-based authentication in Microsoft SharePoint 2013, you receive an exception when you try to access the SPFileVersion.CreatedBy property of a document.
  • When the subject line of a SharePoint alert email is longer than 75 characters and contains a mix of single-byte and double-byte characters, a carriage return line feed (CLRF) can occur between the two bytes of a double-bite character, causing the string to get corrupted..
  • Headings structure is incorrect in blogs basic view.
  • When you start a crawl for a web application that's migrated from SharePoint Server 2010, the crawl fails, and the content isn't searchable. This issue occurs because the connector retrieves the TenantId property two times.
  • When you open a document in Word Web App, you receive the following error message if there are special characters in the URL of the document:

Sorry, there was a problem and we can't open this document.

  • When you try to restore a site that's backed up in a site collection, you receive the following error message if the site collection lock is set to No Access:

Access to the web site has been blocked. The site isn't accessible and isn't displayed on Central Admin.

  • It's difficult for a screen reader to understand the structure between sections on a discussion board because there's only one heading. This update adds h2 and h3 labels to discussion boards for better screen reading.
  • In SharePoint Server 2013 on-premises, you can't not be redirected to SharePoint Online to create sites.

↑ Back to the top

Known issues in this security update

SharePoint Server 2013 and SharePoint Foundation 2013

Users can't open documents in Office Web Apps or Office Online Server in any site whose URL contains a space character.

To resolve this issue, install April 11, 2017, update for SharePoint Foundation 2013 (KB3178732)

↑ Back to the top

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.

↑ Back to the top

More Information

Security update deployment information

For deployment information about this update, see Microsoft Knowledge Base article 4013241.

Security update replacement information

This security update replaces previously released security update KB3115294.

File information

For the list of files that cumulative update KB3172540 contains, download the file information for update KB3172540.

File hash information

Package Name Package Hash SHA 1 Package Hash SHA 2
sts2013-kb3172540-fullfile-x64-glb.exe F40A8A81D5F1D113693DFF1BEB807FF5129D1023 3A9464AA57CD2D70F1C8F932C18C2BBF93EF70EF286643E612036CCECC2F9949

↑ Back to the top


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

↑ Back to the top

Keywords: kbBug, kbfix, kbsurveynew, kbExpertiseInter, KbSECBulletin, KbSECVulnerability, ATdownload, kbMustLoc, kbLangAll, kbSecurity, Known Issues, Known issues, kbSecReview

↑ Back to the top

Article Info
Article ID : 3172540
Revision : 22
Created on : 4/13/2020
Published on : 4/16/2020
Exists online : False
Views : 299