The mystery high-severity flaw that people were expected to be fixed in OpenSSL is no Heartbleed, but it is serious and users should update.
Earlier this week, the OpenSSL Project advised users that patches scheduled to be released Thursday will address several security flaws, one of which was classified as high severity. The announcement gave rise to speculation and some people thought the upcoming vulnerability might have wide-ranging impact, on par with the critical Heartbleed flaw disclosed last April, which affected Web servers, client software, mobile apps and even hardware appliances.
OpenSSL released versions 1.0.2a, 1.0.1m, 1.0.0r and 0.9.8zf Thursday to address 12 flaws, but not all OpenSSL versions were affected by all 12 flaws.
The most serious of those vulnerabilities is tracked as CVE-2015-0291 and can lead to denial-of-service attacks. The issue only affects the 1.0.2 branch of OpenSSL.
"If a client connects to an OpenSSL 1.0.2 server and renegotiates with an invalid signature algorithms extension, a NULL pointer dereference will occur," the OpenSSL Project said in a security advisory.
A remote attacker could exploit the bug to cause servers to crash, which could lead to denial of service, OpenSSL Project member Mark Cox explained in a blog post. However, the number of possible targets will be limited, because OpenSSL 1.0.2 was only released a few months ago, so many servers are likely not using it yet, he said.
OpenSSL maintains several different major versions at the same time, so users of OpenSSL 1.0.1, for example, have no reason to upgrade to 1.0.2 if they don't need the new features. They will continue to receive security patches for the 1.0.1 version.
According to Cox, David Ramos of Stanford University, who found and reported the CVE-2015-0291 vulnerability, developed a proof-of-concept exploit, but did not release it publicly.
However, Trey Ford, global security strategist at security firm Rapid7, believes that others will reverse engineer the patch and develop the attack code relatively quickly.
"Steps to push these fixes to internet exposed systems should be prioritized," he said via email.
On Thursday, the OpenSSL Project also reclassified the FREAK vulnerability as high severity. The flaw, which was publicly disclosed at the beginning of March, could allow man-in-the-middle attackers to downgrade the security of SSL connections and then crack the encryption keys protecting them.
The flaw was quietly patched in OpenSSL in January, but it was classified as low severity at the time because it can only be used to attack connections to servers that support an outdated cipher suite known as RSA export, a condition that was thought to be rare.
However, recent studies have shown that support for RSA export cipher suites is far more common than previously believed, which is why the vulnerability has been reclassified as high severity, the OpenSSL Project said.
The new OpenSSL patches also address eight moderate-severity flaws, some of which can also be used for denial-of-service attacks under certain conditions, as well as three low severity issues.
Because its announcement of an upcoming high severity vulnerability generated confusion, the project might change the way in which it classifies flaws.
"We need another security classification; HIGH scared everyone needlessly," said Rich Salz, an OpenSSL Project member on Twitter. "We'll update the policy soon."
There have been previous instances of critical flaws in OpenSSL, so by now CISOs and IT security teams should have a refined process in place for dealing with them, said Cris Thomas, strategist at Tenable Network Security, via email. "It should be a simple matter of following the procedures you developed based on the previous instances."
Join the CIO New Zealand group on LinkedIn. The group is open to CIOs, IT Directors, COOs, CTOs and senior IT managers.