Vulnerabilities / Threats

7/9/2015
01:55 PM
Connect Directly
Twitter
RSS
E-Mail
100%
0%

OpenSSL Fixes High-Severity, Narrow-Scope Vulnerability

Bug allows attackers to issue invalid certificates, but is difficult to exploit and only affects OpenSSL versions released since last month.

Today, OpenSSL released a fix for a new "high-severity" vulnerability that could enable man-in-the-middle attackers to impersonate a certificate authority, issue invalid certs, trick applications into treating the invalid cert like a legitimate one, and intercept or modify "secure" communications. The vulnerability, CVE-2015-1793, impacts any application that verifies certificates, including SSL/TLS/DTLS clients and servers.

Sounds bad, but the bug only affects OpenSSL versions 1.0.1n, 1.0.1o, 1.0.2b, and 1.0.2c, the oldest of which was released in June. No exploits have been reported so far, and security researchers say that exploitation would not be easy.

CVE-2015-1793 is an alternative chains certificate forgery bug. As the advisory explains:

    During certificate verification, OpenSSL (starting from version 1.0.1n and 1.0.2b) will attempt to find an alternative certificate chain if the first attempt to build such a chain fails. An error in the implementation of this logic can mean that an attacker could cause certain checks on untrusted certificates to be bypassed, such as the CA flag, enabling them to use a valid leaf certificate to act as a CA and "issue" an invalid certificate.

Users of 1.0.1n /1.0.1o have been advised to upgrade to 1.0.1p and users of 1.0.2b/1.0.2c have been advised to upgrade to 1.0.2d.

Although the vulnerability could be nasty, experts say it is not in the same category of other recent SSL vulnerabilities like Heartbleed and FREAK. First, because it requires that the attacker already have a certain degree of access to the target.

According to Chris Eng, vice-president of research for Veracode, exploiting CVE-2015-1793 "is not quick or easy, making it nowhere near as serious as Heartbleed. For starters, an attacker can’t simply directly attack a vulnerable server due to the nature of the vulnerability.

"Going after an individual is also challenging," Eng says, "since the major browsers -- Chrome, Firefox, IE -- don’t use OpenSSL. Even if a user with a vulnerable niche browser were to be targeted, the culprit would have to first deploy a man-in-the-middle (MitM) attack to get access to the browser itself. From there, they would need to serve a forged certificate to the browser directly."

"This vulnerability is only useful to an active attacker who is already capable of performing a man-in-the-middle (MITM) attack, either locally or upstream from the victim," Tod Beardsley of Rapid7 wrote today. "This limits the feasibility of attacks to actors who are already in a privileged position on one of the hops between the client and the server, or locally on the same LAN and can impersonate DNS servers or gateway routers. In short, the vulnerability is not useful for passive attacks, or for widespread, untargeted attacks."

Further, the scope of the attack is narrow.

"Since the bug only affects a few OpenSSL versions that were released in June 2015," says Eng, "major operating systems like RHEL, Ubuntu and CentOS are not vulnerable since they hadn’t yet incorporated the problematic updates at time of release."

"A certificate validation flaw in a TLS library largely affects only clients," says Ivan Ristic, director of engineering at Qualys. "Servers need certificate validation only when mutual authentication is enabled, which is a minor use case. ...  there's certainly lots of server-type tools that might use OpenSSL for client operations. For them, this vulnerability is potentially significant, but attackers would need to exploit them on a case-by-case basis. As such, this is nowhere near Heartbleed."

"To be clear," says Eng, "this is a bad vulnerability and a nice find by the BoringSSL team; however, the overall impact is expected to be minimal.”

Sara Peters is Senior Editor at Dark Reading and formerly the editor-in-chief of Enterprise Efficiency. Prior that she was senior editor for the Computer Security Institute, writing and speaking about virtualization, identity management, cybersecurity law, and a myriad ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
'Hidden Tunnels' Help Hackers Launch Financial Services Attacks
Kelly Sheridan, Staff Editor, Dark Reading,  6/20/2018
Tesla Employee Steals, Sabotages Company Data
Jai Vijayan, Freelance writer,  6/19/2018
Inside a SamSam Ransomware Attack
Ajit Sancheti, CEO and Co-Founder, Preempt,  6/20/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-12633
PUBLISHED: 2018-06-22
An issue was discovered in the Linux kernel through 4.17.2. vbg_misc_device_ioctl() in drivers/virt/vboxguest/vboxguest_linux.c reads the same user data twice with copy_from_user. The header part of the user data is double-fetched, and a malicious user thread can tamper with the critical variables (...
CVE-2018-12634
PUBLISHED: 2018-06-22
CirCarLife Scada v4.2.4 allows remote attackers to obtain sensitive information via a direct request for the html/log or services/system/info.html URI.
CVE-2018-12635
PUBLISHED: 2018-06-22
CirCarLife Scada v4.2.4 allows unauthorized upgrades via requests to the html/upgrade.html and services/system/firmware.upgrade URIs.
CVE-2018-12630
PUBLISHED: 2018-06-21
NEWMARK (aka New Mark) NMCMS 2.1 allows SQL Injection via the sect_id parameter to the /catalog URI.
CVE-2018-12631
PUBLISHED: 2018-06-21
Redatam7 (formerly Redatam WebServer) allows remote attackers to read arbitrary files via /redbin/rpwebutilities.exe/text?LFN=../ directory traversal.