Significant OpenSSL Vulnerability (CVE-2014-0160) with PoC the wild. While only a CVSS 5, due to its memory grabbing ability, this is a CODE UPGRADE-NOW. This is OpenSSL vulnerability is testable with this tool live by Filippo Valsorda and detailed at Heartbleed.com. Testing is also avaialble via Qualys' online SSL Labs tool.
"Ever since the Heartbleed flaw in OpenSSL was made public there have been various questions about who knew what and when. The Sydney Morning Herald has done some analysis of public mailing lists and talked to those involved with disclosing the bug to get the bottom of it. The newspaper finds that Google discovered Heartbleed on or before March 21 and notified OpenSSL on April 1. Other key dates include Finnish security testing firm Codenomicon discovering the flaw independently of Google at 23:30 PDT, April 2. SuSE, Debian, FreeBSD and AltLinux all got a heads up from Red Hat about the flaw in the early hours of April 7 — a few hours before it was made public. Ubuntu, Gentoo and Chromium attempted to get a heads up by responding to an email with few details about it but didn't, as the guy at Red Hat sending the disclosure messages out in India went to bed. By the time he woke up, Codenomicon had reported the bug to OpenSSL."
UNK, bennyboy64, and samzenpus UNK. "Heartbleed Disclosure Timeline Revealed - Slashdot." Heartbleed Disclosure Timeline Revealed - Slashdot. http://it.slashdot.org/story/14/04/14/2013221/heartbleed-disclosure-timeline-revealed (accessed April 14, 2014).
Center for Internet Security Advisory
CIS ADVISORY NUMBER:
OpenSSL TLS 'heartbeat' Extension Information Disclosure Vulnerability
A vulnerability has been discovered in OpenSSL’s implementation of the TLS ‘heartbeat’ extension that could allow for the disclosure of sensitive information. OpenSSL is an open-source implementation of the SSL protocol used by a number of other projects. SSL (Secure Sockets Layer) is a protocol that ensures secure communication over the Internet via encryption. This issue could allow an attacker to compromise the private key and other sensitive data stored in memory.
Proof-of-concept code has been released. This vulnerability was first included in OpenSSL release 1.0.1 on 14th of March 2012. OpenSSL 1.0.1g released on 7th of April 2014 fixes the issue. Software products known to be using OpenSSL are the open source web servers Apache and nginx. According to Netcraft's April 2014 Web Server Survey (http://news.netcraft.com/archives/2014/04/02/april-2014-web-server-survey.html) of 958,919,789 websites, the combined market share of these products on the Internet was over 66%.
· OpenSSL versions 1.0.1 to 1.0.1f
· Large and medium government entities: High · Small government entities: High Businesses:
· Large and medium business entities: High · Small business entities: High
Home users: High
An information disclosure vulnerability has been discovered in OpenSSL’s implementation of the TLS ‘heartbeat’ extension that could allow for an attacker to obtain sensitive information residing in memory. This issue occurs because OpenSSL fails to conduct proper bounds checks when handling TLS ‘heartbeat’ packets. Up to 64KB of memory from either the client or the server can be recovered by an attacker and could allow an attacker to compromise the private key and other sensitive data in memory. It is known to be used on various platforms including Linux and Mac OS X.
· OpenSSL 1.0.1g is NOT vulnerable. · OpenSSL 1.0.0 branch is NOT vulnerable · OpenSSL 0.9.8 branch is NOT vulnerable
More information about this threat as well as a web-based testing tool is available at: http://heartbleed.com
We recommend the following actions be taken:
· Apply appropriate updates provided by the OpenSSL project to affected systems immediately after appropriate testing. · Remind users not to visit un-trusted websites or follow links provided by unknown or un-trusted sources. · Inform and educate users regarding the threats posed by hypertext links contained in emails or attachments especially from un-trusted sources.