PGP Email has Critical Flaw

FrgMstr

Just Plain Mean
Staff member
2FA
Joined
May 18, 1997
Messages
58,693
PGP is a type of email encryption. PGP stands for "Pretty Good Privacy." PGP encryption is used by some of the bigger guys such as Apple Mail, Outlook, and Thunderbird. A critical vulnerability has been exposed by some German researchers and they have tweeted that there are no fixes available, and their immediate suggestion is to stop using PGP altogether. They suggest there will be more on the story released tomorrow and they did suggest that all of these companies that use PGP have been previously warned of this situation. EFF has a write up on this also with all the links you need if reading Twitter is not your thing.

UPDATE: It was just tweeted that due to information embargoes on this being broken, the full details of #efails attacks have been disclosed.



We'll publish critical vulnerabilities in PGP/GPG and S/MIME email encryption on 2018-05-15 07:00 UTC. They might reveal the plaintext of encrypted emails, including encrypted emails sent in the past.
 
Last edited:
PGP might most be commonly used in e-mail, but it's actually used for all kinds of stuff, such as file encryption.

Company doesn't support SFTP/FTPS to transfer files? Use FTP but pgp encrypt the file. Even if someone steals your username/password, the file(s) are encrypted separately.
 
so.. disable auto load of external HTML links, to bypass this vulnerability. OK, that should be a default nowadays anyways.

it is an interesting way around the encryption, but still requires some other comprise to begin with. and honestly, if they have that kind of access to your emails/internet streams to begin with, your screwed.
 
"Use our system! it is incredibly safe and secure!"

10 minutes later

"We regret to inform you that our system is not safe nor secure. Please discontinue using it."

Milkshake Duck, IT version.
 
PGP might most be commonly used in e-mail, but it's actually used for all kinds of stuff, such as file encryption.

Company doesn't support SFTP/FTPS to transfer files? Use FTP but pgp encrypt the file. Even if someone steals your username/password, the file(s) are encrypted separately.

It's worth noting that there is no risk to other applications using a PGP key-pair encryption method. (Hence, the recommendation to use an external app to decrypt e-mails and completely bypass this exploit.)

The problem lies in the way in which a PGP-enabled e-mail client weakly parses the multipart e-mail before decryption, and then, _without validation_, re-parses the decrypted content within the same context. By merely sending a malformed copy of a previously intercepted encrypted e-mail to the intended recipient, you can cause the e-mail client to attempt to access a newly attached hyperlink with the entire contents of the encrypted e-mail (or up until the string ">) at the end of the external URL, but decrypted. I can't express how stupid this is.

The fact this works at all demonstrates bad optimizations and lack of concern for implementation or separation of responsibility.
 
"Use our system! it is incredibly safe and secure!"

10 minutes later

"We regret to inform you that our system is not safe nor secure. Please discontinue using it."

Milkshake Duck, IT version.
This is not even close to true. In the case of PGP, it has been in use for DECADES. Not only that, PGP never claimed to be "incredibly safe and secure", just "pretty good".
 
This is not even close to true. In the case of PGP, it has been in use for DECADES. Not only that, PGP never claimed to be "incredibly safe and secure", just "pretty good".

It's hyperbolic. Of course it was more than 10 minutes.
 
It's hyperbolic. Of course it was more than 10 minutes.
There's hyperbole and exaggerations, but IMO you went over the line into the next category: outright lies. I've seen way too many people and products smeared, only to have the perp say, "just kidding". Sorry, doesn't wash.
 
Is it clear at this point that this is limited to email only, or could GnuPG applications for .deb's, git commits, etc?

If the latter is affected this is pretty damned bad.
 
There's hyperbole and exaggerations, but IMO you went over the line into the next category: outright lies. I've seen way too many people and products smeared, only to have the perp say, "just kidding". Sorry, doesn't wash.

Lighten up, Francis.
 
  • Like
Reactions: Mega6
like this
Is it clear at this point that this is limited to email only, or could GnuPG applications for .deb's, git commits, etc?

If the latter is affected this is pretty damned bad.

There is no opportunity to apply this sort of exploit to signing or verifying commits and packages. It is a much simpler process. The problem really is with e-mail clients acting more like browsers and glazing over malformed markup.
 
Who still uses PGP for any type of legitmate reason? Just curious.
 
Who still uses PGP for any type of legitmate reason? Just curious.

I would expect that most new projects would not use GPG, but there are a lot of important projects that have been around for decades that aren't going to get ported to new encryption schemes overnight.

Well, maybe now they will. :p

In general though, software doesn't get rewritten unless it absolutely needs to be. If existing code can do the job, even as part of a new release, it tends to be kept, as Long as integrating it takes less work that writing it from scratch.

Writing code takes time, and time costs money. For new code to be written, the cost savings or earnings potential must outweigh the cost of writing it.
 
well, it is pretty good protection not perfect protection. That is what you get for accepting sub par.
 
OpenPGP is used for TONS of things! Most notably, the versions implemented in GPG/GnuPrivacyGuard - the most complete and open source implementation thereof. Relatively few people except the technically adept use it "directly/manually", but it is used both directly and indirectly for lots of encryption of communications - probably some of the most commonly used public key cryptography around. Addons like Enigmail for Thunderbird (and pretty much any sort of email encryption feature or plugin) uses PGP, while even "automatic/in browser zero knowledge" setups like those from ProtonMail, Tutanota and a few other providers use it behind the scenes so to speak. It can also be used to encrypt files and whatnot, but symmetric crypto (ie AES) is often used for that instead. However, use for "signing" code, software packages and the like is another use.

From reading the page, it would seem that this is limited to email-related usages, in response to Zarathustra's question. It doesn't seem like many of the vectors that are described as necessary for the attack could be used in say... signing validation for a package or whatnot. Granted I don't know for sure the entire process of that kind of usage, but it doesn't seem like the exposed area would be sufficient and have the vulnerabilities described as opposed to an email type situation.

Honestly though, I wouldn't get bent out of shape about this. No software is ever entirely bug or exploit free and OpenPGP has been around for ages with good policy and practice. Looking at the attack, it will be very easy to close about 75% of the vectors with patches to clients and the software itself . There are even some short term countermeasures such as disabling HTML email that can protect in the meantime. Besides that, the next version of OpenPGP (and perhaps S/MIME) will update the spec to close this vulnerability entirely. Thanks to FLOSS development, this will mean probably patches and workarounds very, very quickly - especially with something so important. I'd be much more worried about proprietary software using old versions and implementations that will never get updated!
 
There is no opportunity to apply this sort of exploit to signing or verifying commits and packages. It is a much simpler process. The problem really is with e-mail clients acting more like browsers and glazing over malformed markup.


Yeah, there is a discussion on this now over on Reddit, and it appears to have been blown WAY out of proportion. The recommendation to cease using PGP, was probably just attention grabbing nonsense.

Lawnmover_Man said:
It's really way overhyped. Only HTML-Mails and external resources *and viewing them in buggy applications.

I mean, it's good they found this out and published it. But recommending de-installation of GnuPG plugins was just utter bullshit. As if they didn't get what they research themselves...

Honestly: Sounds like something other is on the table. People can't be that stupid.


 
Back
Top