any malicious modifications to the transmitted mes-
sages. Usually the goal of eavesdropping is to acquire
the victim’s important health information.
The Advanced Encryption Standard (AES) (Dae-
men and Rijmen, 2013) is a well-known solution that
prevents the attackers from understanding the mes-
sage transmitted even if they record it. However, if the
encrypted cipher can be listened, and the attackers are
able to predict or make a proper guess of the victim’s
health data (precondition 3.), with both the cipher and
plaintext it is possible to apply known-plaintext at-
tacks. This can lead to severe information leakage
such as the secret keys (Bogdanov and Isobe, 2014).
This will be disastrous since the attacker then will be
capable to decrypt and understand any ciphers of the
health data. Moreover, the attacker will have the suf-
ficient knowledge to forge the measurement of health
data to spoof the sensor.
3.2.2 Hijack and Replay
As (Rushanan et al., 2014) have pointed out, some
IMDs have no authentication of the incoming radio
signals. Thus the attackers and establish anonymous
transmissions to either the implanted device or the
monitor/controller.
This gives attackers opportunities to take over the
transmissions between legal sensors and controllers.
The attacker can firstly eavesdrop and record the le-
gal transmitted ciphers without any understanding of
the health data. Then he/she can replay some of the
stored legal ciphers to IMD. Even if every transmitted
message is encrypted and authenticated, the replayed
ciphers will still be considered as legal. Moreover,
if the attacker is able to apply known-plaintext attack
and acquires the information of the secret key, he/she
can choose to inject certain ciphers to harmfully affect
the IMD. For example, very high glucose measure-
ments can be frequently sent to the patient’s monitor,
inducing overdose of insulin pumps. Or commands
of persistent large electric shocks can be sent to the
defibrillator or pacemaker, causing deadly aftermath.
Depending on which AES mode a IMD is quipped
with, the replay attacks will have different effects.
If it is AES in ECB mode, then there is a one-
on-one pairing between the plaintext (health data) and
cipher as shown in the figure below. This makes it ex-
tremely easy for attackers to choose ciphers to inject
into the hijacked channel according to their malicious
purposes.
If it is AES in CBC mode, which is considered
as much more secure than the ECB mode, the cur-
rent plaintext will be randomized by the previous ci-
pher and then sent for encryption. Thus the decrypted
texts are beyond the control of the attackers. How-
Figure 4: In ECB mode the cipher is a function of the secret
key and the plaintext, whose mapping is unique and predi-
catble.
ever, since the health data are usually generated from
microprocessors and sensors of 8 bits, 12 bits, or 16
bits (Chede and Kula, 2008) (McDonald et al., 2011),
it makes the replayed cipher from attackers decrypted
to another legal numeric value with a high probability.
Figure 5: In CBC mode the cipher is effectively randomized
by a function of the secret key, the current plaintext, and the
previous cipher.
Example 3.1: In a 128-bit AES-CBC protected in-
sulin pump IMD system with a 128-bit IV (in hex-
adecimal):
IV = {0x00, 0x01, 0x02, 0x03, 0x04, 0x05, 0x06,
0x07, 0x08, 0x09, 0x0a, 0x0b, 0x0c, 0x0d, 0x0e, 0x0 f }
And a 128-bit secret key (in hexadecimal):
key = {0x60, 0x3d, 0xeb, 0x10, 0x15, 0x ca, 0x71,
0xbe, 0x2b, 0x73, 0xae, 0x f 0, 0x85, 0x7d, 0x77, 0x81}
This insulin pump generates 16-bit measurement
data of glucose in the blood. From a previous eaves-
dropping, the attacker has acquired the legal cipher of
a sensor’s measurement of glucose at moment t
0
as:
cipher(t
0
) =
{0x17, 0x71, 0x98, 0x42, 0xac, 0x9c, 0x9e, 0xe8,
0x87, 0xc6, 0xed, 0x71, 0xd1, 0x1a, 0x78, 0x24}
After a meal at the moment t
1
the patient’s IMD
microprocessor transmits the cipher text for ‘200
mg/dL” high level glucose in the blood to his mon-
itor:
cipher(t
1
) =
{0x0e, 0x11, 0x43, 0x4e, 0x23, 0xb1, 0x32, 0x f 2,
0x4c, 0x12, 0x0a, 0x6d, 0x2c, 0x03, 0x87, 0x1e}
ICISSP 2017 - 3rd International Conference on Information Systems Security and Privacy
236