Challenge 6 - Silent Overpressure
Points: 450
Protocol: EtherNet/IP (CIP)
Difficulty: Advanced
The Story
The water distribution system is controlled by a Rockwell/Allen-Bradley PLC. You can see it live on the SCADA HMI - the Distribution tab shows outlet pressure, pump speed, and an alarm system. Your mission: cause an overpressure without triggering the alarm. A real attacker needs to be stealthy.
What You Know
- From process network scans, there’s a PLC at 10.0.4.104:44818
- Port 44818 = EtherNet/IP (Rockwell/Allen-Bradley standard)
- The SCADA HMI Distribution page shows live pressure and alarm status
- The alarm will fire if pressure exceeds the threshold
Step 1: Open the HMI
Make sure you have the SCADA HMI open in Firefox (from CH-03 tunnel).
Open the Distribution tab - watch it throughout this challenge.
You see:
- Outlet pressure (~42 PSI, green)
- Pump speed (62%)
- Mode: AUTO
- Alarm: ARMED - NORMAL (green)
Step 2: Set Up a Tunnel
Forward port 44818 through the EWS to Kali.
Tunnel command?
```bash sshpass -p 'eng2024!' ssh -f -N -L 44818:10.0.4.104:44818 -p 2222 engineer@127.0.0.1 ```Step 3: Scan the PLC
Discover what tags (variables) the PLC exposes.
Command?
```bash python3 ~/tools/enip-tool.py -t 127.0.0.1 -c scan ```Study the tags carefully. Which ones are writable? Which ones control the alarm? What’s the threshold?
Step 4: Try the Obvious Attack
Switch to manual mode and crank the pump to 100%.
Watch the HMI while you do this.
Commands?
```bash python3 ~/tools/enip-tool.py -t 127.0.0.1 -c write --tag MODE_SELECT --value 0 python3 ~/tools/enip-tool.py -t 127.0.0.1 -c write --tag BOOSTER_PUMP_SPEED --value 100 ```What happens? Pressure rises… passes the threshold… ALARM FIRES! Everything resets. You failed.
In a real system, operators would be alerted. A stealthy attacker wouldn’t trip the alarm.
Step 5: Think Like Stuxnet
The Stuxnet worm disabled safety alerts BEFORE causing physical damage. The operators saw normal readings while centrifuges were being destroyed.
What tag controls the alarm? Can you disable it BEFORE causing overpressure?
Hint
Look at the tag list from the scan. There's a tag that enables/disables the alarm. Write to it first, THEN cause the overpressure.Step 6: The Right Order
- First: disable the alarm
- Then: switch to manual mode
- Then: max out the pump
Watch the HMI - pressure rises past the threshold but no alarm fires. The flag appears on the Distribution page.
Need the exact commands?
Check the solution file - but try to figure out the order yourself first.What You Learned
- EtherNet/IP uses named tags - readable and writable without authentication
- Order of operations matters in ICS attacks
- Disabling alarms before causing damage = stealth (Stuxnet technique)
- The HMI shows real-time impact of your attack
- Defence: tag write monitoring, alarm tamper detection
Scoreboard
Updates when pressure exceeds threshold with alarm disabled. The flag also appears on the HMI Distribution page.