ROPEMAKER Attack Turns Benign Emails Hostile Post-Delivery

Just because an email is secure when it arrives in your inbox doesn't mean that it cannot be maliciously modified later.

The intersection of email and Web technologies in recent years has given attackers a way to undermine the security and non-repudiation of email, including those that are signed using PGP or SMIME, security vendor Mimecast warned this week.

The email security provider has discovered a new exploit that it has dubbed ROPEMAKER, which gives attackers a way to change the content of an email, at their will, after it has been delivered, and without direct access to the user's email inbox. The exploit enables attackers to do things like swap out a benign URL in a delivered email with a malicious one, to edit text in the body of the email and turn entire chunks of benign text to a malicious URL.

Matthew Gardiner, cybersecurity strategist at Mimecast says the company has deliberately decided not to label the issue as either a product vulnerability or fundamental architectural flaw. "We think this is a topic area that needs to be further debated," he says.

There are certainly measures that email application providers can do to better protect users against the kind of threat posed by ROPEMAKER. "[But] part of the challenge with the ROPEMAKER exploit is it doesn't fall squarely into one particular organization's area of responsibility," he says.

The problem, according to Gardiner, stems from the manner in which PC-based email apps like Outlook and Apple Mail use Web technologies to make emails more visually attractive and dynamic compared to the purely text-based emails of a few years ago. Certain browser-based email clients such as Gmail, Outlook.com and icloud.com that Mimecast looked at were not susceptible to the issue.

"Fundamentally ROPEMAKER exists because Web technologies can and often do interoperate over a network, typically the Internet," Mimecast researchers said in a blog on the topic this week. "To be more precise, two resources that are housed remotely from one another, but are linked via a network can interoperate; one affecting the execution of the other."

For example, on the Web, remotely based and remotely controlled content and resources are routinely fetched or referenced without the local user having to do anything. Cascading Style Sheets (CSS) that organizations use to describe how the layout, fonts, colors, and other features of HTML content should be presented is a good example. CSS enables the separation of content from the components that control how the content should be presented, the company noted.

When used in the context of emails, a remotely hosted CSS file can give an attacker a way to control not just the presentation style of the email but its actual content as well, Mimecast said. Just like Web pages can continuously change text content, audio, and visuals, a remotely hosted CSS can enable changes to the content in email that has already been delivered.

"ROPEMAKER works as long as the email client automatically connects to the remote CSS to retrieve the desired 'style' for the email. This is at the core of the ROPEMAKER exploit," Mimecast said.

In its advisory, the email security vendor described two ways in which an attacker could exploit the issue. One of them showed how an attacker could switch a good URL with a bad one. The other, which Mimecast has dubbed a Matrix Exploit, involved an attacker sending a matrix of ASCII text, character by character, and then using the remote CSS file to control what is displayed to the recipient.

"The Matrix Exploit is the delivery of all possible characters in an email," such as a, A, b, B, c, C, Gardiner says. "And then, post-delivery, making whatever message you want to appear come to life for each individual email user. "This tactic makes it very difficult for an email security product to determine if an inbound mail is good or not because what it says is not determined until after the email has been delivered, Gardiner notes.

Apple Mail has a user setting that would allow email users to block automatic execution of a remote resource—like a remotely hosted CSS file for instance, he says. But few are likely using it.

Most email clients use local CSS for reasons of performance and network connectivity, adds Gardiner. However, remote CSS is supported with HTML and there's no reason to believe attackers wouldn't use it. "From the end users' point of view they don't have any idea where the CSS is hosted, unless they check the HTML source of the email. How many users do that?"

Mimecast has shared its research privately with all of the primary email client vendors, but so far not one of them has acknowledged ROPEMAKER as a vulnerability or exploit. Mimecast says it has not seen any evidence of ROPEMAKER-like attacks in the wild so far.

Learn from the industry’s most knowledgeable CISOs and IT security experts in a setting that is conducive to interaction and conversation. Click for more info and to register.

Related content: