Credentials in the Clear: HTTP Basic Auth to OT Devices Over Port 80

During a passive OT assessment, Wireshark revealed HTTP Basic Authentication sent to operational devices over plain port 80. Base64 is not encryption, so privileged root and admin credentials were recoverable by anyone on the network.

On this page

In IT testing you poke the application. In OT (operational technology) testing you often do the opposite: you sit still and watch. Many industrial and building systems run on fragile, long-lived devices that react badly to active scanning, so a careful assessment leans on passive observation of what is already on the wire. During one such engagement, simply reading the traffic was enough to recover privileged credentials for operational devices. Nothing was attacked. The network handed them over.

This write-up describes authorized, passive testing against a scoped OT environment. The capture shown is redacted. Only analyze traffic on networks you own or are explicitly permitted to assess.

The setup: passive capture on an OT segment

Active penetration testing is not an option in an OT environment. Port scans, fuzzing, and credential brute-forcing can crash fragile industrial devices, corrupt a process, or disrupt live operations, and the risk of taking production equipment offline is simply not acceptable. So the assessment began the safe way: a passive assessment, capturing the network traffic with Wireshark and analyzing only what was already flowing, without sending a single probe at any device.

The management traffic between systems and OT devices was flowing over HTTP on TCP port 80. Reviewing the captured packets in Wireshark, I filtered for HTTP requests and started reading the headers. One header stood out immediately:

GET / HTTP/1.1
Host: <ot-device>
Authorization: Basic <base64 string>

That Authorization: Basic header is the whole finding. HTTP Basic Authentication does not encrypt anything. It takes username:password, encodes it with Base64, and puts it in a header. Base64 is an encoding, not a cipher. Anyone who can see the packet can decode it back to the original credentials in a single step, no key and no cracking required.

Because the traffic was plain HTTP, every one of those requests carried a fully recoverable username and password across the OT network.

The discovery: privileged accounts on the wire

Decoding the captured Authorization headers revealed something worse than a low-privilege service account. The credentials in use were privileged root and admin accounts for the OT devices:

Wireshark view of captured HTTP Basic Authentication traffic, with privileged root and admin credentials recoverable from the Authorization headers (values redacted)

Two things made this stand out. First, these were administrative identities, the accounts that can reconfigure a device, not just read from it. Second, the same credentials appeared repeatedly across the capture, which means they are static and reused, exactly the kind of credential an attacker wants because capturing it once grants lasting access.

Why this is serious in an OT context

A cleartext credential is bad anywhere. In an OT environment it is worse, for reasons specific to how these networks are built and run:

  • Privileged blast radius. root and admin on an OT device can change configuration, alter setpoints, disable safety logic, or take the device offline. That is operational disruption, not just data exposure.
  • Flat, trusted networks. OT segments are frequently flat and implicitly trusted, so an attacker who gains a foothold anywhere on the segment can passively collect this traffic without tripping anything.
  • Long-lived, shared credentials. Industrial devices often ship with shared or default admin accounts that are rarely rotated. A credential captured today is likely still valid months later.
  • Legacy devices. Many OT devices only speak HTTP and cannot be patched to add TLS, so the weakness persists until the network around them is changed.

Impact

An attacker with access to the OT network could:

  • Capture and recover the transmitted credentials directly from the traffic, with no exploitation step.
  • Authenticate to the affected OT devices using the recovered privileged accounts.
  • Make unauthorized configuration changes, manipulate devices, or disrupt operations, and use that access as a pivot toward other connected OT systems.

Given the privileged accounts and the operational impact, this came out as High (CVSS 7.0).

Detection

  • Watch for Authorization: Basic headers on plain HTTP (TCP port 80) anywhere on management VLANs, especially toward device IP ranges.
  • Flag repeated use of shared privileged accounts (root, admin) across multiple devices.
  • Alert on management-plane traffic that is not TLS. On an OT management network, cleartext device administration should be an exception, not the norm.

Remediation

This is a medium effort fix because it touches how devices are reached, not a single config line:

  1. Replace HTTP with HTTPS using strong TLS, and disable Basic Authentication wherever a stronger mechanism is available.
  2. Replace shared or default administrative accounts with unique, strong, per device credentials, and rotate them.
  3. Restrict OT device management interfaces to authorized management systems only, using firewall rules and network access controls.
  4. Isolate legacy devices that cannot support HTTPS inside a dedicated secure management zone, and restrict access to authorized administrators.

Takeaway

The most valuable OT findings are often the quietest ones. No exploit was fired and no device was touched, yet privileged credentials for operational equipment were sitting in plain view on the network. When you assess an OT environment, read the traffic before you touch anything, and treat every Authorization: Basic header on port 80 as a credential already in an attacker’s hands.