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. [1]
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 [2] 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 [3]. DROWN only affects SSLv2 while Heartbleed affects everything. Time will tell the impact of DROWN vulnerability.
Recommend solution
- 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 has also successfully fenced off other critical open source bugs like Heartbleed and Glibc.
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.
Reference
- https://www.openssl.org/news/secadv/20160301.txt
- https://drownattack.com/top-sites.html
- http://www.cio.com/article/3023692/security/5-biggest-cybersecurity-concerns-facing-cios-cisos-in-2016.html
Photo credits: Imcreator
Most Recent Articles
- A beginner-friendly intro to the Correlator for effective cybersecurity detection
- Inotify in ASAB Library
- From State Machine to Stateless Microservice
- Entangled ways of product development in the area of cybersecurity #3 - LogMan.io
- Entangled ways of product development in the area of cybersecurity #2 - BitSwan
You Might Be Interested in Reading These Articles
Why You Need Security Audit for Your Point-of-Sale (POS) System
It’s clear that POS systems are a source of important and valuable data, and have the power to either speed up the progress or to stop the development of a company, depending on whether or not they are used. POS data is a business asset. Despite this vital importance, such an asset is not afforded the protection it deserves.
Published on March 07, 2017
Are You Ready for The New European General Data Protection (GDPR) Law?
A new EU regulation, European General Data Protection Regulation (GDPR) has been proposed to improve the data protection of individuals. This regulation is the subsequent to the 1995 directive. It was agreed on 17 December 2015 and its implementation starts from 2018.
Published on July 12, 2016
TeskaLabs’ Technology SeaCat Unaffected by GNU C Library Security Vulnerability (CVE-2015-7547)
TeskaLabs, a Prague and London based startup in application security, today affirmed that their core products are not exposed to the GLibC flaw, a highly critical security vulnerability. There is now a rapidly growing number of IoT devices that use Linux as their operating system and inherently GLibC.
Published on February 17, 2016