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
Emergency SSL/TLS Patching Under Way
Newest First  |  Oldest First  |  Threaded View
<<   <   Page 2 / 2
Marilyn Cohodas
50%
50%
Marilyn Cohodas,
User Rank: Strategist
4/9/2014 | 8:38:28 AM
Change passwords and user names?
Many news reports are quoting secruity gurus who recommendi that anyone using the Web immediately change their user names and passwords, particularly on ecommerce and financial sites. Is that overkill or an appropriate response? 
Ed Moyle
50%
50%
Ed Moyle,
User Rank: Apprentice
4/9/2014 | 8:24:29 AM
Tip of the iceberg IMHO
Heartbleed is, without question, an "earthshattering" bug.  However, it strikes me that there's still another shoe to drop.  What I mean by that is that OpenSSL is open source, right?  Tons of other developers use it: they link against it, copy/paste it, set up web services to incorporate it, etc.  

Remember the ASN1 parsing vulnerability from a few years back (http://www.securityfocus.com/bid/8732)?  Take a look at the list of products impacted and you'll see what I mean (the list goes on for page after page).  Why were so many products impacted?  Becuase that source was reused - and reused - and reused again.  We were literally dealing with that bug for a decade after the fact because that code was used in everything from embedded devices to medical equipment to ICS systems. 

So what really concerns me is less the population of web servers that this impacts - because, impactful as that is, they can at least upgrade fairly easily.  What really makes me nervous is what else is vulnerable that can't be upgraded quite so easily.  This code is in a lot of stuff, in particular embedded systems.  Mark my words -- we'll be deling with this one for a while.  
sidd_452
50%
50%
sidd_452,
User Rank: Apprentice
4/9/2014 | 4:46:24 AM
OpenSSL TLS DTLS Heartbeat Extension
How important are the Antivirus Vendors in releasing the singatures for this vulnerablility as they use the webservers like apache?
Li Tan
50%
50%
Li Tan,
User Rank: Apprentice
4/8/2014 | 10:20:47 PM
Re: On the backend
I fully agree - now we are in the era of risk and uncertainty. Somehow as the normal people, we have to ignore something on purpose. If I think over about how many people/agencies have found my personal data during various exploration, I feel really deterred and cannot sleep well.:-(
securityaffairs
50%
50%
securityaffairs,
User Rank: Ninja
4/8/2014 | 4:49:34 PM
Re: On the backend
Official voices referes to an implementation mistake ... but Snowden's revelations have sown the seeds of distrust. This is just the beginning.  The only certainty is that the flaw is very disconcerting ... and probably many Intelligence agencies have exploited it in the past.

 
Kelly Jackson Higgins
50%
50%
Kelly Jackson Higgins,
User Rank: Strategist
4/8/2014 | 2:59:41 PM
Re: On the backend
That's a great question, @Ryan Sepe. I know it was an implementation flaw in OpenSSL. It would be interesting to know what exactly introduced the problem in that version 2 years ago.
RyanSepe
50%
50%
RyanSepe,
User Rank: Ninja
4/8/2014 | 2:56:14 PM
On the backend
This is very scary that this exploit has come to light. Especially since it is very difficult and will be extensive to make sure that this exploit is remediated based on some of the safeguards mentioned in the article. If you can spoof the server and step in as if you were that server from a malicious standpoint there is no end to the data that will be compromised. Also, does anyone know how this vulnerability came to be? Meaning I am sure there are many ways that a site can be checked for activity, what is it about the previous creation of the heartbeat extension that provided this hole?
<<   <   Page 2 / 2


Manchester United Suffers Cyberattack
Dark Reading Staff 11/23/2020
As 'Anywhere Work' Evolves, Security Will Be Key Challenge
Robert Lemos, Contributing Writer,  11/23/2020
Cloud Security Startup Lightspin Emerges From Stealth
Kelly Sheridan, Staff Editor, Dark Reading,  11/24/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-4626
PUBLISHED: 2020-11-30
IBM Cloud Pak for Security 1.3.0.1 (CP4S) could reveal sensitive information about the internal network to an authenticated user using a specially crafted HTTP request. IBM X-Force ID: 185362.
CVE-2020-4627
PUBLISHED: 2020-11-30
IBM Cloud Pak for Security 1.3.0.1(CP4S) potentially vulnerable to CVS Injection. A remote attacker could execute arbitrary commands on the system, caused by improper validation of csv file contents. IBM X-Force ID: 185367.
CVE-2020-4696
PUBLISHED: 2020-11-30
IBM Cloud Pak for Security 1.3.0.1(CP4S) does not invalidate session after logout which could allow an authenticated user to obtain sensitive information from the previous session. IBM X-Force ID: 186789.
CVE-2020-4900
PUBLISHED: 2020-11-30
IBM Business Automation Workflow 19.0.0.3 stores potentially sensitive information in log files that could be read by a local user. IBM X-Force ID: 190991.
CVE-2020-4624
PUBLISHED: 2020-11-30
IBM Cloud Pak for Security 1.3.0.1 (CP4S) uses weaker than expected cryptographic algorithms during negotiation could allow an attacker to decrypt sensitive information.