Skip to content
MD-5

Choose which cookies we can use. You can change this at any time from “Cookie settings” at the bottom of every page.

Triple DES (3DES): how it works and why it's being retired

How Triple DES works, why its 64-bit block led to the Sweet32 attack and its retirement, and how to remove the 3DES cipher suites that vulnerability scans flag.

By Updated 6 min read

On this page

Triple DES (3DES) kept DES-based systems secure for two decades by running the cipher three times. It has now been retired: NIST disallowed it for encryption after 2023. Most people meet 3DES today as a line in a vulnerability scan, “SWEET32: 64-bit block cipher enabled”, rather than as a cipher they chose.

This guide explains how 3DES works, the research that ended it, and how to remove it from the systems where it lingers. For background on the original cipher, see the DES guide.

What Triple DES is

3DES (formally TDEA, the Triple Data Encryption Algorithm) applies DES three times to each 64-bit block. It fixed DES’s fatal weakness, the short key, while letting banks and payment networks keep hardware and protocols built around DES.

It was standardized in ANSI X9.52 (1998) and FIPS 46-3 (1999), then specified in NIST SP 800-67 (opens in a new tab).

Encrypt-decrypt-encrypt

Each block goes through three stages:

  1. Encrypt with key 1.
  2. Decrypt with key 2.
  3. Encrypt with key 3.

The middle step is decryption for compatibility: if all three keys are the same, the first two steps cancel and 3DES behaves exactly like single DES. That let upgraded equipment keep talking to equipment that hadn’t been upgraded.

Why three passes, not two

Double DES looks like it should give 112 bits of security, but it doesn’t, because of the meet-in-the-middle attack (Diffie and Hellman, 1977; Merkle and Hellman, 1981). With one known plaintext and ciphertext, an attacker encrypts the plaintext under every possible first key, decrypts the ciphertext under every possible second key, and looks for a match in the middle. That costs roughly 2^57 operations plus a lot of memory, barely more than single DES. A third pass defeats the simple version of this attack, which is why the construction is triple.

Keying options and real strength

Variant Key material NIST security strength
Three-key 3DES (3TDEA) 168 bits 112 bits
Two-key 3DES (2TDEA), key 3 = key 1 112 bits 80 bits or less

Meet-in-the-middle caps three-key 3DES at about 112 bits of security despite its 168-bit key. That is still far beyond brute force. Two-key 3DES is weaker again and was disallowed for encryption after 2015. Neither was retired because of its key. Both were retired because of their block.

The 64-bit block and Sweet32

Tripling DES lengthened the key but kept DES’s 64-bit block. With 64-bit blocks there are only 2^64 possible ciphertext blocks, so by the birthday bound you expect two identical blocks after about 2^32 blocks, roughly 32 GB, under one key. In CBC mode, two identical ciphertext blocks reveal the XOR of the two plaintext blocks behind them. If the attacker knows or controls one, they learn the other.

In 2016 Karthikeyan Bhargavan and Gaëtan Leurent turned this into a practical attack, Sweet32 (opens in a new tab) (CVE-2016-2183 for 3DES). Using JavaScript in a victim’s browser to generate a large volume of HTTPS requests over one long-lived connection:

  • they recovered a secure HTTP session cookie encrypted with 3DES from 610 GB of traffic captured in 30.5 hours;
  • the same technique against OpenVPN, which then defaulted to Blowfish, recovered a secret from 705 GB in 18.6 hours.

At the time, they measured that 86% of TLS servers still supported 3DES.

The response was fast. NIST limited 3DES to 2^20 blocks (about 8 MB) per key bundle in SP 800-67 Rev. 2, browsers dropped 3DES, and OpenVPN moved to AES-GCM. A cipher you must rekey every eight megabytes has no place in modern protocols.

Compliance status

  • NIST: SP 800-131A Rev. 2 (opens in a new tab) disallowed 3DES for encryption after December 31, 2023. Decryption of legacy data is still allowed so records can be migrated. NIST withdrew SP 800-67 itself on January 1, 2024.
  • TLS: TLS 1.3 (RFC 8446 (opens in a new tab)) has no 3DES cipher suites, and the IETF’s current TLS recommendations (RFC 9325 (opens in a new tab)) advise against suites offering less than 128 bits of security, which rules 3DES out.
  • PCI DSS: “strong cryptography” requires at least 112 bits of effective key strength. Three-key 3DES technically meets that number, but 3DES in TLS fails assessments because of Sweet32, and card networks have been retiring it from PIN and key-management systems on published timelines.

If you still depend on 3DES, the realistic position is a documented exception with a migration date, not continued use.

Fixing the Sweet32 finding

3DES most often appears as a scan result: Nessus, Qualys, OpenVAS and SSL Labs all flag servers still offering 64-bit block ciphers, usually as “SSL Medium Strength Cipher Suites Supported (SWEET32)” or CVE-2016-2183. It turns up on load balancers, mail servers (SMTP, IMAP), VPN gateways and older Windows servers running IIS or RDP.

Remove 3DES, and any other 64-bit block cipher, from the server’s cipher list:

  • nginx: set an explicit ssl_ciphers list of AES-GCM and ChaCha20 suites (Mozilla’s “intermediate” configuration is a good start) and ssl_protocols TLSv1.2 TLSv1.3.
  • Apache httpd: the same through SSLCipherSuite, plus SSLProtocol -all +TLSv1.2 +TLSv1.3.
  • Windows (IIS, RDP): disable the “Triple DES 168” cipher in the SCHANNEL registry settings or through Group Policy, then reboot. Test RDP afterwards, because very old clients may fail to connect.
  • Appliances and cloud load balancers: choose a current TLS security policy in the vendor console. Older default policies often still include 3DES.

Then rescan to confirm the finding is gone. It’s usually a one-line change with no effect on real users. A vulnerability assessment checks every internet-facing service for this and other weak TLS settings at once.

Where else 3DES survives

  • Payment hardware: PIN pads, ATMs and HSMs on long replacement cycles, being phased out under card-network deadlines.
  • Data at rest: archives encrypted years ago. Decrypt and re-encrypt them under AES, which NIST explicitly allows.
  • Partner integrations: file transfers and VPN tunnels to partners who haven’t migrated. Isolate them behind a gateway and agree a retirement date.
  • Windows domains: 3DES appears alongside DES in legacy Kerberos and IPsec settings, covered in the DES guide.

If you can’t remove it yet

  • Use three independent keys. Two-key 3DES offers 80 bits of security or less.
  • Rekey aggressively. Stay well under 2^20 blocks (8 MB) per key. This data limit is the practical risk, not brute force.
  • Keep keys in an HSM, generated randomly and never exported in clear.
  • Restrict exposure. Make sure the legacy interface isn’t reachable from the internet, and monitor it.
  • Set a date. Every exception needs an owner and a planned end.

For anything new, use AES-GCM. The AES vs DES comparison explains why the gap is so large.

Sources

Published by

· Certified cybersecurity services

Articles are researched and written in-house and link to their primary sources (standards, advisories, papers and public datasets) so you can check every claim. Spotted an error? Email contact@md-5.com and we’ll correct it.