dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2025-2071

CRITICAL · 10.0 CVSS v4.0 Published 2025-03-31
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
A critical OS Command Injection vulnerability has been identified in the FAST LTA Silent Brick WebUI, allowing remote attackers to execute arbitrary operating system commands via specially crafted input. This vulnerability arises due to improper handling of untrusted input, which is passed directly to system-level commands without adequate sanitization or validation. Successful exploitation could allow attackers to execute arbitrary commands on the affected system, potentially resulting in unauthorized access, data leakage, or full system compromise. Affected WebUI parameters are "hd" and "pi".

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 FAST LTA Silent Brick WebUI allows remote attackers to execute arbitrary operating system commands through the 'hd' and 'pi' parameters. User input is passed directly to system-level commands without sanitization or validation, enabling complete system compromise.

MitigationApply vendor-provided patch when available; until then, restrict network access to the WebUI interface and implement input validation/sanitization on affected parameters to prevent command injection.

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
Low
Privileges
None
Authentication
None
User interaction
None
Scope
P

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:P/AU:N/R:X/V:X/RE:M/U:Amber

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. Confirm FAST LTA Silent Brick WebUI is running
    Access the web interface via browser on the expected IP/hostname (default port 80/443) or use a network scanner to detect open HTTP/HTTPS services on the device
    Affected if The WebUI is accessible and responds to HTTP requests
  2. Identify the Silent Brick software version
    Log into the WebUI and look for a version number in the UI footer, About page, or system settings; alternatively, check the installed software package on the system if you have direct access
    Affected if The installed version matches the vulnerable version range (check vendor advisories for exact vulnerable versions)
  3. Verify the WebUI exposes the affected parameters
    Examine the HTML forms or API endpoints in the WebUI for input fields named 'hd' or 'pi', or attempt to access common web paths that may expose these parameters
    Affected if The parameters 'hd' or 'pi' are present in the web application's forms or URL parameters
  4. Check authentication configuration on the WebUI
    Review the WebUI's authentication settings to determine if the affected endpoints require authentication, or test if unauthenticated requests to the affected parameters are accepted
    Affected if The affected parameters can be reached without proper authentication or with weak authentication controls
  5. Confirm network accessibility of the WebUI
    Determine if the WebUI is exposed to the network (including internal networks) by reviewing firewall rules, NAT configurations, or network segmentation policies
    Affected if The WebUI is reachable from network segments where untrusted users or systems can access it

A user is affected if they run a vulnerable version of FAST LTA Silent Brick WebUI with the WebUI accessible on the network and the 'hd' or 'pi' parameters exposed without proper input sanitization or authentication controls.

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

Apply vendor-provided patch when available; until then, restrict network access to the WebUI interface and implement input validation/sanitization on affected parameters to prevent command injection.

Have this fixed Scoped from the published advisory
  • Consultation16.0 h
  • Implementation32.0 h
  • Testing16.0 h
  • Review / QA8.0 h
72.0 hours of engineering $12,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-2071 — 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-2071 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