MITM HL7 v2 → tamper lab orders / results
HL7 v2 over MLLP is plaintext pipe-delimited. From the same VLAN as the lab analyser ↔ EHR link, MITM and rewrite OBX result segments — changes the patient's documented test result.
§ Context
Assumed environment: hospital network where HL7 endpoints (lab analysers, imaging, EHR integration engine) share a VLAN or pass through an unsegmented switch. No TLS on HL7 / MLLP.
§ Steps
- 01Foothold on hospital LANInitial AccessT1078— Valid Accounts
- 02ARP spoof analyser ↔ EHRCredential AccessN-ARP-SPOOF— ARP Spoofing / Cache Poisoning
- 03Falsified results enter EHR recordImpactT1565— Data Manipulation
- 04Capture HL7 v2 messagesCredential AccessT1040— Network Sniffing
- 05Inject / modify OBX segmentsImpactHC-HL7-INJECT— HL7 v2 Message Injection
§ References
- T1078Valid Accounts
- T1565Data Manipulation
- T1040Network Sniffing
§ Frequently asked
- What is the "MITM HL7 v2 → tamper lab orders / results" attack path?
- HL7 v2 over MLLP is plaintext pipe-delimited. From the same VLAN as the lab analyser ↔ EHR link, MITM and rewrite OBX result segments — changes the patient's documented test result. It chains 5 steps drawn from real-world offensive-security techniques.
- What starting position does this attack require?
- The first step is Foothold on hospital LAN (T1078) — a initial access primitive. Assumed environment: hospital network where HL7 endpoints (lab analysers, imaging, EHR integration engine) share a VLAN or pass through an unsegmented switch.
- What is the final impact of this kill-chain?
- The final step lands on Inject / modify OBX segments (HC-HL7-INJECT), which falls under Impact. From here, an operator typically pivots into post-exploitation or maintains persistence.
- How can defenders detect or prevent this attack?
- Detection and prevention vary per step. Refer to each linked MITRE ATT&CK entry under "References" — every technique on that page lists defensive controls, detection telemetry, and known threat-actor usage.
§ Related dossiers
- Shared techniques2
5G core GTP-U user-plane injection → subscriber MITM
Attacker on a transit network between mobile-core hops (or with compromised UPF). GTP-U packets are typically unfiltered between PEs; inject packets into subscriber bearers — credential capture, free-of-charge tunnels, downstream attacks.
- Shared techniques2
Mifare Classic crack → cloned hotel key
Many hotel / corporate door systems still use Mifare Classic. Capture nonces during normal use, recover the Crypto-1 key with mfoc / mfcuk, write to a 'magic UID' card — full access to the property.
- Shared techniques2
MITM unencrypted RTP → call eavesdropping
Most internal SIP deployments still use RTP without SRTP. From the same VLAN, ARP-spoof the IP phone + PBX, capture RTP, decode in Wireshark to .wav.