dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2025-54084

HIGH · 8.5 CVSS v4.0 Published 2025-09-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
87/100
Remediation priority · High
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
OS Command ('OS Command Injection') vulnerability in Calix GigaCenter ONT (Quantenna SoC modules) allows authenticated attackers with 'super' user credentials to execute arbitrary OS commands through improper input validation, potentially leading to full system compromise.This issue affects GigaCenter ONT: 844E, 844G, 844GE, 854GE.

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 Calix GigaCenter ONT devices (Quantenna SoC modules) allows authenticated 'super' users to execute arbitrary OS commands due to improper input validation. This affects models 844E, 844G, 844GE, and 854GE, potentially enabling full system compromise with root-level access.

MitigationApply vendor firmware patches when available; until then, restrict access to the device management interface to trusted networks only and monitor for suspicious command execution patterns.

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
Adjacent
Complexity
Low
Privileges
High
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:A/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/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:X/AU:X/R:X/V:X/RE:X/U:X

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 device model is affected
    Access the device web interface or CLI and identify the exact model number (844E, 844G, 844GE, or 854GE). Check the device status page or use 'show version' command via console/Telnet/SSH.
    Affected if Device model is one of: 844E, 844G, 844GE, or 854GE
  2. Identify firmware version
    Navigate to the device management interface (typically via web UI at the LAN IP) and locate the firmware version in system status or administration settings. Alternatively, use 'show version' or 'cat /proc/version' via console/Telnet if available.
    Affected if Firmware version is unpatched and matches the vulnerable release; compare against any vendor-released patch versions when available
  3. Verify super user access exists
    Check if any account with 'super' or 'administrator' privileges is configured on the device. Access the user management or account settings panel in the web UI or use 'show users' via CLI.
    Affected if A 'super' user account is enabled and accessible, providing the authentication level required to reach the vulnerable code path
  4. Check for exposed management interface
    Determine if the device web UI (port 80/443) or CLI (Telnet/SSH) is reachable from untrusted networks. Review firewall rules, port forwarding configurations, or NAT settings on upstream devices.
    Affected if The device management interface is exposed to untrusted networks, allowing external attackers to attempt authentication as super user
  5. Inspect for command injection entry points
    In the web UI, examine features that accept user input and execute system commands, such as diagnostic tools (ping, traceroute), network diagnostics, or configuration utilities. Look for parameters that might be passed to shell commands without proper sanitization.
    Affected if Any diagnostic or configuration feature that accepts input and executes OS commands is accessible to the authenticated super user
  6. Review logs for suspicious command execution
    Check system logs, command history, or audit logs on the device (often via 'show log' or in the web UI under diagnostics/Logs) for unexpected or unauthorized commands that appear to execute shell commands.
    Affected if Logs show command patterns consistent with injection attempts or unauthorized command execution beyond normal administrative operations

Your environment is affected if you run a vulnerable model (844E/844G/844GE/854GE) with unpatched firmware where the device management interface is accessible to users with super user privileges, and any diagnostic or configuration feature accepting user input is present and exploitable.

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 firmware patches when available; until then, restrict access to the device management interface to trusted networks only and monitor for suspicious command execution patterns.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,730
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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