Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Security Management //

Encryption

5/16/2018
09:35 AM
Larry Loeb
Larry Loeb
Larry Loeb
50%
50%

Relax: PGP Is Still Secure

Talk about overreacting. After researchers claimed to have found some flaws in PGP, the industry lost its collective mind. Here's what is really happening.

This past Sunday evening, rumors swept the Internet that some researchers from Germany and Belgium were about to announce a successful attack on Pretty Good Privacy (PGP) -- OpenPGP -- as well as the corporate-used S/MIME for encrypting email.

While the researchers were slated to announce details on May 15, this storm caused a premature release of the exploit details.

Initial reactions were of "the sky is falling" variety. Tellingly, the Electronic Frontier Foundation added to the overall panic with an advisory to remove PGP encryption.

The problem was, the initial reaction was wrong.

What was described by the "Efail" paper was not that the underlying protocols were broken or even attacked. The researchers found a way for some email programs to get tricked into revealing the plaintext of a message through an injected HTML element sent to a user that was processing HTML elements in their mail clients.

One is forced to ask, then, how that HTML element that causes information to be exfiltrated gets injected in the first place?

If someone is running a man-in-the-middle attack on your email, there are other significant problems that you face. Of course, hacked email accounts or compromised SMTP servers are possible. Here again you face severe problems regardless of the mail situation.

In any case, if an attacker has an encrypted blob of mail and knows who is able to decrypt it, they simply target the person most likely to have HTML view enabled. Boom -- they get the content.

So, that's a problem. But it can be dealt with by not enabling HTML email in your client.

Problem solved for PGP.

The underlying cause of all this has been known for over a decade, and a solution proposed at that time. Some email clients have ignored the solution.

Crypto maven Matthew Green -- he teaches crypto at John Hopkins University -- thinks the S/MIME attack is actually more interesting. He tweeted:

It's [the PGP attack] an extremely cool attack and kind of a masterpiece in exploiting bad crypto, combined with a whole lot of sloppiness on the part of mail client developers. The real news here is probably about S/MIME, which is actually used in corporate e-mail settings. Attacking and modifying encrypted email stored on servers could actually happen, so this is a big deal. Plus the attack on S/MIME is straightforward because it's (a) a dumb protocol, and (b) a simple protocol not filled with legacy cruft, and (c) it's built into email clients. Dumb and simple and one vendor to blame.

The real problem then is that Microsoft Outlook is broken from this, and it is routinely used for encrypted email in corporations and the military.

There may have to be company policy updates right now to stop email HTML from being used. No doubt Microsoft will fix it at some point.

The meta-lesson in all of this may be for the computing community. Don't panic. Take a breath and look at the facts.

Related posts:

— Larry Loeb has written for many of the last century's major "dead tree" computer magazines, having been, among other things, a consulting editor for BYTE magazine and senior editor for the launch of WebWeek.

Comment  | 
Print  | 
More Insights
Comments
Threaded  |  Newest First  |  Oldest First
COVID-19: Latest Security News & Commentary
Dark Reading Staff 8/10/2020
Pen Testers Who Got Arrested Doing Their Jobs Tell All
Kelly Jackson Higgins, Executive Editor at Dark Reading,  8/5/2020
Researcher Finds New Office Macro Attacks for MacOS
Curtis Franklin Jr., Senior Editor at Dark Reading,  8/7/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Special Report: Computing's New Normal, a Dark Reading Perspective
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
The Changing Face of Threat Intelligence
The Changing Face of Threat Intelligence
This special report takes a look at how enterprises are using threat intelligence, as well as emerging best practices for integrating threat intel into security operations and incident response. Download it today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-7029
PUBLISHED: 2020-08-11
A Cross-Site Request Forgery (CSRF) vulnerability was discovered in the System Management Interface Web component of Avaya Aura Communication Manager and Avaya Aura Messaging. This vulnerability could allow an unauthenticated remote attacker to perform Web administration actions with the privileged ...
CVE-2020-17489
PUBLISHED: 2020-08-11
An issue was discovered in certain configurations of GNOME gnome-shell through 3.36.4. When logging out of an account, the password box from the login dialog reappears with the password still visible. If the user had decided to have the password shown in cleartext at login time, it is then visible f...
CVE-2020-17495
PUBLISHED: 2020-08-11
django-celery-results through 1.2.1 stores task results in the database. Among the data it stores are the variables passed into the tasks. The variables may contain sensitive cleartext information that does not belong unencrypted in the database.
CVE-2020-0260
PUBLISHED: 2020-08-11
There is a possible out of bounds read due to an incorrect bounds check.Product: AndroidVersions: Android SoCAndroid ID: A-152225183
CVE-2020-16170
PUBLISHED: 2020-08-11
The Temi application 1.3.3 through 1.3.7931 for Android has hard-coded credentials.