{"id":3774,"date":"2014-08-20T23:53:35","date_gmt":"2014-08-20T15:53:35","guid":{"rendered":"https:\/\/www.darknet.org.uk\/?p=3774"},"modified":"2015-09-09T19:36:46","modified_gmt":"2015-09-09T11:36:46","slug":"heartbleed-implicated-us-hospital-leak","status":"publish","type":"post","link":"https:\/\/www.darknet.org.uk\/2014\/08\/heartbleed-implicated-us-hospital-leak\/","title":{"rendered":"Heartbleed Implicated In US Hospital Leak"},"content":{"rendered":"

If you’ve been up on your news consumption in the past week or so, you’ll have read about the Chinese hackers who managed to access 4.5 million patient records in a huge US Hospital Leak.<\/p>\n

Community Health Systems hacked, records of nearly 4.5 million patients stolen<\/a><\/p>\n

\"US<\/p>\n

Now it turns out, the first entry for this attack was via the Heartbleed<\/a> bug – which should have been fixed months ago.<\/p>\n

The Heartbleed flaw is responsible for the high-impact US hospital hacking attack disclosed this week, an unnamed investigator told Bloomberg.<\/p>\n

As many as 4.5 million patient records have been exposed in an attack against Community Health Systems, a US hospital group that manages more than 200 hospitals.<\/p>\n

China-based attackers stole millions of records which included data such as patient names, Social Security numbers, addresses, birth dates, and phone numbers after breaking into systems. No medical records nor any financial data was exposed by the nonetheless damaging breach, which CHS admitted had taken place between April and June as part of a regulatory filing.<\/p>\n

A person “involved in the investigation who wasn\u2019t authorised to comment publicly” blamed the Heartbleed OpenSSL bug for giving hackers a way into healthcare networks, an assessment backed up by a statement by a US security consultancy with a track record in accessing the IT security of government healthcare projects.<\/p>\n

“The initial attack vector was through the infamous OpenSSL ‘Heartbleed’ vulnerability which led to the compromise of the information,” according to security consultancy TrustedSec, which was the first to comment on the reported cause of the breach.<\/p><\/blockquote>\n