new Microsoft word 0 day exploit.

The internet is buzzing with yet another 0 day exploit for Microsoft Word. Yes this one is serious and can infect you with no action on your part., if you open one of these malicious Word Documents.  But lets just step back, take a deep breath and in the immortal words … Continue reading → Continue reading new Microsoft word 0 day exploit.

Microsoft Tweaks Simplified Servicing Packages for Older Versions of Windows

Microsoft has made a change to the new streamlined update process for older versions of Windows.

read more Continue reading Microsoft Tweaks Simplified Servicing Packages for Older Versions of Windows

How likely is it that the Hot Potato vulnerability can be exploited on a up-to-date Windows 2012 machine?

I recently found an article about the Hot Potato vulnerability and it seemed quite interesting.

Using this technique, we can elevate our privilege on a Windows workstation from the lowest levels to “NT AUTHORITY\SYSTEM” – the highest level of privilege available on a Windows machine.

The exploit basically consists of three aspects:

  1. Local NBNS Spoofer
  2. Fake WPAD Proxy Server
  3. HTTP -> SMB NTLM Relay

I’m specifically interested in this vulnerability on Windows Server 2012 (R2). The exploit makes use of an automatic update mechanism that downloads certificate trust lists (CTLs) on a daily basis.

The researchers said that using SMB (Server Message Block) signing may theoretically block the attack. Other method to stop the NTNL relay attack is by enabling “Extended Protection for Authentication” in Windows.

My question, are one of the two mitigations as suggested by the researchers automatically used as a patch/fix through Windows Update, since the initial vulnerability was released? I think somewhere in the beginning of 2016.

Note: It’s ironic that the introduction of a daily update of CTLs that are meant to improve security, introduce a massive Privilege Escalation vulnerability.

Continue reading How likely is it that the Hot Potato vulnerability can be exploited on a up-to-date Windows 2012 machine?