Updates for SharePoint 2013 (July 2018 CU)

A new cumulative update has been released for SharePoint 2013 (July 2018 CU)
This CU fixes all SharePoint 2013 products.

SP Build: ​15.0.5049.1001

This CU is a full update (Uber package), requiring no earlier updates apart from SP1.

The CU includes all SharePoint 2013 security fixes released since SP1. It does not include SP1, which is required to install this CU.

Because of its size, the CU is split into separate CAB files and one executable. Download all these files into the same installation folder before starting the update.

SharePoint 2013 CU download files

SharePoint 2013 CU – KB articles describing the CU:

  • KB 4022239 – SharePoint Foundation 2013 July 2018 CU
  • KB 4022241 – SharePoint Server 2013 July 2018 CU
  • KB 4022240 – Project Server 2013 July 2018 CU
  • Tento CU neobsahuje aktualizaci pro Office Web Apps Server 2013

SharePoint 2013 CU – CU download link:

After installation, remember to run the SharePoint 2013 Products Configuration Wizard, or:
PSConfig.exe -cmd upgrade -inplace b2b -wait -cmd applicationcontent -install -cmd installfeatures -cmd secureresources -cmd services -install

Important

Before installing the CU, ensure SP1 is already installed.

Installation may take up to five hours, so I recommend reading: Speeding up CU and SP installation on SharePoint 2013.

If your farm's patch level is earlier than July 2015 CU, run PSCONFIG immediately after installing the CU to update the schema of certain search databases. More at:
https://blogs.technet.microsoft.com/stefan_gossner/2015/07/15/important-psconfig-is-mandatory-for-july-2015-cu-for-sharepoint-2013

Always install only the CU matching your product version on a SharePoint 2013 farm.

The Project Server 2013 CU already includes:

  • CU SharePoint Server 2013
  • CU SharePoint Foundation 2013.

The SharePoint Server 2013 CU already includes:

  • CU SharePoint Foundation 2013

Remember to update Distributed Cache as well as SharePoint; see How to update Distributed Cache correctly.

Included fixes and improvements

This CU includes the following fixes and improvements.

SharePoint Foundation 2013

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-8299 and Microsoft Common Vulnerabilities and Exposures CVE-2018-8300.

This security update contains fix for the following nonsecurity issue:

Assume that you use the content editor web part (CEWP) to enter an incorrectly spelled word on a SharePoint page. When you publish the page, the incorrectly spelled word is not underlined, and some letters are deleted.

SharePoint Server 2013

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-8300, Microsoft Common Vulnerabilities and Exposures CVE-2018-8323, and Microsoft Common Vulnerabilities and Exposures CVE-2018-8299.

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

  • Assume that you use the content editor web part (CEWP) to enter an incorrectly spelled word on a SharePoint page. When you publish the page, the incorrectly spelled word is not underlined, and some letters are deleted.
  • This update supports current culture number separators for numeric refiners.
  • This update provides a translation update for certain search query strings.

Project Server 2013

This update fixes the following issues:

  • Local custom date type fields that have a formula and have the Calculation for task and group summary rows option set to minimum or maximum are not rolled up correctly to summary tasks when you update a project in Project Web App.
  • The ReadStatusTimephasedData API is not available for users who have the Status Broker permission. Therefore, they cannot get the timesheet time-phased related data.
  • When you assign a resource to an unassigned task and publish the task in Project 2013, the newly created assignment does not properly update the AssignmentResourceType, AssignmentType, ResourceUID, and ResourceOwnerUID fields in the MSP_EpmAssignment table in the reporting database. Additionally, the expected time-phased data for the assignment in the MSP_EpmAssignmentByDay table is not found. This issue occurs after you install March 6, 2018, update for Project 2013 (KB4018292).
  • A custom event receiver that’s associated with timesheets generates an error in Project Server in Windows Server 2012 R2. When you create a timesheet, you receive the following error message:

    Timesheet

    This Web Part was unable to load.

    Information that may be useful in solving this problem was written to the Unified Logging Service (ULS) log on the Project Web App with the following ID: IDNumber

    For more information, contact your Project Web App administrator.


Komentáře