📚 Series Maritime Cybersecurity Learning Roadmap | PART 2 Lesson 9 of 7 · Course Index →
PART 2 · Lesson 9 Interception MitM · TLS

Man-in-the-Middle (MitM) Attacks

ARP Spoofing · SSL Stripping · Rogue Access Points · Session Hijacking · TLS and Certificate Validation · HSTS · VSAT and Port Wi-Fi Interception — attacks that intercept communications silently between two parties.

Captain Paul
Captain Paul
Maritime Cybersecurity · IACS UR E26/E27
September 2026
🎯 Lesson Objective

After this lesson you can explain what a Man-in-the-Middle attack achieves, describe ARP spoofing and how it enables local network interception, explain SSL stripping and how it downgrades secure connections, describe rogue access point attacks, explain how TLS, certificate validation, HSTS, and certificate pinning defend against MitM, and identify the specific MitM risks in maritime satellite and port Wi-Fi environments.

Imagine two people exchanging sealed letters through a courier. A Man-in-the-Middle attack is the equivalent of that courier secretly opening every letter, reading it, potentially modifying the contents, resealing it, and delivering it as if nothing happened. Neither sender nor recipient knows the interception is occurring.

In digital communications, a Man-in-the-Middle (MitM) attack positions the attacker between two communicating parties — a client and a server, two internal systems, or a vessel and a shore-based management platform — in a way that intercepts, reads, and potentially modifies the traffic passing between them. The communicating parties continue to believe they are communicating directly with each other.

MitM attacks can target Confidentiality (reading credentials and data), Integrity (modifying data in transit — for example, changing an invoice's bank account number), and even Availability (if the attacker drops packets rather than forwarding them). They are particularly relevant in shared network environments — hotel Wi-Fi, port facilities, coffee shops — where multiple users share the same network segment.

For maritime professionals, the attack surface includes port Wi-Fi networks used by crew members with company laptops, VSAT satellite links, and shore-to-ship communication channels used for operational data exchange. This lesson examines the technical mechanisms and the defences — primarily TLS — that make modern MitM attacks much harder to execute than they once were.

1. ARP Spoofing — Intercepting Local Network Traffic

ARP (Address Resolution Protocol) is used on local networks to map IP addresses to MAC (hardware) addresses. When Device A wants to send data to Device B on the same local network, it broadcasts an ARP request: "Who has IP address 192.168.1.10?" Device B responds with its MAC address. ARP is stateless and unauthenticated — any device can send an unsolicited ARP reply claiming any IP address.

ARP Spoofing (ARP Poisoning) exploits this: the attacker sends forged ARP replies to both the victim and the network gateway, claiming that the attacker's MAC address corresponds to the IP address of the other party. Both devices update their ARP cache with the false mapping and begin sending traffic to the attacker, who forwards it to the real destination. Neither party knows the traffic is being routed through a third machine.

ARP Spoofing — What the Attacker Intercepts
  • Unencrypted HTTP traffic — usernames, passwords, session tokens, form data submitted to non-HTTPS sites.
  • DNS queries — allowing the attacker to observe which domains the victim is resolving (and potentially redirect them via DNS spoofing).
  • Email traffic on unencrypted SMTP/IMAP connections — full email content including attachments.
  • Internal application traffic — if applications use unencrypted internal protocols (Telnet, FTP, older industrial protocols).
  • Session cookies — if not protected by the Secure and HttpOnly flags, allowing session hijacking.

Countermeasures: Dynamic ARP Inspection (DAI) on managed switches validates ARP packets against a trusted DHCP database — preventing spoofed ARP replies from being accepted. Static ARP entries for critical systems, and network segmentation that limits the shared broadcast domain, also reduce ARP spoofing risk.

2. SSL Stripping and Rogue Access Points

🔓 SSL Stripping

SSL Stripping (Moxie Marlinspike, 2009) is a technique that downgrades a secure HTTPS connection to an unencrypted HTTP connection without the victim noticing. When a positioned MitM intercepts a victim's HTTP request that would redirect to HTTPS, it fetches the HTTPS version from the real server itself, but serves the plain HTTP version to the victim. The victim sees no security indicator because the browser's address bar shows HTTP — but thinks the connection is working.

This allows the attacker to read all traffic in cleartext even though the real server is using TLS.

HSTS Defence: HTTP Strict Transport Security (HSTS) tells browsers to always use HTTPS for a domain, refusing HTTP connections entirely. Combined with preloading, HSTS prevents SSL stripping on known domains.

📶 Rogue Access Point (Evil Twin)

An attacker sets up a wireless access point with the same SSID (network name) as a legitimate network — a port facility's "PortWiFi_Free" or a ship's crew Wi-Fi. Devices may automatically connect to the stronger signal. All traffic through the rogue AP passes through the attacker's device before reaching the internet.

This is trivially accomplished with a laptop and a wireless adapter running hostapd. No hacking tools required — the attack creates a standard Wi-Fi hotspot.

Maritime risk: Crew members connecting to "free Wi-Fi" at ports with company laptops may expose corporate credentials, VPN configurations, and email contents to an attacker in the terminal or on the quayside.

3. TLS and Modern MitM Defences

TLS (Transport Layer Security) is the primary defence against MitM on internet communications. TLS provides: (1) encryption — all data in transit is encrypted, so even if intercepted, it cannot be read without the session keys; (2) authentication — the server presents a digital certificate signed by a trusted Certificate Authority (CA), allowing the client to verify it is communicating with the real server, not an impostor; (3) integrity — MAC (Message Authentication Code) values detect any tampering with data in transit.

MitM Defence Layers
TLS 1.3 Current TLS standard. Removes weak cipher suites, mandates forward secrecy (PFS — each session uses unique keys so past sessions cannot be decrypted even if the private key is later compromised). All new services should use TLS 1.3; TLS 1.0 and 1.1 are deprecated.
Certificate Validation Browsers validate the server's TLS certificate against the trusted CA store. A certificate signed by an unknown or untrusted CA produces a browser warning. Users who click through certificate warnings are bypassing the MitM defence entirely.
HSTS HTTP Strict Transport Security instructs browsers to always connect via HTTPS, even if the user types http://. Prevents SSL stripping. Combined with the HSTS preload list (browsers ship with a list of HSTS-enabled domains), this provides protection on first visit.
Certificate Pinning Mobile and desktop applications can pin a specific certificate or public key — refusing to connect if the server presents any other certificate, even a legitimately CA-signed one. Prevents attacks that use rogue CA certificates. Used in banking apps and high-security applications.
VPN for Untrusted Networks A VPN tunnels all traffic through an encrypted channel before it leaves the device, preventing local network interception (including rogue APs and ARP spoofing). All company devices connecting to external networks (port Wi-Fi, hotel, satellite) should use a corporate VPN.
Captain Paul
✍️ Author Insight — From the Field
Captain Paul · Maritime Cybersecurity Consultant · IACS UR E26/E27

During E26 CRSI assessments, the topic of crew device security at ports consistently surfaces as an area requiring immediate attention. In interviews with crew members, it is common to find that officers regularly connect company laptops to port-provided Wi-Fi networks to access email, upload voyage reports, or communicate with the operator — without any VPN or network protection.

Some ports in high-risk regions operate Wi-Fi infrastructure that is unsecured or monitored by parties with interests in the vessel's voyage data, cargo information, or crew details. An officer connecting to a rogue AP — or even a legitimate but poorly secured port Wi-Fi — with a company device and no VPN protection is exposing corporate communications and potentially OT network access credentials.

The policy requirement is straightforward: all company devices must connect through a corporate VPN before accessing any company systems, regardless of the underlying network. "I'm at a trusted port" is not a security posture. The VPN must be configured as always-on, not user-optional. This single policy, consistently enforced, eliminates the local network interception risk regardless of what network the device happens to be connected to.

✅ Key Takeaways — Lesson 9
  • MitM attacks intercept communications between two parties without either knowing — targeting confidentiality, integrity, and potentially availability.
  • ARP Spoofing positions the attacker as the gateway on a local network, allowing interception of all unencrypted traffic.
  • SSL Stripping downgrades HTTPS to HTTP so the attacker can read cleartext traffic even when the server supports TLS.
  • Rogue Access Points (Evil Twin Wi-Fi) allow attackers to intercept all traffic from devices that connect — trivially deployed in port environments.
  • TLS 1.3, HSTS, certificate validation, and certificate pinning are the primary technical defences against MitM.
  • Never click through browser certificate warnings — they indicate a potential MitM attack or a serious misconfiguration.
  • Always-on VPN on company devices is the most effective single policy for maritime crew using external networks at ports.
▶ Next — Lesson 10

Lesson 10 — SQL Injection introduces one of the most persistent and well-documented web application vulnerabilities. We examine how improperly handled database queries allow attackers to extract, modify, or delete data by embedding malicious SQL code in user input — and how parameterised queries and input validation eliminate this vulnerability class.

📚 PART 2 — Understanding Cyber Attacks
DoneLesson 6 — Phishing & Social Engineering
DoneLesson 7 — Ransomware & the Cyber Kill Chain
DoneLesson 8 — DoS and DDoS Attacks
Current Lesson 9 — Man-in-the-Middle (MitM) Attacks
NextLesson 10 — SQL Injection
ComingLesson 11 — Cross-Site Scripting (XSS)
ComingLesson 12 — DNS Spoofing & DNS-based Attacks

⚓ Join the ShipPaulJobs Community

Join →
Share

Comments

Top Ranked · All Posts

Popular Posts