dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2025-9996

MEDIUM · 5.8 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 →
60/100
Remediation priority · Elevated
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
CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') vulnerability exists that could cause the execution of any shell command when executing a netstat command using BLMon Console in an SSH session.

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 confidence

OS command injection vulnerability in BLMon Console allows execution of arbitrary shell commands through improper sanitization of input when executing a netstat command within an SSH session. User-supplied data is passed directly to the shell without neutralization of special shell metacharacters.

MitigationImplement strict input validation and use parameterized command execution or secure APIs that avoid shell interpretation of user input. Alternatively, use allowlists of permitted command arguments.

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

CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:H/VI:L/VA:L/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. Identify BLMon Console installation
    Search for BLMon Console binaries, services, or installation directories on the system. Common locations may include /opt/blmon, /usr/local/blmon, or check system services for blmon-related processes.
    Affected if BLMon Console is found running on the system
  2. Determine installed BLMon Console version
    Run version detection commands such as 'blmon --version', 'blmon -v', or check installed package information if installed via a package manager. Compare against any available version documentation.
    Affected if The installed version is within the affected product range or version cannot be determined (treat as potentially affected)
  3. Verify SSH access is enabled
    Check if SSH service is running and if BLMon Console has SSH-related configurations. Look for SSH configuration files in BLMon directories or check if SSH authentication methods are configured for BLMon.
    Affected if SSH access is enabled and BLMon Console is accessible via SSH sessions
  4. Confirm netstat command functionality exists
    Within BLMon Console's SSH session interface, attempt to locate or access the netstat command functionality. Check if netstat can be invoked through BLMon's command interface or help menus.
    Affected if The netstat command functionality is available within the BLMon Console SSH session
  5. Inspect input handling for command injection vectors
    If netstat is accessible, test the input fields used for netstat arguments. Observe if special shell characters (; | & $ ` etc.) are processed by a shell interpreter or passed directly to the command.
    Affected if User-supplied input to netstat is passed to a shell interpreter without sanitization

A user is affected if BLMon Console is installed with SSH access enabled and the netstat command within SSH sessions accepts unsanitized user input that gets interpreted by a shell.

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

Implement strict input validation and use parameterized command execution or secure APIs that avoid shell interpretation of user input. Alternatively, use allowlists of permitted command arguments.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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