KB3013455 (MS15-010) causes font corruption

Anonymous
2015-02-10T21:06:56+00:00

February 2015 update KB3013455 causes 'Courier New' font corruption on some Windows systems, I can confirm it for Windows Server 2003 and 2008. You can verify it in Notepad. Removing the update fixes the issue.

Windows 7 and 8.1 are not affected by the update.

[removed information that 64bit may not be affected]

Windows for home | Other | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
Answer accepted by question author
Anonymous
2015-02-12T05:17:15+00:00

Yes Remove/Add Program >> View Installed Windows Updates >> I added the column to display installation date, reverse sorted and found "3013455" ((this update), then Uninstalled it.

This was common in the late 90's/early 2000's, had to remember which updates not to install that would break things. It's been solid for at least a decade, now this.

I don't really care what the fix is for. If I can't read my screen from my chair, I need to resolve it to do my job (own a web design firm).

I share the same opinion as this article "...the bottom line here is that if you want to be able to actually read the screen, you'll want to hold off installing this update until the problem is fixed."

http://windowsitpro.com/msrc/patch-tuesday-font-corruption-kb3013455

Was this answer helpful?

3 people found this answer helpful.
0 comments No comments
Answer accepted by question author
Anonymous
2015-02-18T18:42:43+00:00

The link for all downloads is:

http://www.microsoft.com/en-us/search/Results.aspx?q=kb3013455&form=DLC

Choose your OS from the half dozen big options at the top and it brings you right to the download page.

Hit the big red download button and it should offer you two updates:

kb3013455   (the original that breaks fonts)

and

KB3037639  (the secondary update to fix fonts)

I installed the original, said do not reboot, and installed the second.

After reboot I appear patched and my fonts are good.

Was this answer helpful?

2 people found this answer helpful.
0 comments No comments

300 additional answers

Sort by: Oldest
  1. Anonymous
    2015-02-15T21:43:06+00:00

    I am flabbergasted that the advice here is to uninstall a patch for a critical vulnerability that could lead to customers machines being infected with malicious software that could result in a them being exposed to data loss, theft, ransomed data or running a hijacked machine used for all manner of illegal purposes.

    I am also astonished that a fault such as this couldn't be fixed and properly tested within 90 days of notice.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2015-02-15T22:24:44+00:00

    I, for one, won't uninstall any security update, but have changed fonts in applications and the system where possible and convenient. There are still a few applications, email, etc, where the font is a little shaky, but it's a small price to pay to keep an affected system up to date.  Also, I continue to hope Microsoft will present a solution, as I'm sure they're well aware of the problem by now.

    (Security tech)

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2015-02-15T22:42:33+00:00

    Fine, then come up with a better suggestion.

    We don't control Microsoft.

    None of the issues are in active attack at this time.  So attackers first have to code up something to take advantage of this. 

    Given that there is a ton of other stuff (zero day flash) they can attack us with we have time to put pressure on Microsoft to fix this for these platforms.

    Of the items that you will have no protection for the true type one has the most risk.

    Even then, again as stated in the bulletin "When this security bulletin was originally issued Microsoft had not received any information to indicate that this vulnerability had been publicly used to attack customers. "

    The clock is ticking yes, but if someone has to choose between getting their job done, then pull off this update and surf carefully.

    This was not a Google disclosed item that I see so I'm not sure how long it took to code.

      The google disclosed one is the OTHER patch as I read it  3023562 which maps to **CNG Security Feature Bypass Vulnerability - CVE-2015-0010**  which per https://technet.microsoft.com/library/security/dn903755.aspx is the Google one.

    This is one of the vulns not protected for if you pull off the update.

    TrueType Font Parsing Remote Code Execution Vulnerability - CVE-2015-0059

    A remote code execution vulnerability exists in the Windows kernel-mode driver (Win32k.sys) that is caused when it improperly handles TrueType fonts.

    An attacker who successfully exploited this vulnerability could run arbitrary code in kernel mode. An attacker could then install programs; view, change, or delete data; or create new accounts with full administrative rights. To exploit the vulnerability, an attacker would need to convince a user to open a specially crafted document or visit an untrusted website that contains embedded TrueType Fonts. The update addresses the vulnerability by correcting how the kernel-mode driver handles TrueType fonts.

    Microsoft received information about this vulnerability through coordinated vulnerability disclosure. When this security bulletin was originally issued Microsoft had not received any information to indicate that this vulnerability had been publicly used to attack customers.

    Mitigating Factors

    Microsoft has not identified any mitigating factors for this vulnerability.

    Workarounds

    The following workarounds may be helpful in your situation:

    • Deny access to T2EMBED.DLL For 32-bit systems, enter the following commands at an administrative command prompt:

    Copy

    Takeown.exe /f "%windir%\system32\t2embed.dll" Icacls.exe "%windir%\system32\t2embed.dll" /deny everyone:(F)

    For 64-bit systems, enter the following commands at an administrative command prompt:
    

    Copy

    Takeown.exe /f "%windir%\system32\t2embed.dll" Icacls.exe "%windir%\system32\t2embed.dll" /deny everyone:(F) Takeown.exe /f "%windir%\syswow64\t2embed.dll" Icacls.exe "%windir%\syswow64\t2embed.dll" /deny everyone:(F)

    **Impact of workaround.** Applications that rely on embedded font technology will fail to display properly.
    

    Was this answer helpful?

    0 comments No comments