11-04-2011 12:44 PM - edited 11-05-2011 07:08 AM
Microsoft Security Advisory, Vulnerability in TrueType Font Parsing Could Allow Elevation of Privilege, relates to a Windows kernel issue related to the Duqu malware, a trojan that injects malicious code into other processes. An update is not expected to be ready for delivery with the scheduled November update. A Microsoft Fix it solution is available from Microsoft Microsoft KB Article 2639658
(A few additional details and informational links are available in my article at Microsoft Fix it for Duqu Malware, Security Advisory 2639658.)
11-04-2011 07:22 PM
Symantec has posted: "Duqu: Status Updates Including Installer with Zero-Day Exploit Found" that includes a link to Microsoft's advisory and to the workaround for the zero-day vulnerability identified as one Duqu infection vector.
http://www.symantec.com/connect/w32-duqu_status-up
If you find a post helpful and it answers your question, please click the "Accept As Solution" button.
Lenovo Advocate
Microsoft MVP - Consumer Security
Member of Alliance of Security Analysis Professionals
11-05-2011 07:16 AM
The Symantec article also has a nice infographic. (It is one of the additional references I referenced in my article.)
Another important point that I should have mentioned earlier is that Microsoft has provided MAPP partners (Microsoft Active Protections Program) the details for adding detection in their products. That means A/V vendors should have signatures to detect and block attempts to exploit the vulnerability.
11-06-2011 10:11 AM
Corrine,
Welcome to the forum! Thank you both for sharing info on Duqu - great to have more security experts here in the community!
Best regards,
Mark
11-06-2011 10:31 AM
11-06-2011 03:47 PM
After enabling Microsoft Fix it 50792, there have been reports of Microsoft updates KB 972270 (MS10-001: Vulnerability in the Embedded OpenType Font Engine could allow remote code execution) and KB 982132 (MS10-076: Vulnerability in the Embedded OpenType Font Engine could allow remote code execution) being repeatedly re-offered.
In the event you experience the same issue, after confirming in the update history that both updates are installed, I suggest that you enable the Fix it and then hide the updates when offered again.
To hide the updates, select the first update and then right-click the update and click "Hide Update." Repeat for the second update.
11-11-2011 03:10 PM - edited 11-11-2011 03:12 PM
Updated: Friday, November 11, 2011
Microsoft Security Advisory (2639658)
Vulnerability in TrueType Font Parsing Could Allow Elevation of Privilege
https://technet.microsoft.com/en-us/security/advis
If you find a post helpful and it answers your question, please click the "Accept As Solution" button.
Lenovo Advocate
Microsoft MVP - Consumer Security
Member of Alliance of Security Analysis Professionals
11-11-2011 07:16 PM
Thanks, Bugbatter! I'm glad to see the Advisory was finally updated.
The change: "V1.4 (November 11, 2011): Revised impact statement for the workaround, Deny access to T2EMBED.DLL, to address applications that rely on T2EMBED.DLL for functionality."
Impact of Workaround.
- Applications that rely on embedded font technology will fail to display properly.
- After applying this workaround, users of Windows XP and Windows Server 2003 may be reoffered the KB982132 and KB972270 security updates. These reoffered updates will fail to install. The reoffering is a detection logic issue and users who have successfully applied both the KB982132 and KB972270 security updates previously can ignore the reoffer.
- Applications with functionality that relies on T2EMBED.DLL, such as generating PDF files, may fail to work as expected. For example, Microsoft Office software will fail to generate PDF files.
~~~~~~~~~~~~~
It was reported at one of the forums that running System File Checker with the Microsoft Fix it enabled results in it stopping at 16% and giving the message:
Cannot repair member file [l:22{11}]"t2embed.dll" of Microsoft-Windows-Font-Embedding
After disabling the Microsoft Fix it, System File Checker works again. That makes sense since the Fix it is taking ownership of t2embed.dll and then denying access to the dll: Takeown.exe /f "%windir%\system32\t2embed.dll" Icacls.exe "%windir%\system32\t2embed.dll" /deny *S-1-1-0
F)