CVE-2025-67038: Lantronix EDS5000, G520, and X300 OS Command Injection
An issue was discovered in Lantronix EDS5000 2.1.0.0R3. The HTTP RPC module executes a shell command to write logs when user's authentication fails. The username is directly concatenated with the command without any sanitization. This allow attackers to inject arbitrary OS commands into the username parameter. Injected commands are executed with root privileges.
Security readout for executives and security teams
Plain-English summary
A remote attacker can abuse the device login process without valid credentials to make vulnerable Lantronix equipment run operating-system commands as root. Successful exploitation could expose data, alter configurations, disrupt operations, or provide control of the device. CISA’s KEV listing indicates exploitation has occurred in the wild.
Executive priority
Treat this as an immediate, highest-priority operational-security issue. Identify exposed Lantronix devices, restrict management access, validate firmware applicability, and apply confirmed vendor remediation. Because CISA lists the CVE as known exploited and compromise provides root privileges, potentially affected devices also require evidence-based compromise review.
Technical view
The HTTP RPC authentication-failure path constructs a shell command for logging and directly concatenates the supplied username without sanitization. This creates unauthenticated OS command injection with root privileges. CVSS 3.1 rates it 9.8: network-accessible, low complexity, no privileges or user interaction, with high confidentiality, integrity, and availability impact.
Likely exposure
Risk is greatest where affected HTTP RPC or management interfaces are reachable from the internet or untrusted networks. The bundle identifies EDS5000, G520, X300, E210, and E220 series entries, but its version-range encoding is ambiguous. It explicitly describes EDS5000 firmware 2.1.0.0R3; verify every model and firmware against current Lantronix and CISA guidance.
Exploitation context
CISA KEV status supports active exploitation in the wild. The supplied evidence does not identify attackers, campaign scope, exploitation volume, ransomware use, or whether public exploit code exists. Because authentication is unnecessary and commands execute as root, exposed vulnerable devices should be treated as urgent investigation targets.
Researcher notes
CWE-78 occurs before successful authentication in the failed-login logging path. User-controlled username data reaches a shell command without sanitization, producing root-level command execution. The supplied affected-product metadata appears broader than the narrative description and lacks clear range operators, so exact firmware conclusions require the vendor advisory or CISA CSAF rather than assumptions.
Mitigation direction
Restrict HTTP RPC and management access to trusted administrative networks immediately.
Remove affected management interfaces from direct internet exposure.
Check Lantronix and CISA guidance for applicable fixed firmware; do not infer fixes from the supplied version entries.
Apply confirmed vendor remediation through an emergency change process.
Isolate devices and initiate incident response where compromise is suspected.
Validation and detection
Inventory EDS5000, G520, X300, E210, and E220 devices with exact firmware versions.
Resolve affected-version applicability using the Lantronix advisory and CISA CSAF record.
Confirm HTTP RPC and management interfaces are unreachable from untrusted networks.
Review authentication failures for unusual username values or timing patterns.
Investigate unexpected root processes, configuration changes, outbound connections, and service disruptions.
After remediation, verify firmware versions and repeat exposure checks.
The source record changed after analysis: Material source record changed after analysis.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-78: Command execution behavior lookup
Command injection weaknesses can lead defenders to review execution techniques and command interpreter telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
Exploitation: activeAutomatable: yesTechnical Impact: total
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-78 · source CWE mapping
Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')
Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.