Sunday, March 2, 2025
HomeCryptocurrency hackDUHK Attack allows Hackers to Recover Encryption Keys and Decrypt Communications Passing...

DUHK Attack allows Hackers to Recover Encryption Keys and Decrypt Communications Passing Over VPN

Published on

SIEM as a Service

Follow Us on Google News

DUHK attack targets the old vulnerability that resides in the pseudorandom number generator called ANSI X9.31. It is an algorithm widely used to generate cryptographic keys that secure VPN connections and web browsing sessions.

ANSI X9.31 PRNG is a pseudorandom number generator algorithm design that was incorporated into different structures cryptographic standards and listed as recommended RNG for FIPS certification for decades.

DUHK attack allows hackers to recover encryption keys and to decrypt the encrypted web traffic.This vulnerability hits devices utilizing ANSI X9.31 Random Number Generator (RNG) in combination with a hard-coded seed key. This cryptographic attack followed by Factorization Attack and KRACK Attack.

Researchers wrote We performed a systematic study of publicly available FIPS 140-2 certifications for hundreds of products that implemented the ANSI X9.31 random number generator, and found twelve whose certification documents use of static hard-coded keys in the source code, leaving them vulnerable to an attacker who can learn this key from the source code or binary.

DUHK was developed by researchers at the University of Pennsylvania and Johns Hopkins University: Shaanan Cohney, Nadia Heninger, and Matthew D. Green.

Devices Vulnerable to DUHK Attack

For demonstration, researchers developed a full passive decryption attack against FortiGate VPN gateway products using FortiOS version 4 and they were able to recover the random number generator state for 21% of HTTPS hosts serving a default Fortinet product certificate.

Researchers used ZMap to perform Internet-wide scans on port 443 for HTTPS and port 500 to measure the population of vulnerable Fortinet devices and they found 23,000 devices are running a vulnerable version of FortiOS.

FortiGate devices with FortiOS 4.3.0 to FortiOS 4.3.18 are vulnerable to DUHK attacks and Fortigate fixed it by implementing CTR_DRBG from FortiOS 4.3.19, 5.0.(CVE-2016-8492).

Researchers provided a list of the Hardware and software products that are vulnerable to DUHK.

AM I Vulnerable?

X9.31 RNG was removed FIPS list of approved RNGs in 2016. If your product was certified after 2016 then you are not vulnerable.

The x9.31 vulnerability is symmetric, and any implementation that stores a fixed secret key in code or hardware is vulnerable to passive exploitation by an attacker who can recover the key through reverse engineering.

Updating software regularly is a good practice to protect you against flaws. More details on DUHK attack found in the dedicated page or the blog post by Matthew Green.

Gurubaran
Gurubaran
Gurubaran is a co-founder of Cyber Security News and GBHackers On Security. He has 10+ years of experience as a Security Consultant, Editor, and Analyst in cybersecurity, technology, and communications.

Latest articles

Network Penetration Testing Checklist – 2025

Network penetration testing is a cybersecurity practice that simulates cyberattacks on an organization's network...

Hackers can Crack Into Car Cameras Within Minutes Exploiting Vulnerabilities

At the upcoming Black Hat Asia 2025 conference, cybersecurity experts will unveil a groundbreaking...

Chinese Hackers Breach Belgium State Security Service as Investigation Continues

Belgium’s State Security Service (VSSE) has suffered what is being described as its most...

Hacktivist Groups Emerge With Powerful Tools for Large-Scale Cyber Operations

Hacktivism, once synonymous with symbolic website defacements and distributed denial-of-service (DDoS) attacks, has evolved...

Supply Chain Attack Prevention

Free Webinar - Supply Chain Attack Prevention

Recent attacks like Polyfill[.]io show how compromised third-party components become backdoors for hackers. PCI DSS 4.0’s Requirement 6.4.3 mandates stricter browser script controls, while Requirement 12.8 focuses on securing third-party providers.

Join Vivekanand Gopalan (VP of Products – Indusface) and Phani Deepak Akella (VP of Marketing – Indusface) as they break down these compliance requirements and share strategies to protect your applications from supply chain attacks.

Discussion points

Meeting PCI DSS 4.0 mandates.
Blocking malicious components and unauthorized JavaScript execution.
PIdentifying attack surfaces from third-party dependencies.
Preventing man-in-the-browser attacks with proactive monitoring.

More like this

Stablecoin Bank Hit by Cyberattack, Loses $49.5M to Hackers

The cryptocurrency sector faced one of its most significant security breaches this year as...

Biggest Crypto Hack in History – Hackers Stolen $1.46 Billion Worth Crypto From Bybit

In what has become the largest cryptocurrency theft in history, hackers infiltrated Bybit’s Ethereum...

Malicious Solana Packages Attacking Devs Abusing Slack And ImgBB For Data Theft

Malicious packages "solanacore," "solana login," and "walletcore-gen" on npmjs target Solana developers with Windows...