CVE-2025-70082
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn issue in Lantronix EDS3000PS v.3.1.0.0R2 allows an attacker to execute arbitrary code and obtain sensitive information via the ltrx_evo component
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceLantronix EDS3000PS v.3.1.0.0R2 contains a critical vulnerability in the ltrx_evo component that allows unauthenticated attackers to execute arbitrary code and obtain sensitive information. The CVSS 9.8 score indicates the vulnerability is remotely exploitable with minimal complexity and no authentication required.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 3.1.0.0r2= 3.1.0.0r2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the device modelAccess the device's web interface or console and locate the model number displayed in the system information or device status page. Alternatively, check the physical device label for EDS3016ps1ns or EDS3008ps1ns markings.Affected if The device model is Lantronix EDS3016ps1ns or EDS3008ps1ns
-
Verify the firmware versionNavigate to the device's firmware or software version information page in the web management interface, or use the command line interface and run the appropriate version display command.Affected if The installed firmware version is exactly 3.1.0.0r2 (no other version number indicates the specific affected build)
-
Determine if ltrx_evo component is accessibleAttempt to access the ltrx_evo management interface over the network on common management ports (typically HTTP/HTTPS on ports 80/443 or the device's configured management port). Check if the endpoint responds to requests.Affected if The ltrx_evo web interface is reachable from the network and responds to unauthenticated requests
-
Check for unauthorized access or configuration changesReview the device's event logs, access logs, and audit trails for any entries showing requests from unexpected IP addresses, successful logins without corresponding legitimate sessions, or modifications to user accounts, network settings, or startup configurations.Affected if Logs show unauthorized access attempts, successful logins from unknown sources, or unexpected configuration changes
-
Inspect for unexpected processes or servicesIf CLI access is available, use commands to list running processes, active network connections, and recently modified system files. Look for unknown executables, listening ports not associated with normal device operation, or scripts in temporary directories.Affected if Unexpected processes are running, unknown services are listening on network ports, or suspicious files exist in system directories
You are affected if your device is an EDS3016ps1ns or EDS3008ps1ns running firmware version 3.1.0.0r2 with the ltrx_evo component accessible on the network.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply vendor-supplied firmware patch for EDS3000PS when available; if no patch exists, restrict network access to the ltrx_evo management interface and monitor for Indicators of Compromise.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-70082 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-70082 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data