Oh no, you're thinking, yet another cookie pop-up. Well, sorry, it's the law. We measure how many people read us, and ensure you see relevant ads, by storing cookies on your device. If you're cool with that, hit “Accept all Cookies”. For more info and to customize your settings, hit “Customize Settings”.

Review and manage your consent

Here's an overview of our use of cookies, similar technologies and how to manage them. You can also change your choices at any time, by hitting the “Your Consent Options” link on the site's footer.

Manage Cookie Preferences
  • These cookies are strictly necessary so that you can navigate the site as normal and use all features. Without these cookies we cannot provide you with the service that you expect.

  • These cookies are used to make advertising messages more relevant to you. They perform functions like preventing the same ad from continuously reappearing, ensuring that ads are properly displayed for advertisers, and in some cases selecting advertisements that are based on your interests.

  • These cookies collect information in aggregate form to help us understand how our websites are being used. They allow us to count visits and traffic sources so that we can measure and improve the performance of our sites. If people say no to these cookies, we do not know how many people have visited and we cannot monitor performance.

See also our Cookie policy and Privacy policy.

This article is more than 1 year old

Using Outlook? You should probably do some patching

It's 2018 and previewing an email can flash your privates at the world

Microsoft emitted a patch for all supported versions of Outlook on Patch Tuesday this month to prevent attackers harvesting credentials from users who simply preview a carefully crafted Rich Text (RTF) email.

The vulnerability (CVE-2018-0950) exploited Outlook’s unfortunate habit of retrieving remotely hosted Object Linking and Embedding (OLE) content when previewing a RTF email.

The Windows client was able to authenticate itself if that content was hosted on SMB/CIFS server.

If the SMB server was controlled by the attacker, then Windows had effectively handed over the user’s login credentials, including a hashed password, without any interaction on behalf of the user other than the email being rendered.

And let’s face it, most users generally are unlikely to have a particularly strong password, meaning that cracking the hash would not have presented a problem for a determined attacker.

Microsoft’s OLE technology was surely the gift that keeps on giving as far as hackers are concerned.

Will Dormann of CERT reported the issue on 29 November 2016 (yes, 2016) and it has taken Microsoft 18 months to deal with it.

Unfortunately, the fix didn't entirely solve the problem. While it did stop Outlook from kicking off a SMB connection during preview, it would not avoid the scenario of a user clicking on a link in the email itself. Such carefree clicking sees the same potential impact as the original vulnerability.

To solve the issue in the absence of a more complete fix, Dormann recommended installing the patch (obviously) and then stopping inbound and outbound SMB connections at the network border by blocking ports 445/tcp, 137/tcp, 139/tcp, as well as 137/udp and 139/udp.

Dormann also suggested blocking NTLM SSO authentication. To be fair, Microsoft issued an advisory on this very thing in November 2017.

Dormann concluded with some common-sense security advice: “Assume that at some point your client system will attempt to make an SMB connection to an attacker's server. For this reason, make sure that any Windows login has a sufficiently complex password so that it is resistant to cracking”

He went on to recommend using a password manager to deal with all those symbols and numbers we should all be using in hard-to-crack and easy-to-forget passwords. ®

 

Similar topics

TIP US OFF

Send us news


Other stories you might like