Problem with Microsoft Antivirus regarding malware from google website

Published: 2012-02-14
Last Updated: 2012-02-15 01:50:21 UTC
by Manuel Humberto Santander Pelaez (Version: 2)
3 comment(s)

In my company, we began experiencing a problem when the users tried to access though our Forefront TMG proxy. Every corporate user saw the following message:

Forefront TMG blocking google


This really looked strange, specially coming from google. I captured some packets and queried about the http get operations and got the following:

Wireshark Capture

Got three operations: one from the main query, second one retrieving a javascript file and a third one unknown. First one looked normal as always, so I started analyzing second one. The MD5 for the javascript file is 886e4780fc0af43a19eb4dcd55b728d7. I looked up the resulting MD5 and got nothing. I uploaded the script to jsunpack and got nothing:


Jsunpack Analysis

Also tried VirusTotal to scan the URL ( and also got nothing:

 Virustotal Check for google website

I started analysis for http get number three. Wireshark shows some compressed content, so I took it from the capture and decompressed:

 Wireshark capture from

The compressed file has md5 1375a0f59d52d862a1297df7566c6894, the uncompressed file has md5  c4c490a2a55a16492c068ec50827958b and when loaded starts a download from I analyzed that javascript and wepawet and jsunpack shows nothing abnormal.

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.

 Manuel Humberto Santander Peláez
SANS Internet Storm Center - Handler
Twitter: @manuelsantander
e-mail:msantand at isc dot sans dot org

3 comment(s)

February 2012 Microsoft Black Tuesday

Published: 2012-02-14
Last Updated: 2012-02-14 20:41:30 UTC
by Johannes Ullrich (Version: 1)
4 comment(s)

Overview of the February 2012 Microsoft patches and their status.

# Affected Contra Indications - KB Known Exploits Microsoft rating(**) ISC rating(*)
clients servers
MS12-008 Code Execution Vulnerabilities in Windows Kernel-Mode Drivers
(Replaces MS11-087)
KB 2660465 disclosed vuln. Severity:Critical
Exploitability: Likely
Critical Critical
MS12-009 Elevation of privilege vulnerabilities in ancillary function driver
(Replaces MS11-046, MS11-080)
Ancillary Function Driver
KB 2645640 no. Severity:Important
Exploitability: Likely
Important Important
MS12-010 Cumulative Patch for Internet Explorer
(Replaces MS11-099)
Internet Explorer
KB 2647516 no. Severity:Critical
Exploitability: Likely
Critical Important
MS12-011 Sharepoint Elevation of Privileges Vulnerabilities
KB 2663841 no. Severity:Important
Exploitability: -
N/A Important
MS12-012 Remote code execution vulnerability in color control panel
Color Control Panel
KB 2643719 no. Severity:Important
Exploitability: Likely
Critical Important
MS12-013 Vulnerability in C Run-Time Library Could Allow Remote Code Execution
C Run Time Library
KB 2654428 no Severity:Critical
Exploitability: Likely
Critical Critical
MS12-014 Vulnerability in Indeo Codec Could Allow Remote Code Execution
Indeo Audio Codec
KB 2661637 no Severity:Important
Exploitability: Likely
Important N/A
MS12-015 Vulnerabilities in Microsoft Visio Viewer 2010 Could Allow Remote Code Execution
(Replaces MS11-089)
Microsoft Office Suites and Software
KB 2663510 no. Severity:Important
Exploitability: Likely
Important N/A
MS12-016 Vulnerabilities in .NET Framework and Microsoft Silverlight Could Allow Remote Code Execution
(Replaces MS11-069)
.NET Framework
KB 2651026 no. Severity:Critical
Exploitability: Likely
Critical Critical
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.

Johannes B. Ullrich, Ph.D.
SANS Technology Institute

Keywords: mspatchday
4 comment(s)

Adobe Shockwave Player and RoboHelp for Word Patches

Published: 2012-02-14
Last Updated: 2012-02-14 14:21:43 UTC
by Johannes Ullrich (Version: 1)
0 comment(s)

Adobe released two security bulletins for today's patch tuesday kickoff:

APSB12-02 [1]: Security update for Adobe Shockwave Player

This patch fixes a total of 9 vulnerabilities that affect Shockwave Player and earlier on Windows and OS X. After the update is applied, you should be at version Adobe rates these vulnerabilities critical as some of them allow the execution of arbitrary code. 

APSB12-04 [2]: 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.



Johannes B. Ullrich, Ph.D.
SANS Technology Institute

0 comment(s)
ISC StormCast for Tuesday, February 14th 2012


Diary Archives