Last Updated: 2012-02-15 01:50:21 UTC
by Manuel Humberto Santander Pelaez (Version: 2)
In my company, we began experiencing a problem when the users tried to access http://www.google.com.co though our Forefront TMG proxy. Every corporate user saw the following message:
This really looked strange, specially coming from google. I captured some packets and queried about the http get operations and got the following:
Also tried VirusTotal to scan the URL (http://www.google.com.co) and also got nothing:
I started analysis for http get number three. Wireshark shows some compressed content, so I took it from the capture and decompressed:
This problem has been confirmed in Microsoft website. I will update the diary when I have more information about it.
UPDATE: As of 20:11 GMT-5 Feb 14 2012, we received confirmation from Microsoft stating that this problem is a false positive and will be corrected in the update 1.119.1986.0 or higher for the antivirus.
Last Updated: 2012-02-14 20:41:30 UTC
by Johannes Ullrich (Version: 1)
Overview of the February 2012 Microsoft patches and their status.
|#||Affected||Contra Indications - KB||Known Exploits||Microsoft rating(**)||ISC rating(*)|
|MS12-008||Code Execution Vulnerabilities in Windows Kernel-Mode Drivers
|KB 2660465||disclosed vuln.||Severity:Critical
|MS12-009||Elevation of privilege vulnerabilities in ancillary function driver
(Replaces MS11-046, MS11-080)
|Ancillary Function Driver
|MS12-010||Cumulative Patch for Internet Explorer
|MS12-011||Sharepoint Elevation of Privileges Vulnerabilities
|MS12-012||Remote code execution vulnerability in color control panel
|Color Control Panel
|MS12-013||Vulnerability in C Run-Time Library Could Allow Remote Code Execution|
|C Run Time Library
|MS12-014||Vulnerability in Indeo Codec Could Allow Remote Code Execution|
|Indeo Audio Codec
|MS12-015||Vulnerabilities in Microsoft Visio Viewer 2010 Could Allow Remote Code Execution
|Microsoft Office Suites and Software
|MS12-016||Vulnerabilities in .NET Framework and Microsoft Silverlight Could Allow Remote Code Execution
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.
(**): 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.
Last Updated: 2012-02-14 14:21:43 UTC
by Johannes Ullrich (Version: 1)
Adobe released two security bulletins for today's patch tuesday kickoff:
APSB12-02 : Security update for Adobe Shockwave Player
This patch fixes a total of 9 vulnerabilities that affect Shockwave Player 184.108.40.2063 and earlier on Windows and OS X. After the update is applied, you should be at version 220.127.116.114. Adobe rates these vulnerabilities critical as some of them allow the execution of arbitrary code.
APSB12-04 : Security update for RoboHelp for Word
RoboHelp is not as commonly installed as other Adobe products. This patch fixes one vulnerability that is considered important. The vulnerability introduces a cross site scripting flaw in output generated by RoboHelp. I am not that familiar with the product, but even though Adobe doesn't specify it, it sounds like it may be necessary to re-create RoboHelp output after the update is applied to avoid the XSS issue in content generated with older versions.