News for hackers. Stuff that matters.
Re:Hacking Gmail’s UX with 'From' Fields – Another Phishing ... by amelius on Wednesday November 14, 2018 @03:34PM (#18453627)
Is someone collecting these attack vectors somewhere?

That would help prevent anyone writing an email client to make the same mistake.

Re:Hacking Gmail’s UX with 'From' Fields – Another Phishing ... by jorangreef on Thursday November 15, 2018 @02:59AM (#18457638)
I wrote @ronomon/mime, an email parser which enforces RFC 2822 3.6.2 and which also detects a variety of attack vectors before they can reach the email client.

A summary of these vectors are listed in the README (amongst various sanity checks): https://github.com/ronomon/mime#robust

Just through checking everything about an email carefully, @ronomon/mime has detected and brought to light some interesting attack vectors, for example a malformed email which crashes Apple Mail. This was disclosed to Apple's security team although they did not see any actual security implications.

Another interesting attack vector was an email containing millions of empty multiparts, which was able to crash several popular email servers. This was disclosed through Snyk, here are the details: https://snyk.io/blog/how-to-crash-an-email-server-with-a-sin...

Re:Hacking Gmail’s UX with 'From' Fields – Another Phishing ... by bo1024 on Thursday November 15, 2018 @08:47AM (#18459156)
My understanding is that email headers can be spoofed and should not be relied on. So this is probably too hard to ask from an email client (i.e. a program that reads and writes emails) that only has access to the email headers. Whereas for the email server (the computer that sends/receives emails for this address) this would be trivial, just keep a list of emails that the server has sent.