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


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
The State of Cybersecurity Incident Response
In this report learn how enterprises are building their incident response teams and processes, how they research potential compromises, how they respond to new breaches, and what tools and processes they use to remediate problems and improve their cyber defenses for the future.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-20399
PUBLISHED: 2021-07-27
IBM Qradar SIEM 7.3.0 to 7.3.3 Patch 8 and 7.4.0 to 7.4.3 GA is vulnerable to an XML External Entity Injection (XXE) attack when processing XML data. A remote attacker could exploit this vulnerability to expose sensitive information or consume memory resources. IBM X-Force ID: 196073.
CVE-2021-20562
PUBLISHED: 2021-07-27
IBM Sterling B2B Integrator Standard Edition 5.2.0.0 through 5.2.6.5_3 and 6.1.0.0 through 6.1.0.2 vulnerable to cross-site scripting. This vulnerability allows users to embed arbitrary JavaScript code in the Web UI thus altering the intended functionality potentially leading to credentials disclos...
CVE-2020-18428
PUBLISHED: 2021-07-26
tinyexr commit 0.9.5 was discovered to contain an array index error in the tinyexr::SaveEXR component, which can lead to a denial of service (DOS).
CVE-2020-18430
PUBLISHED: 2021-07-26
tinyexr 0.9.5 was discovered to contain an array index error in the tinyexr::DecodeEXRImage component, which can lead to a denial of service (DOS).
CVE-2021-37576
PUBLISHED: 2021-07-26
arch/powerpc/kvm/book3s_rtas.c in the Linux kernel through 5.13.5 on the powerpc platform allows KVM guest OS users to cause host OS memory corruption via rtas_args.nargs, aka CID-f62f3c20647e.