Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Comments
Accidental Heartbleed Vulnerabilities Undercut Recovery Effort
Newest First  |  Oldest First  |  Threaded View
SgS125
SgS125,
User Rank: Ninja
5/12/2014 | 4:07:11 PM
Re: Heartbleed is a vulnerability, not an infection
Thanks for the correction,  I am so tired of reading about the "Heartbleed Virus"  the "Heartbleed worm" and the many other inaccuarate descriptions that have flown by my desk.

It's too funny when you get these requests to verify your systems from trading partners that have the request sent out by the marketing department.

I started correcting them but the flood of crap just got bigger too quickly.

 

And thanks to KJH for correcting the Article as well.

 

 
Robert McDougal
Robert McDougal,
User Rank: Ninja
5/12/2014 | 11:37:17 AM
Possible reason for increase in vulnerable machines.
In my experience many system administrators do not pay very close attention to security issues.  The commons sysadmin is more concerned with getting a working server up and online.  In the same way that programmers are generally more concerned with producing usable code over secure coding, sysadmins have a similar mindset when it comes to servers.

Therefore, it is the responsibility of the information security office to constantly remind IT operations of the security vulnerabilities in a particular product.  Also, it is of the upmost importance that prior to allowing a server to be put in production or placed in the DMZ, it must be evaluated for vulnerabilities.

 

 
Bprince
Bprince,
User Rank: Ninja
5/11/2014 | 1:59:36 PM
Heartbleed
Some more bad news about Heartbleed  - A study from Netcraft (http://news.netcraft.com/archives/2014/05/09/keys-left-unchanged-in-many-heartbleed-replacement-certificates.html) found that of all the scanned sites impacted by Heartbleed, only 43 percent had reissued their SSL certificates. On top of that, 7 percent had done so with the same private key.

BP

 
JrmeM921
JrmeM921,
User Rank: Apprentice
5/10/2014 | 4:13:53 PM
A good VPN tetraupload
This is why i'm use a good VPN to protect my IP address :)
If you want take a look to this great speed VPN: http://tetraupload.com 
Kelly Jackson Higgins
Kelly Jackson Higgins,
User Rank: Strategist
5/9/2014 | 3:01:29 PM
Re: Heartbleed is a vulnerability, not an infection
You're correct, @Mrs. Y. It was used as a figure of speech, but is not the right word that should have been used. We will fix that wording. Thank you for pointing this out.
Tyson S
Tyson S,
User Rank: Apprentice
5/9/2014 | 2:50:21 PM
Our company's Heartbleed audit
After patching our Apache web servers, our IT group conducted an audit to see if bad guys had used the Heartbleed exploit against us previously. How did they do that? Well, our company makes a network appliance that parses all SSL transactions going over the wire in our environment, among other things. We could look back to see if there were any heartbeat messages (the attack vector in this case) to our devices since March 2012 when the vulnerability was first introduced. Our dog food tastes great! You can read the details here: http://www.extrahop.com/post/blog/how-extrahops-it-team-performed-a-heartbleed-audit-going-back-years/
Mrs. Y
Mrs. Y,
User Rank: Apprentice
5/9/2014 | 1:48:06 PM
Heartbleed is a vulnerability, not an infection
Heartbleed is a vulnerability arising from the hearbeat functionality of OpenSSL. I'm not sure where you got the idea that this is malware or an "infection." Hearbleed is an exploit technique against vulnerable version of OpenSSL. You're giving out incorrect information and you should correct this in your article.


Edge-DRsplash-10-edge-articles
I Smell a RAT! New Cybersecurity Threats for the Crypto Industry
David Trepp, Partner, IT Assurance with accounting and advisory firm BPM LLP,  7/9/2021
News
Attacks on Kaseya Servers Led to Ransomware in Less Than 2 Hours
Robert Lemos, Contributing Writer,  7/7/2021
Commentary
It's in the Game (but It Shouldn't Be)
Tal Memran, Cybersecurity Expert, CYE,  7/9/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Black Hat USA 2022 Attendee Report
Black Hat attendees are not sleeping well. Between concerns about attacks against cloud services, ransomware, and the growing risks to the global supply chain, these security pros have a lot to be worried about. Read our 2022 report to hear what they're concerned about now.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2022-2734
PUBLISHED: 2022-08-09
Improper Restriction of Rendered UI Layers or Frames in GitHub repository openemr/openemr prior to 7.0.0.1.
CVE-2022-2729
PUBLISHED: 2022-08-09
Cross-site Scripting (XSS) - DOM in GitHub repository openemr/openemr prior to 7.0.0.1.
CVE-2022-2730
PUBLISHED: 2022-08-09
Authorization Bypass Through User-Controlled Key in GitHub repository openemr/openemr prior to 7.0.0.1.
CVE-2022-2731
PUBLISHED: 2022-08-09
Cross-site Scripting (XSS) - Reflected in GitHub repository openemr/openemr prior to 7.0.0.1.
CVE-2022-2732
PUBLISHED: 2022-08-09
Improper Privilege Management in GitHub repository openemr/openemr prior to 7.0.0.1.