dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2025-23237

MEDIUM · 6.6 CVSS v3.0 Published 2025-01-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
Improper neutralization of special elements used in an OS command ('OS Command Injection') issue exists in UD-LT2 firmware Ver.1.00.008_SE and earlier. If a user logs in to CLI of the affected product, an arbitrary OS command may be executed.

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 · high confidence

OS command injection vulnerability in UD-LT2 firmware CLI allows authenticated users to execute arbitrary operating system commands due to improper neutralization of special elements in user input. The vulnerability exists in firmware versions Ver.1.00.008_SE and earlier, requiring CLI authentication as a prerequisite for exploitation.

MitigationRestrict CLI access to trusted personnel only until vendor firmware update is available. Apply the vendor patch (firmware version later than Ver.1.00.008_SE) when released and verify the fix through authenticated CLI testing.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS 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
High
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:H/PR:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the device model
    Confirm the target device is the UD-LT2 model by checking the device label, web interface, or CLI prompt
    Affected if The device is not a UD-LT2 model
  2. Check the installed firmware version
    Access the device CLI or web management interface and retrieve the firmware version information (typically displayed in system info or version commands)
    Affected if The displayed firmware version is Ver.1.00.008_SE or any version earlier than it
  3. Verify CLI access is enabled
    Confirm the CLI service is running and accessible on the device (check if TCP port for CLI is listening or attempt to connect)
    Affected if CLI authentication is available and reachable on the network or console
  4. Confirm authenticated CLI access
    Attempt to log in to the device CLI with valid credentials
    Affected if You can successfully authenticate to the CLI - this is required for the vulnerability to be exploitable

You are affected if the device is a UD-LT2 running firmware Ver.1.00.008_SE or earlier AND the CLI is accessible with valid authentication credentials.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Restrict CLI access to trusted personnel only until vendor firmware update is available. Apply the vendor patch (firmware version later than Ver.1.00.008_SE) when released and verify the fix through authenticated CLI testing.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,392.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-23237 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-23237 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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