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
Heartbleed: Examining The Impact
Newest First  |  Oldest First  |  Threaded View
macker490
50%
50%
macker490,
User Rank: Ninja
4/13/2014 | 9:12:33 AM
Secure Computing in a Compromised World
the impact is less than you might think:   we all live in a heavilly compromised world due to years of poor practice.

 

i posted some notes on this here:

 

https://www.schneier.com/blog/archives/2014/04/friday_squid_bl_419.html#c5430516
tsapio
50%
50%
tsapio,
User Rank: Author
4/12/2014 | 8:35:59 AM
Re: Assessing damage
For maximum security assurance, you should patch all your servers, change all passwords, revoke and reissue all certificates, and consider the impact of everything served by vulnerable systems being compromised. Each company will have to make their own decisions in this regard. As I stated above, there is no way of telling what (if anything) has actually been compromised. It is one of the worst features of this attack, and there is no way to find out retroactively. If it passed through a vulnerable web server, it is potentially compromised.
tsapio
50%
50%
tsapio,
User Rank: Author
4/12/2014 | 8:32:38 AM
Re: Assessing damage
It is theoretically possible to determine by examining server logs that a possible attack has occurred. However, what has been compromised is still going to be almost impossible to determine since what is being compromised is contents of memory adjacent to the buffer that holds the normal heartbeat response. This information is not going to be logged under normal circumstances. It would be extremely memory intensive to do so, and very time consuming to analyze. My recommendation is to close off this hole because it is the easiest and safest course of action.
Thomas Claburn
100%
0%
Thomas Claburn,
User Rank: Ninja
4/10/2014 | 6:59:53 PM
Re: Assessing damage
Is there any consensus on the need to change passwords? I keep reading differing opinions.
Marilyn Cohodas
100%
0%
Marilyn Cohodas,
User Rank: Strategist
4/10/2014 | 4:27:47 PM
Assessing damage
Thanks for a fascinating article Tim.  Now that the bug has been identified, going forward I assume it will be easier to tell when a breach has occurred. Or not? 

 


News
Inside the Ransomware Campaigns Targeting Exchange Servers
Kelly Sheridan, Staff Editor, Dark Reading,  4/2/2021
Commentary
Beyond MITRE ATT&CK: The Case for a New Cyber Kill Chain
Rik Turner, Principal Analyst, Infrastructure Solutions, Omdia,  3/30/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
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-2021-28797
PUBLISHED: 2021-04-14
A stack-based buffer overflow vulnerability has been reported to affect QNAP NAS devices running Surveillance Station. If exploited, this vulnerability allows attackers to execute arbitrary code. QNAP have already fixed this vulnerability in the following versions: Surveillance Station 5.1.5.4.3 (an...
CVE-2020-36323
PUBLISHED: 2021-04-14
In the standard library in Rust before 1.50.3, there is an optimization for joining strings that can cause uninitialized bytes to be exposed (or the program to crash) if the borrowed string changes after its length is checked.
CVE-2021-31162
PUBLISHED: 2021-04-14
In the standard library in Rust before 1.53.0, a double free can occur in the Vec::from_iter function if freeing the element panics.
CVE-2017-20004
PUBLISHED: 2021-04-14
In the standard library in Rust before 1.19.0, there is a synchronization problem in the MutexGuard object. MutexGuards can be used across threads with any types, allowing for memory safety issues through race conditions.
CVE-2018-25008
PUBLISHED: 2021-04-14
In the standard library in Rust before 1.29.0, there is weak synchronization in the Arc::get_mut method. This synchronization issue can be lead to memory safety issues through race conditions.