US-CERT warns DKIM email open to spoofing

Mathematician accidentally spots flaw


US-CERT has issued a warning that DomainKeys Identified Mail (DKIM) verifiers that use low-grade encryption are open to being spoofed and need to be upgraded to combat attackers wielding contemporary quantities of computing power.

You might think this is no big deal – after all the value of strong cryptography has been recognized for years. Unfortunately this problem has been found to affect some of the biggest names in the tech industry, including Google, Microsoft, Amazon, PayPal and several large banks.

The DKIM system adds a signature file to messages that can be checked to ascertain the domain of the sender by checking with DNS. It also takes a cryptographic hash of the message, using the SHA-256 cryptographic hash and RSA public key encryption scheme, so it can't be altered en route.

The problem stems from the very weak key lengths that are being used by companies that should know better. To make matters more embarrassing the problem was spotted by complete accident by Floridian mathematician Zachary Harris, who used it to spoof an email to Google CEO Larry Page.

Harris told Wired that he received an email from a Google recruiter, asking him to interview with the company for a site-reliability engineering position. Smelling a rat, he looked at the email in more depth and saw that Google was only using a 512-bit key, which isn’t particularly secure these days.

"A 384-bit key I can factor on my laptop in 24 hours," he said. "The 512-bit keys I can factor in about 72 hours using Amazon Web Services for $75. And I did do a number of those."

Thinking the recruiter might have introduced the vulnerability as a creative test if he was suitable for the job, Harris used the flaw to spoof and email to Larry Page from fellow co-founder Sergey Brin, in which he plugged his own website as something worthy of attention. He got no response, but two days later noticed Google had upped its key length to 2,048 bits and he was suddenly getting a lot of IP hits from the Chocolate Factory.

After doing some digging around Harris discovered this was a surprisingly common problem. Amazon, Twitter, eBay and Yahoo! were all using 512-bit keys and even Paypal and banks like HSBC were still on 768-bit systems, despite the standard recommending at least 1,028-bit as a minimum.

"Those are not factorable by a normal person like me with my resources alone. But the government of Iran probably could, or a large group with sufficient computing resources could pull it off," he warned.

Harris contacted those companies he had found were vulnerable and most, but not all, upgraded their systems to much higher keys. He also contacted CERT Coordination Center at Carnegie Mellon University so an alert could be put out before he went public.

Upgrading key length isn't difficult, but companies also need to revoke the old ones and remove test keys from files. Some receiving domains are still accepting test keys that have never been revoked he said.

With spoofed emails an increasing problem you'd think something so simple could have been spotted earlier. The industry still has a lot of catching up to do it seems. ®

Similar topics


Other stories you might like

  • Google Pixel 6, 6 Pro Android 12 smartphone launch marred by shopping cart crashes

    Chocolate Factory talks up Tensor mobile SoC, Titan M2 security ... for those who can get them

    Google held a virtual event on Tuesday to introduce its latest Android phones, the Pixel 6 and 6 Pro, which are based on a Google-designed Tensor system-on-a-chip (SoC).

    "We're getting the most out of leading edge hardware and software, and AI," said Rick Osterloh, SVP of devices and services at Google. "The brains of our new Pixel lineup is Google Tensor, a mobile system on a chip that we designed specifically around our ambient computing vision and Google's work in AI."

    This latest Tensor SoC has dual Arm Cortex-X1 CPU cores running at 2.8GHz to handle application threads that need a lot of oomph, two Cortex-A76 cores at 2.25GHz for more modest workloads, and four 1.8GHz workhorse Cortex-A55 cores for lighter, less-energy-intensive tasks.

    Continue reading
  • BlackMatter ransomware gang will target agriculture for its next harvest – Uncle Sam

    What was that about hackable tractors?

    The US CISA cybersecurity agency has warned that the Darkside ransomware gang, aka BlackMatter, has been targeting American food and agriculture businesses – and urges security pros to be on the lookout for indicators of compromise.

    Well known in Western infosec circles for causing the shutdown of the US Colonial Pipeline, Darkside's apparent rebranding as BlackMatter after promising to go away for good in the wake of the pipeline hack hasn't slowed their criminal extortion down at all.

    "Ransomware attacks against critical infrastructure entities could directly affect consumer access to critical infrastructure services; therefore, CISA, the FBI, and NSA urge all organizations, including critical infrastructure organizations, to implement the recommendations listed in the Mitigations section of this joint advisory," said the agencies in an alert published on the CISA website.

    Continue reading
  • It's heeere: Node.js 17 is out – but not for production use, says dev team

    EcmaScript 6 modules will not stop growing use of Node, claims chair of Technical Steering Committee

    Node.js 17 is out, loaded with OpenSSL 3 and other new features, but it is not intended for use in production – and the promotion for Node.js 16 to an LTS release, expected soon, may be more important to most developers.

    The release cycle is based on six-monthly major versions, with only the even numbers becoming LTS (long term support) editions. The rule is that a new even-numbered release becomes LTS six months later. All releases get six months of support. This means that Node.js 17 is primarily for testing and experimentation, but also that Node.js 16 (released in April) is about to become LTS. New features in 16 included version 9.0 of the V8 JavaScript engine and prebuilt Apple silicon binaries.

    "We put together the LTS release process almost five years ago, it works quite well in that we're balancing [the fact] that some people want the latest, others prefer to have things be stable… when we go LTS," Red Hat's Michael Dawson, chair of the Node.js Technical Steering Committee, told The Register.

    Continue reading

Biting the hand that feeds IT © 1998–2021