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.

11:00 AM

St. Jude Says Muddy Waters, MedSec Video Shows Security Feature, Not Flaw

Feud between St. Jude Medical and Muddy Waters and MedSec continues with the former reiterating safety feature of its implantable devices.

St. Jude Medical has refuted the recent flawed-device allegation made by Muddy Waters Capital and MedSec and has issued a statement saying the “flaw” was actually a “security feature.” Muddy Waters and cybersecurity firm MedSec had released a video on August 29 to demonstrate that some of St. Jude’s implantable devices were soft targets of cyberattacks.

“We want our patients to know that they can feel secure about the cybersecurity protections in place on our devices,” said Michael T. Rousseau of St. Jude Medical adding that the “crash” implied by the Muddy Waters video was in reality a display of the Radio Frequency (RF) Telemetry Lockout security feature of the company’s pacemakers.

“If attacked, our pacemakers place themselves into a 'safe' mode to ensure the device continues to work,” further elaborated Phil Ebeling of St. Jude Medical.

St. Jude claims its implantable devices include features that bring down dangers of unauthorized commands issued to them and thwart crash attacks.

For full press statement, click here.

Dark Reading's Quick Hits delivers a brief synopsis and summary of the significance of breaking news events. For more information from the original source of the news item, please follow the link provided in this article. View Full Bio

Recommended Reading:

Comment  | 
Print  | 
More Insights
Threaded  |  Newest First  |  Oldest First
User Rank: Ninja
8/31/2016 | 2:44:03 PM
Collaboration is key to uncover and remedy vulnerabilities
When it comes to security of medical devices, this type of article makes me nervous.  I would like to see all parties collaborate to test and strenghten the security of implantable medical devices rather than having a war of words over media.
User Rank: Ninja
8/31/2016 | 11:07:27 PM
Re: Collaboration is key to uncover and remedy vulnerabilities
I agree, but I would say a caveat to that is that the collaboration should be closed source. Open source collaboration was a good idea in theory but it seems to do more harm than good.
User Rank: Ninja
8/31/2016 | 11:09:45 PM
If attacked, our pacemakers place themselves into a 'safe' mode to ensure the device continues to work,
Referring to the title of my post, I think this needs to be more clearly defined. What constitutes an attack? Do authroized users have the ability to make changes as needed after the implants have been implanted, and if so can this behavior be mimicked, etc?
Joe Stanganelli
Joe Stanganelli,
User Rank: Ninja
9/3/2016 | 5:11:09 PM
Isn't "It's not a bug; it's a feature!" the oldest software-engineering excuse in the book?
How SolarWinds Busted Up Our Assumptions About Code Signing
Dr. Jethro Beekman, Technical Director,  3/3/2021
'ObliqueRAT' Now Hides Behind Images on Compromised Websites
Jai Vijayan, Contributing Writer,  3/2/2021
Attackers Turn Struggling Software Projects Into Trojan Horses
Robert Lemos, Contributing Writer,  2/26/2021
Register for Dark Reading Newsletters
White Papers
Cartoon Contest
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
How Enterprises are Developing Secure Applications
How Enterprises are Developing Secure Applications
Recent breaches of third-party apps are driving many organizations to think harder about the security of their off-the-shelf software as they continue to move left in secure software development practices.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
PUBLISHED: 2021-03-08
Oryx Embedded CycloneTCP 1.7.6 to 2.0.0, fixed in 2.0.2, is affected by incorrect input validation, which may cause a denial of service (DoS). To exploit the vulnerability, an attacker needs to have TCP connectivity to the target system. Receiving a maliciously crafted TCP packet from an unauthentic...
PUBLISHED: 2021-03-08
The package github.com/pires/go-proxyproto before 0.5.0 are vulnerable to Denial of Service (DoS) via the parseVersion1() function. The reader in this package is a default bufio.Reader wrapping a net.Conn. It will read from the connection until it finds a newline. Since no limits are implemented in ...
PUBLISHED: 2021-03-07
An issue was discovered in MantisBT before 2.24.5. It associates a unique cookie string with each user. This string is not reset upon logout (i.e., the user session is still considered valid and active), allowing an attacker who somehow gained access to a user's cookie to login as them.
PUBLISHED: 2021-03-07
This affects all versions of package github.com/nats-io/nats-server/server. Untrusted accounts are able to crash the server using configs that represent a service export/import cycles. Disclaimer from the maintainers: Running a NATS service which is exposed to untrusted users presents a heightened r...
PUBLISHED: 2021-03-07
An issue was discovered in the Linux kernel through 5.11.3. drivers/scsi/scsi_transport_iscsi.c is adversely affected by the ability of an unprivileged user to craft Netlink messages.