Vulnerabilities / Threats
1/3/2014
04:20 PM
Connect Directly
Twitter
RSS
E-Mail

OpenSSL Says Breach Did Not Involve Corrupted Hypervisor

Hosting provider's compromised password system, not a hacked hypervisor, led to defacing of OpenSSL.org site, site reps say – after VMware cries foul.

Comment  | 
Print  | 
Comments
Newest First  |  Oldest First  |  Threaded View
Stratustician
50%
50%
Stratustician,
User Rank: Moderator
1/7/2014 | 2:37:33 PM
Locking down the hypervisor
I sadly think we are going to see lots of these types of incidents as ports are left open in virtual environments, as well as faulty SSL policies.  The real threat to the hypervisor will probably come from an unsecured VM being accessed and somehow the hypervisor is accessed, or through the management console.  In a private environment it's a scary thought, but in a public environment where multiple companies share the same hypervisor, it's the stuff that would keep security folks up at night.
asksqn
50%
50%
asksqn,
User Rank: Apprentice
1/4/2014 | 6:24:06 PM
The Turkish hack was a just a dry run-
Next time, however, it is doubtful the next crop of hackers will be so warm/fuzzy.  Regardless, this is a breach that should underscore security is dynamic.  It is simply no longer enough to rest on the laurels of hard to hack 'nux distros and proclaim impregnability.
cbabcock
50%
50%
cbabcock,
User Rank: Apprentice
1/3/2014 | 7:13:51 PM
First it was, then it wasn't
I like the speedy resolution of this issue. There's bound to be some questions at a site as sensitive as OpenSSL when an incident occurs, and the site administrators were on the right track when they pointed toward the hosting service server, VMware had the courage of its convictions to say no, it was not the hypervisor, when OpenSSL first pointed in that direction, and indeed, it was password management on the hosting site. Multiple parties looking at the problem came up with the right answers quickly and pretty transparently. Salud.
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Dark Reading Must Reads - September 25, 2014
Dark Reading's new Must Reads is a compendium of our best recent coverage of identity and access management. Learn about access control in the age of HTML5, how to improve authentication, why Active Directory is dead, and more.
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2012-5485
Published: 2014-09-30
registerConfiglet.py in Plone before 4.2.3 and 4.3 before beta 1 allows remote attackers to execute Python code via unspecified vectors, related to the admin interface.

CVE-2012-5486
Published: 2014-09-30
ZPublisher.HTTPRequest._scrubHeader in Zope 2 before 2.13.19, as used in Plone before 4.3 beta 1, allows remote attackers to inject arbitrary HTTP headers via a linefeed (LF) character.

CVE-2012-5487
Published: 2014-09-30
The sandbox whitelisting function (allowmodule.py) in Plone before 4.2.3 and 4.3 before beta 1 allows remote authenticated users with certain privileges to bypass the Python sandbox restriction and execute arbitrary Python code via vectors related to importing.

CVE-2012-5488
Published: 2014-09-30
python_scripts.py in Plone before 4.2.3 and 4.3 before beta 1 allows remote attackers to execute Python code via a crafted URL, related to createObject.

CVE-2012-5489
Published: 2014-09-30
The App.Undo.UndoSupport.get_request_var_or_attr function in Zope before 2.12.21 and 3.13.x before 2.13.11, as used in Plone before 4.2.3 and 4.3 before beta 1, allows remote authenticated users to gain access to restricted attributes via unspecified vectors.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
In our next Dark Reading Radio broadcast, we’ll take a close look at some of the latest research and practices in application security.