Microsoft August 2013 Black Tuesday Overview

Overview of the August 2013 Microsoft patches and their status.

#	Affected	Contra Indications - KB	Known Exploits	Microsoft rating(**)	ISC rating(*)
#	Affected	Contra Indications - KB	Known Exploits	Microsoft rating(**)	clients	servers
MS13-059	A multitude of new vulnerabilities have been added to the regular cumulative IE update. You want this one if you use IE.
MS13-059	MSIE CVE-2013-3184 CVE-2013-3186 CVE-2013-3187 CVE-2013-3188 CVE-2013-3189 CVE-2013-3190 CVE-2013-3191 CVE-2013-3192 CVE-2013-3193 CVE-2013-3194 CVE-2013-3199	KB 2862772	No publicly known exploits	Severity:Critical Exploitability:1	Critical	Important
MS13-060	A vulnerability in how OpenType fonts are handled allow for random code execution with the rights of the logged-on user. Note that exploitation over the Internet via a a browser is possible.
MS13-060	unicode font parsing CVE-2013-3181	KB 2850869	No publicly known exploits	Severity:Critical Exploitability:2	Critical	Important
MS13-061	Multiple publicly disclosed vulnerabilities allow random code execution when previewing malicious content using OWA (Outlook Web Access). The vulnerabilities are situated in the webready (to display attachments) and Data Loss Prevention (DLP) components. Of interest is to note that - it was Oracle who disclosed the vulnerabilities in their patch updates in April and July 2013. Microsoft licensed the vulnerable libraries from Oracle. - There are also functional changes non security changes rolled up into this update
MS13-061	Exchange CVE-2013-2393 CVE-2013-3776 CVE-2013-3781	KB 2876063	Publicly disclosed vulnerabilities.	Severity:Critical Exploitability:2	NA	Critical
MS13-062	A vulnerability in the handling of asynchronous RPC requests allows for an escalation of privileges. As such it would allow execution of random code in the context of another user.
MS13-062	Microsoft RPC CVE-2013-3175	KB 2849470	No publicly known exploits	Severity:Important Exploitability:1	Critical	Important
MS13-063	Multiple vulnerabilities allow privilege escalation. Of note is CVE-2013-2556, which allows to bypass a security feature called ASLR (Address Space Layout Randomization)
MS13-063	Windows Kernel CVE-2013-2556 CVE-2013-3196 CVE-2013-3197 CVE-2013-3198	KB 2859537	CVE-2013-2556 was publicly disclosed and exploitation was demonstrated.	Severity:Important Exploitability:1	Critical	Important
MS13-064	A memory corruption vulnerability in the Windows NAT driver allows for a denial of service (DoS) situation that would cause the system to stop responding till restated. Relies on malicious ICMP packets. Unrelated to MS13-065.
MS13-064	NAT driver CVE-2013-3182	KB 2849568	No publicly known exploits	Severity:Important Exploitability:3	Less urgent	Important
MS13-065	A memory allocation problem in the ICMPv6 implementation allows attackers to cause a Denial of Service (DoS). Exploitation would cause the system to stop responding till restarted. Unrelated to MS13-064.
MS13-065	ICMPv6 CVE-2013-3183	KB 2868623	No publicly known exploits	Severity:Important Exploitability:3	Critical	Critical
MS13-066	Active Directory Federation Services (AD FS) could reveal information about the service account used. This information could as an example subsequently be used in a Denial of Service attack by locking the account out, causing all users that rely on the federated service to be locked out as well.
MS13-066	Active Directory CVE-2013-3185	KB 2873872	No publicly known exploits	Severity:Important Exploitability:3	NA	Important

We will update issues on this page for about a week or so as they evolve.
We appreciate updates
US based customers can call Microsoft for free patch related support on 1-866-PCSAFETY

(*): ISC rating

We use 4 levels:
- PATCH NOW: Typically used where we see immediate danger of exploitation. Typical environments will want to deploy these patches ASAP. Workarounds are typically not accepted by users or are not possible. This rating is often used when typical deployments make it vulnerable and exploits are being used or easy to obtain or make.
- Critical: Anything that needs little to become "interesting" for the dark side. Best approach is to test and deploy ASAP. Workarounds can give more time to test.
- Important: Things where more testing and other measures can help.
- Less Urgent: Typically we expect the impact if left unpatched to be not that big a deal in the short term. Do not forget them however.
The difference between the client and server rating is based on how you use the affected machine. We take into account the typical client and server deployment in the usage of the machine and the common measures people typically have in place already. Measures we presume are simple best practices for servers such as not using outlook, MSIE, word etc. to do traditional office or leisure work.
The rating is not a risk analysis as such. It is a rating of importance of the vulnerability and the perceived or even predicted threat for affected systems. The rating does not account for the number of affected systems there are. It is for an affected system in a typical worst-case role.
Only the organization itself is in a position to do a full risk analysis involving the presence (or lack of) affected systems, the actually implemented measures, the impact on their operation and the value of the assets involved.
All patches released by a vendor are important enough to have a close look if you use the affected systems. There is little incentive for vendors to publicize patches that do not have some form of risk to them.

(**): The exploitability rating we show is the worst of them all due to the too large number of ratings Microsoft assigns to some of the patches.

--
Swa Frantzen

Swa

760 Posts

Aug 13th 2013

Microsoft has also today rereleased MS13-052, the .NET patch which broke Sharepoint and SCCM.

http://technet.microsoft.com/en-us/security/bulletin/ms13-052#section4

Why was this bulletin revised on August 13, 2013?
Microsoft revised this bulletin to rerelease the following updates for the specified editions of Windows:

For Windows XP: The 2840628 and 2844285 updates
For Windows Server 2003: The 2840628 and 2844285 updates
For Windows Vista: The 2840628, 2840642, and 2844287 updates
For Windows Server 2008: The 2840628, 2840642, and 2844287 updates
For Windows 7: The 2840628, 2840642, and 2844286 updates
For Windows Server 2008 R2: The 2840628, 2840642, and 2844286 updates
For Windows 8: The 2840632 and 2844289 updates
For Windows Server 2012: The 2840632 and 2844289 updates
For Windows RT: The 2840632 update

The rereleased updates address issues as described in Microsoft Knowledge Base Article 2872441 and Microsoft Knowledge Base Article 2872041. Customers should install the rereleased updates that apply to their systems.

Anonymous

MS13-057 was rereleased for NT6.1 aswell.
https://technet.microsoft.com/en-us/security/bulletin/ms13-057#section4

Microsoft revised this bulletin to rerelease the 2803821 update for Windows 7 and Windows Server 2008 R2.
The rereleased update addresses an application compatibility issue in which WMV encoded video could fail to properly render during playback. Windows 7 and Windows Server 2008 R2 customers should install the rereleased update.

Anonymous

Issues reported with MS13-061 and Exchange 2013.

http://windowsitpro.com/blog/ms13-061-causes-search-controller-headaches-exchange-2013

Anonymous

...And now MS-066 aswell
"Why was this bulletin revised on August 14, 2013? What happened to the original AD FS security updates?
Microsoft is aware of issues with the 2868846, 2843638, and 2843639 updates affecting Active Directory Federation Services (AD FS) that could cause AD FS to stop working. Microsoft has removed the updates from Windows Update and the Download Center and is investigating the issues. Microsoft will release new packages once the issues have been resolved."

Anonymous

...and MS13-063 was also re-released:

"Known issues with this security update: Some users may experience issues with certain games after they install security update 2859537. In some cases, users may not successfully start and sign in to the games. Microsoft is researching this problem and will post more information in this article when the information becomes available.
see"

see https://support.microsoft.com/kb/2859537

Anonymous

I count six bad patches in the August crop: http://www.infoworld.com/t/microsoft-windows/microsoft-botches-six-windows-patches-in-latest-automatic-update-224988

WoodyLeonhard

9 Posts