Hacking a Pacemaker
jonkman sean writes "University researchers conducted research into how they can gain wireless access to pacemakers, hacking them. They will be presenting their findings at the "Attacks" session of the 2008 IEEE Symposium on Security and Privacy. Their previous work (PDF) noted that over 250,000 implantable cardiac defibrillators are installed in patients each year. This subject was first raised along with similar issues as a credible security risk in Gadi Evron's CCC Camp 2007 lecture "hacking the bionic man"."
I'm sure glad the device in my eye (see my sig for details) is focused by the eye's muscles rather than electronics/motors. Some things shouldn't be networkable.
Oh yeah, the oblig: We are cyborg. You will be assimilated. resistance is not only futile but you won't resist, you'll beg to join us..
mcgrew's razor: Never attribute to stupidity that which can be explained by greedy self-interest
does this mean that someone can eventually kill people remotely?
Hacking a pacemaker? What could possibly go wr... *thud*
This guy's the limit!
What a surprise that you can hack something that has electronics?
If there is a will there is a way.
One: The experiment required more than $30,000 worth of lab equipment and a sustained effort by a team of specialists from the University of Washington and the University of Massachusetts to interpret the data gathered from the implant's signals. And two: "To our knowledge there has not been a single reported incident of such an event in more than 30 years of device telemetry use, which includes millions of implants worldwide," Um, that was until a NYTimes article described that it could be done and (more importantly) a
Similarly the argument that it took $30,000 worth of equipment and a 'team of experts' is retarded because the same might probably have been said about DVD encryption till an adolescent did it in his bedroom with his home computer and enough caffeine.
If I had an AICD, I sure as hell wouldn't want to be around Cheney, lest the signal from mine be confused with his. Of course maybe that is why he has a man sized safe in his office is a Faraday cage.
Even if you could hack it wirelessly the only benefits I see are bragging rights cool they may be just doesn't seem worth the time and effort
Doesn't Dick Cheney have a pace maker?
Life sucks, but death doesn't put out at all. -- Thomas J. Kopp
From http://www.snpp.com/episodes/BABF01
% The Simpsons happen upon Krusty, who is having a Y2K crisis of his
% own. His pacemaker is stuck in the "hummingbird" mode. Krusty
% lifts himself in the air briefly by flapping his arms, before
% collapsing on the ground.
See also:
http://en.wikipedia.org/wiki/Treehouse_of_Horror_X#Life.27s_a_Glitch.2C_Then_You_Die
-theGreater.
A real heart stopper if you will.
Just make a pacemaker for the pacemaker. That way, if it ever shuts down, it'll have a tiny little heart inside it to get it going again.
Would be heartless.
I record my sleeptalking
For a device that serves a life-or-death function for many individuals, some of these headlines about Medtronic Inc. are not the most heart-warming. Especially this recall of defective heart parts.
I'm not that worried about this for 2 reasons: Hackers usually want something that is easily available to hack. These pacemakers are not so common as to be everywhere and easy to access. It would take some work to find and set up a situation where you can hack a pacemaker. The second reason is there are a lot easier ways to kill people than this. If someone goes through this much effort to kill you, they could have done it any number of different ways already. So if you die this way, think of it as living longer than you would have otherwise.
Most pacemakers and defibrillators can be turned off with just a magnet. This is designed to allow medical staff to stop a defective device. Yep I have done it myself and seen it done many times for diagnostic reasons in the hospital. M
"It wasn't me grabbing her ass your honor, someone hacked my arm!"
A-Bomb
RSA encryption is used in these devices. There certainly is a lot of techofear journalism about lately.
The article details how the researchers had to be within 2 inches of the pacemaker, and several thousands of dollars worth of equipment. I suspect there is an easier way to deactivate a pacemaker, find out what frequency they operate at. I've got an FM radio blocker, that is basically just a 100mhz oscillator, a potentiometer, and a battery. It works by canceling out a given frequency, thus letting me silence my neighbors stereo from 50ft away. I know the technique works for the 2.4ghz band, for blocking out wireless phone signals and whatnot. I suppose finding an oscillator in the high ghz range would suffice for 'killing' a pacemaker.
- Aetheral Research -
Why don't they build firewalls into the pacemakers? And perhaps close off ports 21, 80 and 135. Hmmm...
But device makers have begun designing them to connect to the Internet, which allows doctors to monitor patients from remote locations.
"Excuse me, sir? The plane is about to taxi, and I'm going to need you to shut down your wireless internet device."
Some day in my lifetime, a person's heart might have "flight mode." That idea bowls me over. I'm assuming this is some kind of cellular internet connection the devices use. Fifteen seconds of google didn't really turn up much info, but then again I wasn't looking very heard.
I heard Uncle Joe is about to write me out of his will. He has a pacemaker. He's old, there won't be an autopsy. Hmmm......
Knowledge is how to play a game, intelligence is how to win, wisdom is knowing what game to play.
So can I get the pacemaker make a heartbeat sound like the jumping sound effect....
"nah nah nah nahhhhhhhhh"
(Posting this as AC since I don't want to get in trouble).
I think the summary is more alarming than the actual article. The researchers had to be at two inches from the device in order to tamper with it.
It's probably not such a big deal now, but some more thought should definitely go into future products. 30000$ sound like much, but it certainly sounds like a bargain if you can kill the Vice President of the USA without even touching him.
I mean, imagine the following scenario:
1. Bad guys want to kill Cheney. That seems quite plausible.
2. They find out the exact model of his pacemaker. That sounds feasible with some knowledge of the field, money, time and determination.
3. They buy one and hire some researchers to crack it and to create an automated system which is portable and works reliably. Say, a laptop with some transmitter attached or something similar. This is quite hard, but should be feasible as well with enough money and time.
4. The researchers manage to increase the range from 2 inches to 20 inches. This is probably the hardest part.
5. The bad guys put the laptop in a briefcase, wires running up the sleeve and the transmitter in the other sleeve (close to the hand). This is easy.
6. Now they just have to get close enough to Cheney. I have no idea about how hard this is.
7. He has a "heart attack". Bodyguards/security come running and push all the people away. People go away because they don't want trouble, including the guy with the briefcase. I think this is quite realistic.
8. Cheney dies. Maybe they find out that the pacemaker was tampered with, maybe not. If not, the plan worked out perfectly. If yes, they will have some video on a security camera showing the bad guy, who is in another country by now. Maybe they catch him, maybe not.
This sounds pretty far fetched (and it is), but it could be possible with some minor advances. So some more thought should go into these devices.
Pacemakers have batteries which have enough power to supply some encryption hardware. What should be done to prevent this scenario is something like this:
1. Create a key pair for every pacemaker. The public key is on the pacemaker, the private key gets printed on a 2d barcode on a piece of plastic. The patient gets the barcode which he carries in his wallet. The patient's doctor/hospital also gets a barcode.
2. The devices used to communicate with the pacemaker have a slot for the barcode.
3. The pacemaker ignores any request not signed with the private key. Problem solved!
Dick Cheney is preparing to leave office and NOW you tell us?!?!
SJW: Someone who has run out of real oppression, and has to fake it.
Would I need a "team of experts" and $30K of gear if I had worked as an engineer for Medtronic?
Well, sad to say and please don't take it as an offense, it's that kind of attitude that's the cause of half the problems today. Products are made by engineers couldn't care less about security, with their budget dictated by a boss who couldn't care less about security, and end up configured by users who couldn't care less about security. Because they all operate under that assumption that if it's even remotely related to computers or electronics, it can be hacked anyway, so why bother?
Well, no, there are ways to prevent that.
Let's start with the simplest: you can't remote-hack a computer which isn't connected to the net. Pull your network cable out of the computer and that's it, you can't be hacked by some guy in China any more.
Of course, you don't want to do that to your home computer, but we're talking pacemakers and the like. Why _does_ a pacemaker need a WiFi interface anyway? No, seriously. It's not like you want the users to surf for porn and post to Slashdot on their pacemakers. It's not even an appliance, as far as the user is concerned, it's a standalone device like their computer chair or the windshield wipers on their car. You have no freaking need for those to be networked, in any form or shape.
And here's an even more sobering thought: even if you wanted some control from outside, you're near your pacemaker the whole time. In fact, it's inside you. There's no time when you're on the other side of the town than your pacemaker is. So even if you're one of the die-hards that can argue with a straight face why you might need to log in to your fridge from work, the same doesn't apply to pacemakers. You're near it all the time. Any interface to it or from it can be contact-based just as well.
Second, even if you do want it networked, there _are_ ways to minimize bugs drastically. Code _can_ be proven correct, test cases can cover the code to ridiculous extents, and the thing can be riddled with pre- and post-condition checks right in the code and be able to fail safely to its normal offline mode. Yes, it's damn expensive to do that to something the size of Vista. But we're talking a pacemaker. It's just not the same number of lines of code. (Or if it does have millions of lines of code, maybe you just need to fire the guy who programmed it;)
More importantly, we already do _both_ of those for life-and-death systems like flight control systems on airplanes or brake computers on cars. They're both built and reviewed to be as good as bulletproof, _and_ not wired to talk to the outside world, unless one physically plugs in a special connector and a special computer into it. You don't want a car's brakes to be hijacked by wireless by the guy in the next car, so you just don't give them a wireless connection. Do you see any reason why we wouldn't apply the same thinking to a pacemaker? It's even more likely to kill than hijacking someone's brakes. There is no airbag to save you when your pacemaker fails.
So what I'm saying is: let's all stop and think twice before shrugging and dismissing security as impossible anyway. Sometimes it's very feasible to make it bulletproof, and, really, it has no excuse to not be so.
A polar bear is a cartesian bear after a coordinate transform.
TO: osama.bin.laden@cave.net
Doesn't Dick Cheney have a pace maker?
your sincerely, a helpful Brit.
IranAir Flight 655 never forget!
I'm gonna overclock this sucker!
Better than a triple espresso!
----------------------------------- My Other Sig Is Hilarious -----------------------------------
Punchline: Heartworm.
Imagine hooking up your pacemaker to your favorite FPS via bluetooth or something. Every time you get hit your heart misses a beat. Literally.
... :-) Hehehe ...
I can also just imagine installing Vista remotely onto the pacemakers of all those Windows fanboys.
We suffer more in our imagination than in reality. - Seneca
I don't see it as a big threat. In fact, I have a pacemaker implanted and HNNNNNNGGGGG.....
to the term 'reboot', doesn't it? *Laugh*
Working on the communications software for one of these devices, I can say for sure there is no encryption on at least one of them. A decision was made by the company to not worry about this issue at the moment.
Some health care insurance / hospitals may want to cut you off if you can't pay or they found out that you had a pre existing condition they make you pay up and say pay or we cut you off.
Some of them have said that a kidney transplant is to experimental and they let a someone die just to get out of paying for it.
There was a movie about someone putting bombs in Pacemakers
http://en.wikipedia.org/wiki/Dead_in_a_Heartbeat
Some testing was conducted to see if the various transmitters on a Toyota Camry could interfere with operation of a defibrillator. Interference was detected that caused the defibrillator to miss sensing important heart events, and also to fire when there was no event. The study recommended staying a few meters away from certain areas of the car. Similar article on hybrid intereference: http://trusted.md/feed/items/system/2008/02/25/pacemakers_defibrillators_and_hybrid_cars
There are many posts about high profile evil types with pacemakers and what-ifs to reprogram said pacemakers. They all seem a little silly to me since, as I recall, microwave ovens produce a signal that can kill the pacemaker user. Conceivably, it would not be very difficult to create a waveguide antenna to shape the output from a high-power microwave horn from a commercial microwave oven into an aim-able beam. With a few of these running at the same time a DOS attack would be very feasible. Disclaimer: IANAP (physicist), and have only dabbled in wifi antennas (about the same frequency of microwave ovens), nor do I recommend employing these tactics against anyone, no matter how despicable they are. Especially when a firing squad works just as well, its just not as geeky.
How amazed would you be to suddenly find that you just forgot what I wrote and you needed to reread my post.... again.
I don't remember the author's name. Anyway, this book (should be 10 years old at least) has a pseudo sci-fi/apocalyptic plot in which the bad guy, who owns the most powerful software company on earth, uses its latest operating system to take control of all the desktops and collect information on all the people. I won't disclose the ending (but it's groovily psychedelic and dripping with LSD/religious fanaticism). However, I will point out the scenario where bad guy uses a PDA with his devilish OS to hack the pacemaker of one of his rivals and kills him through a fake heart-attack.
All new pacemakers are to be fitted with government escrow keys to the control interface. After all, if you have nothing to hide then you have nothing to worry about, have you......
Every six months my pacemaker is checked. Part of the test is to speed and slow down the pacemaker and my heart for a short time.
It is a truly heartfelt experience.
Bookwormhole.net -- a site for book lovers.
Yes, that's a very real concern that the secret service has been terrified of for years. Most people know that Cheney has a pacemaker, but the real secret is that they forgot to turn off SSID broadcast and its password is "Linksys".
Nice pacemaker you have there - shame if anything should happen to it.
try { do() || do_not(); } catch (JediException err) { yoda(err); }
I mean, sure, if your heart was hooked to the internet and easily hackable, I would be worried. But, right now, if I want to kill someone it would still be done with a good old fashioned bullet. Much cheaper (maybe a dollar?) and a hell of a lot faster.
Brings a different meaning to the words "Heart Attack"
Death Note, anyone?
(Sorry about the Anime reference, but wow.)
The Faraday vest - what a concept! EMI shielding is the new kevlar.
Hmm, old story but interesting.
Ant(Dude) @ Quality Foraged Links (AQFL.net) & The Ant Farm (antfarm.ma.cx / antfarm.home.dhs.org).
The ban on wireless/electronic devices in flight is actually to prevent "air rage." Picture being on a flight with a teenage girl babbling at the top of her lungs on the cell phone 6 inches from your head the whole way. That was an extreme example, but people are ticked off by other things such as a bunch of hyped up little boys in a heated 4-player Mario Kart game - that's why handheld gaming devices were expressly forbidden from use in flight about a decade ago.
Look at the list today - cell phones and handheld gaming devices, which all conveniently use wireless communication nowadays, so only multiplayer games are bad juju.
"When information is power, privacy is freedom" - Jah-Wren Ryel
.. I see this more like, "Cheney hacks pacemaker to extract confessions from suspect cardiac patients".
Still, I'd like to see proof of concept. There is no such thing as "guaranteed short range" in wireless. My Bluetooth headset has a 50-foot range in the right locations.
Give a man a fish and you have fed him for today. Teach a man to fish, and he'll say "WHERE'S MY FISH, YOU IDIOT?"
http://www.formatnovel.com/formatc/html/reviews.php
4th Google result of "format C: book"
"When information is power, privacy is freedom" - Jah-Wren Ryel
So basically you're telling me that you have to have an external thing strapped to your chest, full time, for it deal with that? I thought they were programmed by a cardiologist once, and left on their own afterwards.
_If_ any model needs it to be done that often, there _are_ ways to have things sticking out of someone's skin (think: dental implants) or have an electrode go out to right under the skin (think: some hearing implants.) So, you know, they require contact or near contact to work at all.
That still doesn't excuse its being an insecure protocol. If the only thing it has going for its security is that it's a custom proprietary protocol, then at best it's "security by obscurity." I.e., an antipattern by any other name.
Again, there are ways to place electrodes for that, so they don't involve shooting a couple of amps through the chest.
So, basically, to wrap this up: I don't know what your qualifications are, but security is obviously not one of them. You can tell that when someone starts stringing straw men, non-sequiturs and a few other fallacies as why they didn't and shouldn't think about security. Whether it's about pacemakers or "why XSS vulnerabilities are overhyped and inevitable, and you shouldn't ask me to learn to encode strings" types, it's the same basic phenomenon.
At the end of the day, I still don't see why those things shouldn't be more secure. And I still don't see how your arguments have anything to do with security. No, it doesn't have to be fixed rate to be secure. No, you don't need to shoot a few amps through someone's chest. Etc. You just need to spend some time designing and reviewing it for security too, which is where most people fail. In all domains, so I'm not just picking on pacemakers. Pretty much invariably the failure isn't that security is impossible, it's that it didn't occur to anyone to even think (much) about it.
I mean, seriously, it didn't take me more than 5 minutes to think up solutions to those issues you raise, and I'm not even claiming to be the smartest guy around. I'm sure you or the companies manufacturing them too can come up with even better ones. But for that to happen, you have to snap out of the reflex of defending insecure designs as inevitable and impossible to change. You just need to devote some honest thinking and research to security too. That's all.
Or even shorter, as I was saying: it's that fatalism that's the problem. Too many people are too quick to throw both hands up and accept that everything is hackable anyway, rather than even try to do better.
A polar bear is a cartesian bear after a coordinate transform.
...a blue-hair receives a text message from her grandkids...
H4 H4 H1 GR4NNY W3 H4XX0RS U! W3 RuL3!
(Meanwhile, Granny clutches at her chest as her pace maker pulses out the drum solo from "In A Gadda Da Vida")
"If god did not exist, it would be necessary to invent him" --Voltaire
I agree with those that said that in order to "hack" the pacemaker you have to be at a very close range to the victim. At this range, you could just as easily stab or shoot them. As a more general rule, apart from a select few VIP figures, there is nothing we can do to prevent someone from carrying out a murder if they want to, the only thing we can do is punish them after the fact and hope it serves as deterrent for others.
What IS a problem is that unlike other means to kill a person at close range, this method is rather subvert, and unless you are an expert at recognizing behavior and/or expect the victim to be targeted, you will probably not even notice the attack took place. Picture this: a man walks by another man, with a wireless device in his pocket and already pre-configured to carry out the attack. They each go their own ways, and seconds later the other man has a heart attack. The pacemaker is likely not to keep any logs that can reveal the nature of the "hack". So unless you find the equipment used for "hacking" and can tie it to the attacker, you have very little evidence to charge them with.
At this point the technique is so unknown that it is unlikely to be used as an attack option by anyone other than professional assassins. But this can change. If someone writes software that can work on a device like a PDA or cellphone, we may well have "script kiddies" who know nothing about hacking but just download and use the software for any reason they have.
We have a much milder precedent of this kind of abuse - some new traffic lights have wireless detectors to detect a special signal used by emergency vehicles and turn the lights green. Some people abuse this technology to just get a green light whereever they drive. Few get caught, and those who do get really laughable sentences, like a small fine with no jail time, perhaps a license suspension, but that's about it.
So in the long run, yes, I think we should have some kind of encryption or other security on the pacemakers. Of course, this has to be balanced with cost and speed issues for doctors to be able to treat patients.
As for punishment for this kind of offense, a "hacking" charge is just the icing on the cake. Tampering with life support equipment, whether via hacking or not, can result in charges from aggravated assault to attempted murder/manslaughter. I wouldn't envy someone who gets caught doing this, whatever their intentions are, as chances are they'll spend a lot of years behind bars for this.
But will it play Doom?
The main reason that things like encryption aren't needed is that it's industry standard practice to have pacemakers not respond to communications of any kind unless their communication mode is enabled by placing a big magnet on or near the patient's chest. This is why pacemaker owners are warned against magnets.
Unless you have some means to apply a magnet to the pacemaker, you can't really communicate with it, and if you're in a position to apply a magnet to within a few inches of the pacemaker and you intend the patient harm, why not just use a knife instead of bothering with reprogramming the pacemaker?
Thus, encrypting the communication wouldn't really be very useful except in very obscure scenarios (e.g. a doctor is reprogramming the pacemaker and has placed the magnet, and you send a vastly higher-power signal from a remote location, and somehow manage to avoid the checksumming that occurs, as well as the doctor's equipment re-interrogating the pacemaker to make sure that the program made it down OK.)
You know, they used to require a large-ish magnet to initiate communication with these things; the magnet would flip a little reed switch inside the device, and only then would the device be able to communicate. This has changed (or is in the process of changing) for all of the major mfg's of ICD's (and their little brothers: pacemakers) recently ...
BTW, for those who think that these things shouldn't communicate at all: Um, right ... there are hundreds of settable parameters in these things, and in addition, they're built-in holter monitors (iegm recorders) from which the dr can d/l important diagnostic info. Tweaking settings based on this info can make HUGE quality-of-life differences for the patients involved (see "t-wave oversensing" ... yike!)
Disclaimer: I work for a place that makes PM's and ICD's.
and hacking someone to death without spilling a drop of blood (assuming the pacemaker is not set to over-pressurise and inflate the target...).
Hmmm, that gives rise to "talk about being "pounded" to death"....
Can beat (ring) tones be generated so as to deliver a message to the soon-to-be-deceased?
(hehehe: captcha: salvager)
Previously: "Linux... Toward the Sunrise..." Now: "Linux... Toward the-- No, now, part of Every Sunrise"
My girlfriend is a type 1 diabetic. Instead of regular injections, she uses an insulin pump. This pump is an external device, about the size of a pager, that feeds insulin into her body via a short tube.
Several months ago she upgraded to a new pump. This new model (a Medtronic MiniMed) wirelessly communicates with a number of devices. It receives blood glucose data from a continuous glucose monitor. It also receives her regular readings from her standard "prick your finger" blood sugar tests via her test kit. And, it has a wireless key fob that allows her to adjust the pumps settings without having to dig through pockets and clothes to get at the unit.
My first comment to her was "With all of this wireless control, how easy is it for someone to use this wireless interface to put you into a diabetic coma, or worse, kill you?" She thinks it's a fairly ridiculous concept, citing encryption, receiver range, and "Why would anyone want to kill me?", among other reasons.
Well, I say that anything that has any type of wireless interface is hackable. There are, of course, no published documents that I can find detailing what steps have been taken to secure these devices. I'm seriously concerned as to whether or not the companies that make insulin pumps, pace makers, implants, etc, may not be taking these concerns seriously.
Imagine a cylon network of those...
Excuse me, but please get off my Pennisetum Clandestinum, eh!
drive-by MRI's?
Ping of death anyone?
I read this subject in the original sense of hacking - like someone would get in under the covers and hot-rod it to increase his aerobic performance.
Advice: on VPS providers
If you stole the programming equipment from Medronic, then no, you wouldn't need 30K of gear.
Part of the cost would be attributable to the fact that these items operate in the MICS band (402-405 MHz), which is a specific band isolated for medical implantable use. To generate and listen to signals at this frequency, you would typically need some type of engineering test equipment or a custom built circuit. This is regardless of any encryption or whatnot. It's more of a security through obscurity model.
Secondly, assuming you had access to the protocol details and a familiarity with wireless set-ups, you need to really want to hurt someone. Most engineers working for medical device companies don't seek that kind of thrill. For those that do, there are plenty of other ways to cause damage that is so much easier.
On the other hand I know of a few that do - bizzarely the old Z80 chip still lives on in these things and does have the grunt for RSA encyrption within workable time frames.