Feeds

Proprietary software puts pacemaker users at risk

Open source group wants mandatory code review

The Power of One eBook: Top reasons to choose HP BladeSystem

More than one-fourth of defective implantable medical devices discovered this year were probably the result of bugs in the software used to control them, a group advocating open source software claimed in a report that argues against the use of proprietary code in the life-saving products.

Although the pacemakers, implantable cardioverter defibrillators and other IMDs, or implantable medical devices, are heavily regulated by the US Food and Drug Administration, the source code for their underlying software is deemed the exclusive property of its manufacturers, the Software Freedom Law Center wrote in the report. As a result, doctors and patients are barred from scrutinizing the code for defects that could result in life-threatening conditions.

"Though the surge in IMD treatment over the past decade has had undeniable health benefits, device failures have also had fatal consequences," the authors wrote. "Research indicates that as IMD usage grows, the frequency of potentially fatal software glitches, accidental device malfunctions, and the possibility of malicious attacks will grow."

In the first half of this year, the FDA recalled 23 devices because there was a "reasonable probability that use of these products will cause serious adverse health consequences or death," according to the report. At least six of those defects likely stemmed from software bugs. One defibrillator recalled by a subsidiary of Medtronic had been the subject of failure reports that spanned its entire eight-year history including one "unconfirmed adverse patient event," the report claimed.

Chris Garland, an executive with the company said the recalled device was an external defibrillator used by paramedics and emergency personnel, and not one implanted in patients, as the report suggests.

From 1997 to 2003, at least 212 deaths resulted from defects in five different brands of defibrillators.

The report comes as researchers over the past few years have warned that implantable devices, particularly newer ones that are remotely controlled using radio signals, are vulnerable to attacks that can cause the devices to malfunction or expose vital signs and other sensitive patient data. Researchers have struggled to devise ways to secure the devices against tampering without preventing doctors from accessing them in the event of an emergency. Protections based on ultrasound waves and password tattoos are two of the proposed solutions.

The non-profit software group has offered a new approach: requiring device manufacturers to make all source code publicly auditable.

"Our intention is to demonstrate that auditable medical device software would mitigate the privacy and security risks in IMDs by reducing the occurrence of source code bugs and the potential for malicious device hacking in the long-term," the report states. "Although there is no way to eliminate software vulnerabilities entirely, this paper demonstrates that free and open source medical device software would improve the safety of patients with IMDs, increase the accountability of device manufacturers, and address some of the legal and regulatory constraints of the current regime."

The report, titled "Killed by Code: Software Transparency in Implantable Medical Devices," is here. ®

This article was updated to make clear that software defects are likely the cause of one-quarter of the recalls. It was also updated to add comment from Medtronic.

Reducing security risks from open source software

More from The Register

next story
NO MORE ALL CAPS and other pleasures of Visual Studio 14
Unpicking a packed preview that breaks down ASP.NET
Captain Kirk sets phaser to SLAUGHTER after trying new Facebook app
William Shatner less-than-impressed by Zuck's celebrity-only app
Apple fanbois SCREAM as update BRICKS their Macbook Airs
Ragegasm spills over as firmware upgrade kills machines
Cheer up, Nokia fans. It can start making mobes again in 18 months
The real winner of the Nokia sale is *drumroll* ... Nokia
Mozilla fixes CRITICAL security holes in Firefox, urges v31 upgrade
Misc memory hazards 'could be exploited' - and guess what, one's a Javascript vuln
Put down that Oracle database patch: It could cost $23,000 per CPU
On-by-default INMEMORY tech a boon for developers ... as long as they can afford it
Google shows off new Chrome OS look
Athena springs full-grown from Chromium project's head
prev story

Whitepapers

Top three mobile application threats
Prevent sensitive data leakage over insecure channels or stolen mobile devices.
Implementing global e-invoicing with guaranteed legal certainty
Explaining the role local tax compliance plays in successful supply chain management and e-business and how leading global brands are addressing this.
Boost IT visibility and business value
How building a great service catalog relieves pressure points and demonstrates the value of IT service management.
Designing a Defense for Mobile Applications
Learn about the various considerations for defending mobile applications - from the application architecture itself to the myriad testing technologies.
Build a business case: developing custom apps
Learn how to maximize the value of custom applications by accelerating and simplifying their development.