Risk
8/1/2009
11:50 PM
George V. Hulme
George V. Hulme
Commentary
50%
50%

Is AES On The Way Out?

Cryptographic researchers have uncovered a new attack against the ubiquitous AES encryption algorithm. While there have been a number of complex attack aimed at AES recently, this one, experts warn, may be practical enough for run-of-the-mill attackers to exploit.

Cryptographic researchers have uncovered a new attack against the ubiquitous AES encryption algorithm. While there have been a number of complex attack aimed at AES recently, this one, experts warn, may be practical enough for run-of-the-mill attackers to exploit.The Advanced Encryption Standard (AES) was selected by the U.S. Department of Commerce in October 2000 to replace the then de facto standard, triple DES. Today, AES is one of the most widely used algorithms for symmetric key cryptography. Symmetric key cryptography, like the name implies, is when the keys for encryption and decryption are either the same, or only slightly different. Generally, it's a shared secret between the person encrypting something, and those with the key to decrypt the information.

Well a group of researchers, including Adi Shamir (whose last name puts the S in the RSA algorithm) and Alex Biryukov, Orr Dunkelman, Nathan Keller and Dmitry Khovratovich.

The paper, which details the attack, has yet to be made public. Brice Schneier has read the paper, and provided a peek on his Web site:

In this paper we describe several attacks which can break with practical complexity variants of AES-256 whose number of rounds are comparable to that of AES-128. One of our attacks uses only two related keys and 239 time to recover the complete 256-bit key of a 9-round version of AES-256 (the best previous attack on this variant required 4 related keys and 2120 time). Another attack can break a 10 round version of AES-256 in 245 time, but it uses a stronger type of related subkey attack (the best previous attack on this variant required 64 related keys and 2172 time).

The paper, detailing the attack technique, should be available within days. For now, Schneier is recommending people not use AES-256 and that AES-128 "provides more than enough security margin for the foreseeable future."

Let's hope so.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
IIWK1101@IWK.COM152
50%
50%
IIWK1101@IWK.COM152,
User Rank: Apprentice
11/1/2011 | 9:44:43 AM
re: Is AES On The Way Out?
I Agree
IIWK1101@IWK.COM152
50%
50%
IIWK1101@IWK.COM152,
User Rank: Apprentice
11/1/2011 | 9:44:33 AM
re: Is AES On The Way Out?
Nice Blog
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Dark Reading December Tech Digest
Experts weigh in on the pros and cons of end-user security training.
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2014-3407
Published: 2014-11-27
The SSL VPN implementation in Cisco Adaptive Security Appliance (ASA) Software 9.3(.2) and earlier does not properly allocate memory blocks during HTTP packet handling, which allows remote attackers to cause a denial of service (memory consumption) via crafted packets, aka Bug ID CSCuq68888.

CVE-2014-4829
Published: 2014-11-27
Cross-site request forgery (CSRF) vulnerability in IBM Security QRadar SIEM and QRadar Risk Manager 7.1 before MR2 Patch 9 and 7.2 before 7.2.4 Patch 1, and QRadar Vulnerability Manager 7.2 before 7.2.4 Patch 1, allows remote attackers to hijack the authentication of arbitrary users for requests tha...

CVE-2014-4831
Published: 2014-11-27
IBM Security QRadar SIEM and QRadar Risk Manager 7.1 before MR2 Patch 9 and 7.2 before 7.2.4 Patch 1, and QRadar Vulnerability Manager 7.2 before 7.2.4 Patch 1, allow remote attackers to hijack sessions via unspecified vectors.

CVE-2014-4832
Published: 2014-11-27
IBM Security QRadar SIEM and QRadar Risk Manager 7.1 before MR2 Patch 9 and 7.2 before 7.2.4 Patch 1, and QRadar Vulnerability Manager 7.2 before 7.2.4 Patch 1, allow remote attackers to obtain sensitive cookie information by sniffing the network during an HTTP session.

CVE-2014-4883
Published: 2014-11-27
resolv.c in the DNS resolver in uIP, and dns.c in the DNS resolver in lwIP 1.4.1 and earlier, does not use random values for ID fields and source ports of DNS query packets, which makes it easier for man-in-the-middle attackers to conduct cache-poisoning attacks via spoofed reply packets.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
Now that the holiday season is about to begin both online and in stores, will this be yet another season of nonstop gifting to cybercriminals?