Microsoft June 2013 Black Tuesday Overview - SANS Internet Storm Center

Overview of the June 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-047	The usual monthly MSIE cumulative patch, adding fixes for a bunch more vulnerabilities. All but one are memory corruption vulnerabilities. The odd one is an information leak.
MS13-047	MSIE CVE-2013-3110 CVE-2013-3111 CVE-2013-3112 CVE-2013-3113 CVE-2013-3114 CVE-2013-3116 CVE-2013-3117 CVE-2013-3118 CVE-2013-3119 CVE-2013-3120 CVE-2013-3121 CVE-2013-3122 CVE-2013-3123 CVE-2013-3124 CVE-2013-3125 CVE-2013-3139 CVE-2013-3141 CVE-2013-3142	KB 2838727	No publicly known exploits	Severity:Critical Exploitability:1	Critical	Important
MS13-048	A kernel memory information leak vulnerability.
MS13-048	kernel CVE-2013-3136	KB 2839229	No publicly known exploits	Severity:Important Exploitability:3	Important	Less urgent
MS13-049	A vulnerability in the implementation of TCP/IP allows for a TCP connection to cause the system to stop responding.
MS13-049	TCP/IP CVE-2013-3138	KB 2845690	No publicly known exploits.	Severity:Important Exploitability:3	Important	Critical
MS13-050	Privilege excalation vulnerability when deleting a printer connection.
MS13-050	Print spooler CVE-2013-3139	KB 2839894	No publicly known exploits	Severity:Important Exploitability:1	Important	Important
MS13-051	A memory corruption vulnerability allows random code execution in the context of the current user due to failure to properly handle PNG images. Note it also affects Office for Mac 2011.
MS13-051	Office CVE-2013-1331	KB 2839571	Microsoft claim this is being exploited in "targeted attacks".	Severity:Important Exploitability:1	Critical	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 -- Section 66

Swa

760 Posts

Jun 11th 2013

Has anyone else seen a WIN2K8 R2 standard server go into a boot loop after applying the latest updates? I have seen this on 2 of my servers. 2 came up after the 2nd reboot and the 3rd is toast.

PW