dbcve.org
Improper Access ControlWeakness · CWE-284

CVE-2025-10847

HIGH · 8.4 CVSS v4.0 Published 2025-10-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
93/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
DX Unified Infrastructure Management (Nimsoft/UIM) and below contains an improper ACL handling vulnerability in the robot (controller) component. A remote attacker can execute commands, read from, or write to the target system.

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

DX Unified Infrastructure Management (Nimsoft/UIM) contains an improper ACL handling vulnerability in the robot/controller component. A remote attacker can exploit this ACL misconfiguration to execute arbitrary commands and read/write to the target system due to insufficient access control enforcement in the controller component.

MitigationApply vendor patches for CVE-2025-10847 immediately. Until patched, restrict network access to the robot/controller ports using firewall rules or network segmentation to limit exposure to trusted systems only.

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
None
Authentication
Y
User interaction
None
Scope
N

CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:L/VI:H/VA:H/SC:L/SI:N/SA:L/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:N/AU:Y/R:U/V:D/RE:L/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. Verify DX UIM/Nimsoft installation
    Check for the presence of Nimsoft installation directories (commonly C:\Program Files\Nimsoft or /opt/nimsoft) and running processes named 'robot' or 'nimbus controller'. On Windows, use 'wmic process list' or Task Manager; on Linux, use 'ps -ef | grep -i nim'
    Affected if DX UIM or Nimsoft robot/controller component is present on the system
  2. Identify robot/controller version
    Locate the controller executable (controller.exe on Windows, controller on Linux) and query its version using 'nimversion' utility or by inspecting file properties. Common paths: <nimsoft>/robot/controller.exe or <nimsoft>/bin/controller
    Affected if The installed version cannot be determined or falls below the patched version provided by Broadcom/DX UIM documentation
  3. Check ACL configuration files
    Inspect the controller's ACL configuration file (typically hub.cfg, robot.cfg, or acl.cfg in the <nimsoft>/robot directory). Look for Access_Control_List or security-related entries that control which hosts can send commands to the controller
    Affected if ACL entries are missing, misconfigured, or allow unrestricted access from remote hosts
  4. Verify controller security settings
    Review controller configuration for 'securesl' or 'encryption' settings. Check if 'superuser' account is password-protected. Use 'nimconfig -l' or inspect hub.cfg/robot.cfg for 'allowed_hosts' or 'ip_filter' settings
    Affected if Security settings are disabled, superuser password is default/blank, or allowed_hosts is set to permit any IP
  5. Audit recent controller command logs
    Review controller logs (<nimsoft>/robot/log/controller.log) for command execution entries, particularly from unexpected IP addresses. Look for patterns like 'execute', 'command', or 'run' from remote sources
    Affected if Logs show command execution from untrusted IP addresses or unauthorized users

A system is affected if DX UIM/Nimsoft robot/controller is installed and the ACL configuration is missing, misconfigured, or allows unrestricted remote access.

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 patches for CVE-2025-10847 immediately. Until patched, restrict network access to the robot/controller ports using firewall rules or network segmentation to limit exposure to trusted systems only.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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 locally
dbcve dependency scanner

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