Security readout for executives and security teams
Plain-English summary
Lantronix EDS5000 version 2.1.0.0R3 contains command-injection flaws in its SSH Client and SSH Server management pages. An attacker may manipulate delete actions for server keys, users, or known hosts to run arbitrary operating-system commands as root, potentially taking complete control of the device.
Executive priority
Treat as an immediate remediation priority for internet-exposed or broadly reachable devices. Root-level compromise could disrupt operations, alter configurations, expose sensitive information, or provide a foothold into connected environments. Isolate exposure while obtaining confirmed vendor remediation guidance.
Technical view
Missing input sanitization permits OS command injection through parameters used by delete operations on the SSH Client and SSH Server pages. The supplied CVSS 3.1 vector indicates network reachability, low complexity, no required privileges or user interaction, and high confidentiality, integrity, and availability impact. Commands execute with root privileges.
Likely exposure
Highest risk applies to Lantronix EDS5000 devices running 2.1.0.0R3 whose affected management pages are reachable from untrusted networks. The bundle does not establish whether other versions are affected. Inventory and management-interface accessibility must be verified locally.
Exploitation context
The supplied record is not marked as CISA KEV, and the bundle provides no evidence of active exploitation. This does not establish that exploitation is absent. The reported network-accessible, unauthenticated, root-level impact makes exposed devices attractive targets.
Researcher notes
CWE-94 and the description support command injection caused by unsanitized delete-action parameters. The affected-product metadata says “n/a,” while the title and description identify EDS5000 2.1.0.0R3. Patch availability and broader version scope are not established in the supplied bundle; verify them through the cited advisory and vendor guidance.
Mitigation direction
- Identify and prioritize every EDS5000 device running version 2.1.0.0R3.
- Restrict management interfaces to trusted administrative networks and authorized operators.
- Prevent direct internet access to affected management pages.
- Consult the cited CISA advisory and Lantronix guidance for approved remediation.
- Apply vendor-approved updates or mitigations when confirmed, following operational change controls.
Validation and detection
- Confirm each EDS5000 model, firmware version, and management-interface address.
- Test whether SSH Client and SSH Server pages are reachable from untrusted networks.
- Review device and network logs for unexpected management actions or root-level changes.
- Verify access restrictions from both trusted and untrusted network segments.
- After remediation, confirm the installed version and repeat exposure checks.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-94: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process 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.
Open ATT&CK lookupCVE-2025-67035 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
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.
SSVC decision data
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://www.cisa.gov/news-events/ics-advisories/icsa-26-069-02CVE reference, mitre
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Control of Generation of Code ('Code Injection')
Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.