Jump to content

OpenSSL swats a dozen bugs, one notable nasty


steven36

Recommended Posts

Denial of service dross dead

 

PVsIV66.jpg

 

A dozen flaws have been patched in OpenSSL, including one high severity hole that allows denial of service attacks.

 

The OpenSSL Project pushed patches in versions 1.1.0a, 1.0.2i and 1.0.1u, with most of the flaws flagged as low severity risks.

 

The nastiest vulnerability (CVE-2016-6304) results when attackers issue a massive OCSP status request extension which exhausts memory on servers in default configuration. Researcher Shi Lei of vulnerability blitzkrieg house Qihoo 360 spotted that one.

 

Admins can mitigate damage by running no-ocsp or by running older versions of OpenSSL below 1.0.1g.

 

Another moderate severity denial of service flaw (CVE-2016-6305) is fixed in the patch run which affects 1.0 of OpenSSL.

 

The OpenSSL project nixed risky ciphers in version 1.1 to squash the so-called Sweet32 exploit which is a birthday attack against 64-bit ciphers like Blowfish and Triple DES.

Cisco said it was difficult to exploit.

 

“For a successful attack, a large amount of data has to be sent one-way during the session, and the session has to be encrypted using the same key," Borg security engineers said.

"For 64-bit ciphers, it would take about 32GB of data in order to have a 50 percent probability of collision in any of the cipher blocks”.

 

Source:

http://www.theregister.co.uk/2016/09/23/openssl_swats_a_dozen_bugs_one_notable_nasty/

 

Link to comment
Share on other sites


  • Replies 1
  • Views 477
  • Created
  • Last Reply

OpenSSL Patches High-Severity OCSP Bug, Mitigates SWEET32 Attack

 

A vulnerability in the OpenSSL implementation of the Online Certificate Status Protocol (OCSP) was patched this week, closing a denial-of-service weakness in affected servers.

The patch was the most severe of 14 released yesterday by OpenSSL.

 

OCSP is an alternative in many cases to Certificate Revocation Lists where a client can use the protocol to ping a server requesting the status of a digital certificate.

 

The vulnerability, CVE-2016-6304, can be exploited by a malicious client by sending a large OCSP Status Request extension.

 

“If that client continually requests renegotiation, sending a large OCSP Status Request extension each time, then there will be unbounded memory growth on the server,” OpenSSL said in its advisory. “This will eventually lead to a denial of service attack through memory exhaustion.”

 

Researchers from Qihoo 360 of China privately disclosed the vulnerability.

 

“A server with default configuration would allow unbounded memory allocation of the OCSP ids every time a renegotiation occurs even if the server is not configured with OCSP,” Qihoo 360 said in its report on the bug. “The OCSP id can, according to the spec, consume up to 65,535 bytes of memory. Theoretically, an attacker could continually reneg with the server thus causing unbounded memory growth on the server up to 64k each time.”

 

The vulnerability affects default configurations of OpenSSL 1.1.0 and later; versions prior to 1.0.1g are not affected, OpenSSL said. OpenSSL 1.1.0 should be upgraded to 1.1.0a, 1.0.2 to 1.0.2i, and 1.0.1 to 1.0.1u.

 

“In 1.0.2 an attacker could grow the memory usage on the server by approx 16k per reneg as the maximum overall ClientHello size is set to 16,384 bytes,” Qihoo 360 said. “In version 1.1.0, along with the maximum size of a ClientHello increased to 131,396 bytes, the memory growth would be near 64k per reneg.”

 

Linux and BSD distributors Debian, Ubuntu, RedHat/CentOS and FreeBSD have also updated their respective software.

 

Of the remaining 13 vulnerabilities, patched, 12 were rated low severity by OpenSSL. The other was rated moderate severity and could lead to a denial-of-service condition where SSL or TLS would hang during a SSL_peek() call if an empty record is sent. The bug affected OpenSSL 1.1.0 and users are urged to upgrade to 1.1.0a.

 

OpenSSL also mitigated the SWEET32 vulnerability, CVE-2016-2183. Sweet32 was disclosed in August and affected 64-bit ciphers such as Triple-DES (3DES) and Blowfish and could allow an attacker to recover authentication cookie data from 3DES traffic, and usernames and passwords from OpenVPN traffic, which is secured by Blowfish.

 

As expected, OpenSSL moved 64-bit ciphers from the high cipherstring group to medium in OpenSSL 1.0.1 and 1.0.2. OpenSSL 1.1.0 disables these ciphersuites by default.

 

The attack is a collision attack against these ciphers in CBC mode, or cipher block chaining; 64-bit ciphers are still supported in TLS, IPsec, SSH and other protocols. The researchers said that 3DES support for HTTPS servers that show in Alexa’s top website list hovers between 1 percent and 2 percent of traffic on Firefox, Internet Explorer, Chrome and Android 5.0 integrated browser.

 

SWEET32 is one of the first relatively practical attacks against 64-bit suites, and can be executed with the resources at the disposal of a nation-state or well stocked criminal enterprise.

 

 

Source:

https://threatpost.com/openssl-patches-high-severity-ocsp-bug-mitigates-sweet32-attack/120845/

 

Link to comment
Share on other sites


Archived

This topic is now archived and is closed to further replies.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...