July 2010 Microsoft Black Tuesday Summary
Overview of the July 2010 Microsoft Patches and their status.
Important: with today's patches, support for XP SP2 officially comes to an end. There will be no more patches for XP SP2 after today.
| # | Affected | Contra Indications | Known Exploits | Microsoft rating | ISC rating(*) | |
|---|---|---|---|---|---|---|
| clients | servers | |||||
| MS10-042 | Vulnerability in Help and Support Center Could Allow Remote Code Execution | |||||
| Windows XP SP2 and above, Windows Server 2003 SP2 CVE-2010-1885 |
KB 2229593 | actively being exploited | Severity:Critical Exploitability: 1 |
PATCH NOW! | Critical | |
| MS10-043 | Vulnerability in Canonical Display Driver Could Allow Remote Code Execution | |||||
| Windows7 x64, Windows Server 2008 R2 x64 CVE-2009-3678 |
KB 2032276 | no known exploits. | Severity:Critical Exploitability: 2 |
Critical | Critical | |
| MS10-044 | Vulnerabilities in Microsoft Office Access ActiveX Controls Could Allow Remote Code Execution | |||||
| Access 2003 SP3, Access 2007 SP1 and above CVE-2010-0814 CVE-2010-1881 |
KB 982335 | no known exploits. | Severity:Critical Exploitability: 1,1 |
Critical | Critical | |
| MS10-045 | Vulnerability in Microsoft Office Outlook Could Allow Remote Code Execution (Replaces MS09-060 ) | |||||
| Outlook CVE-2010-0266 |
KB 978212 | no known exploits. | Severity:Important Exploitability: 1 |
Critical | Critical | |
We appreciate updates
US based customers can call Microsoft for free patch related support on 1-866-PCSAFETY
- 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
---------------
Jim Clausing, jclausing --at-- isc [dot] sans (dot) org
FOR408 coming to central OH in Sep, see http://www.sans.org/mentor/details.php?nid=22353
VMware Studio Security Update
The folks at VMware folks have posted a new bulletin and update to address a privilege escalation in a non-default configuration of appliances created with VMware Studio 2.0.
---------------
Jim Clausing, jclausing --at-- isc [dot] sans (dot) org
FOR408 coming to central OH in Sep, see http://www.sans.org/mentor/details.php?nid=22353
Forensic challenge results
The results of the SANS Forensics Challenge (aka the 6th challenge from Jonathon Ham and Sherri Davidoff at http://forensicscontest.com) were announced last week at the SANS Forensics and Incident Response Summit. The winning entry was submitted by Wesley McGrew and included a cool new tool, pcapline.py. The other finalists also came up with some interesting tools, so be sure to check out all of them.
---------------
Jim Clausing, jclausing --at-- isc [dot] sans (dot) org
FOR408 is coming to central OH in Sept, see http://www.sans.org/mentor/details.php?nid=22353
Comments