OpenSSL DROWN Vulnerability Affects Millions of HTTPS Websites and Software Supporting SSLv2
University researchers from Israel, Germany and the USA; together with Hashcat Project, OpenSSL community and Google; have recently published a paper reporting a critical vulnerability (CVE-2016-0800), which is also referred to as DROWN (Decrsypting RSA with Obsolete and Weakened eNcryption).
DROWN is caused by legacy OpenSSL SSLv2 protocol, which is known to have many deficiencies and thus, it is condemned since 1996. For many years, security experts have recommended to turn it off. There is no need to use this 20-year-old protocol, but apparently many servers still support it because disabling SSLv2 requires non-default reconfiguration of the SSL cryptographic settings which is not easy for common IT people who have limited security knowledge and don’t know the location to disable this protocol and the way to disable it.
This cross-protocol vulnerability allows the cyber attackers to exploit servers using SSLv2, thus decrypting secure communications based on SSL/TLS. “SSL traffic between clients and non-vulnerable servers can be decrypted too provided another server supporting SSLv2 (even with a different protocol such as SMTP, IMAP or POP) shares the RSA keys of the non-vulnerable server,” said OpenSSL organization. 
Hackers can take advantage of DROWN vulnerability and perform a Man-in-the-Middle (MitM) type of attack. In a MitM attack, hackers trick the servers to steal the encryption key. They can use this key to decode encrypted messages and steal sensitive data like credit cards, email messages, passwords, trade secrets and financial information.
An example of a DROWN attack
Surprisingly, the world’s known brands  like Yahoo, Buzzfeed, Groupon, Sina have got their websites affected by DROWN vulnerability. Keeping this in view,it can be inferred that more companies still rely on servers that support this legacy protocol and are likely to fall a victim of cyber attacks.
OpenSSL is a cryptographic library used in many server products. It is difficult to know all the affected ones. The situation continue to becoming more urgent because the attack can be done in minutes, and the vulnerability is now disclosed. DROWN has been regarded as the new Heartbleed by many. Heartbleed is another OpenSSL vulnerability which was found in 2014. It is problematic and is one of the top five biggest security concerns for CIOs and CISOs in 2016 . DROWN only affects SSLv2 while Heartbleed affects everything. Time will tell the impact of DROWN vulnerability.
- Check web servers that implement OpenSSL, disable SSLv2 in your SSL configuration and upgrade your server software to the new OpenSSL version.
- Check certificates or keys and make sure that they are not used in servers or software that support SSLv2. If this is true, consider them as being compromised.
- Re-issuing a new certificate is not mandatory but can be taken as precautionary measure to prevent DROWN attacks.
How SeaCat keeps your backend resources safe from DROWN vulnerability?
SeaCat never implements SSLv2 protocol, having disabled it from day one. SeaCat uses TLS1.2 exclusively and has very strict configuration of ciphers. SeaCat Gateways are, therefore, unaffected. However, we still release an updated version of SeaCat with the new OpenSSL 1.0.2g.
SeaCat is the core technology behind SeaCat Mobile Secure Gateway and IoT/M2M Application Security Platform, which protects mobile, IoT/M2M applications, the communication channel and application backends.
If your mobile/IoT application is secured by SeaCat and monitored by our Network Security Center, you don’t have to worry. The application is immune from this vulnerability. If you are unsure, contact us today to request a FREE Demo or learn about our Application Security technology and how we can help you with the security of your mobile app and its backend systems.
Photo credits: Imcreator
You Might Be Interested in Reading These Articles
The official source of OpenSSL software is the OpenSSL website. One can download OpenSSL source codes archives and compile them for a given platform. The compilation work can sometimes be quite tedious, especially for exotic platforms. We, at TeskaLabs, set up this page because we frequently compile OpenSSL for various platforms for our internal purposes and this may save some time to other developers.
Published on July 20, 2017
Apple will want to dominate the market for TV apps. To achieve this objective, it’s understandable that Apple makes it easy for app developers to create apps and games for the Apple TV platform using tvOS and profit from them just as they have already done so for the iPhone and iPad devices. Developers can leverage similar frameworks and technologies since tvOS is just a modified version of the iOS. They can even retrofit the apps that were previously developed for iOS to support the Apple TV’s tvOS.
Published on June 29, 2016
With APIs (Application Programming Interfaces) becoming a crucial factor in any web or mobile application, security feels more like a journey than a destination. Of all the constituents that encompass an application, API gateway offers easy access points for a hacker to break in and steal your data. A single error in API can cause immense problems for any organization using your API.
Published on November 22, 2016