dbcve.org
CmcApplication · Nozominetworks

CVE-2025-3719

HIGH · 8.1 CVSS v3.1 Published 2025-10-07
Fix available
A fix is available. Upgrade to 25.2.0 or later.
See remediation →
87/100
Remediation priority · High
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
An access control vulnerability was discovered in the CLI functionality due to a specific access restriction not being properly enforced for users with limited privileges. An authenticated user with limited privileges can issue administrative CLI commands, altering the device configuration, and/or affecting its availability.

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

This is an authorization bypass vulnerability in CLI functionality where proper privilege level enforcement is missing. An authenticated user with limited privileges can bypass access controls and execute administrative CLI commands, allowing unauthorized modification of device configuration or disruption of service.

MitigationImplement and enforce proper role-based access control (RBAC) checks at the CLI command execution layer to verify user privilege levels before allowing administrative commands. All CLI commands requiring elevated privileges must validate the user's authorization level.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
CmcApplication
Affected:< 25.2.0
GuardianApplication
Affected:< 25.2.0

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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 product and installed version
    Access the device management interface or check system information to determine if the installed product is Nozomi Networks CMC or Guardian. Locate the version number in the product UI or via CLI command 'show version' or similar.
    Affected if The installed product is CMC or Guardian and the version is below 25.2.0
  2. Confirm CLI access method exists
    Verify that the device has CLI functionality enabled. This may be via SSH, console access, or a management interface that exposes CLI commands. Check if CLI access is listed in the system's available management interfaces.
    Affected if CLI interface is accessible and the version is below 25.2.0
  3. Identify user privilege levels configured
    Review the user accounts configured on the device. Access the user management section of the management interface or use CLI commands such as 'show users' or 'show privileges' to list all configured accounts and their assigned privilege levels.
    Affected if There are user accounts with limited or non-administrative privilege levels and the version is below 25.2.0
  4. Test administrative CLI command execution by limited user
    Log in to the CLI using a limited-privilege user account that should not have administrative access. Attempt to execute administrative-level CLI commands that should require elevated privileges, such as configuration modification or system management commands.
    Affected if A limited-privilege user can successfully execute administrative CLI commands that should be restricted to higher privilege levels, confirming the authorization bypass is present

A user is affected if they are running CMC or Guardian versions below 25.2.0 and have limited-privilege users who can bypass authorization to execute administrative CLI commands.

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.

dbcve · scoped
Upgrade available Upgrade to 25.2.0 or later
Fixed in 25.2.0
Interim mitigation

Implement and enforce proper role-based access control (RBAC) checks at the CLI command execution layer to verify user privilege levels before allowing administrative commands. All CLI commands requiring elevated privileges must validate the user's authorization level.

Recommended fix High confidence

CMC and Guardian version 25.2.0 or later

  1. 1. Back up the current device configuration before upgrading.
  2. 2. Ensure the device has sufficient power and network stability during the upgrade process.
  3. 3. Download the upgrade package for version 25.2.0 or later from the official Nozomi Networks support portal.
  4. 4. Upload the upgrade file to the device through the management interface or SCP.
  5. 5. Initiate the upgrade process following the documented upgrade procedure.
  6. 6. Verify the upgrade was successful by checking the version number.
  7. 7. Confirm that the authorization fix is working by testing that limited-privilege users can no longer execute administrative CLI commands.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Cmc Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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