

- MICROSOFT FOREFRONT TMG 2010 WIKI PATCH
- MICROSOFT FOREFRONT TMG 2010 WIKI CODE
- MICROSOFT FOREFRONT TMG 2010 WIKI WINDOWS
So, if we put this file on a test web server and attempt to access it from a host behind TMG, TMG’s Malware Inspection will detect the threat as Exploit:JS/Elecom.B and it will clean the file:Ĭlean means that it removed the script from the file(note that the browser will still attempt to get that ‘.gif’ file, but this should not do any harm now):
MICROSOFT FOREFRONT TMG 2010 WIKI CODE
If we upload to VirusTotal the exploit code publicly available, we can note that only a few antivirus engines currently detect it, Microsoft’s antivirus engine being one of them detecting this exploit code as Exploit:JS/Elecom.B: We will use the exploits just the way they are. The signatures version on my test Forefront TMG 2010 machine were 4.17.0.0.īasically we have available for assessing the protection offered by Forefront TMG 2010 for MS Advisory 979352:īellow we won’t attempt to bypass the inspection engines on TMG. NIS was implemented based on GAPA(Generic Application-level Protocol Analyzer) research. Normally the NIS offers intrusion prevention and detection for exploits against Microsoft products. Thus protection offered by NIS is none for MS Advisory 979352 as writing. There is a signature, Expl:Win/!0000-0000, that "detects commonly used exploitation techniques for browser based vulnerabilities" which is of no use in this case(against the currently available exploit public code). Currently I do not see any specific signature for this vulnerability. The success of the Malware Inspection is up to the inspection engines and the way the exploit will be written/used(it may be possible for an attacker to bypass the inspection engines with the "help" of the HTTP protocol or by obfuscating the code).

The signatures version on my test Forefront TMG 2010 machine were. The later signature is for "detecting JavaScript-enabled objects that exhibit suspicious behavior", and if the dates are correct, apparently Forefront TMG 2010 could detect and block some attacks attempting to exploit the MS Advisory 979352 vulnerability before this vulnerability became known(against a “true” 0-day)-pure speculation, as can be many variables involved. The publicly available exploits, depending on some aspects, were detected by Microsoft’s antivirus engine as Exploit:JS/Elecom.B(Published: Jan 12, 2010), as Trojan:Win32/Swrort.A(Published: Jan 12, 2010) and as Exploit:JS/ShellCode.gen(Updated: Sep 09, 2008, Published: Sep 09, 2008).

MICROSOFT FOREFRONT TMG 2010 WIKI PATCH
To quickly summarize it, we have potential web-based threats against users or businesses due to MS Advisory 979352 while there is no patch available for this vulnerability. I wrote this blog entry as is interesting to see if the enhancements introduced by Microsoft with Forefront TMG 2010 can help mitigate against the risks that may appear now when the “Aurora” exploit is publicly available. Currently there is no patch available for this vulnerability.
MICROSOFT FOREFRONT TMG 2010 WIKI WINDOWS
We won’t go into the details of this situation, as it is well covered in the Reference section bellow.Ĭertain Windows machines running Internet Explorer are at risk, for the affected systems lists please see Microsoft Security Advisory (979352). January 2010 adrian Forefront TMG (0)Īs you may know, the “Aurora” exploit used in the attack over Google went public.
