dbcve.org
CmcApplication · Nozominetworks

CVE-2023-22378

MEDIUM · 6.5 CVSS v3.1 Published 2023-08-09
Fix available
A fix is available. Upgrade to 22.6.2 or later.
See remediation →
71/100
Remediation priority · Elevated
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
A blind SQL Injection vulnerability in Nozomi Networks Guardian and CMC, due to improper input validation in the sorting parameter, allows an authenticated attacker to execute arbitrary SQL statements on the DBMS used by the web application. Authenticated users may be able to extract arbitrary information from the DBMS in an uncontrolled way, alter its structure and data, and/or affect 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

Blind SQL Injection vulnerability in Nozomi Networks Guardian and CMC web applications. The sorting parameter lacks proper input validation, allowing authenticated attackers to inject and execute arbitrary SQL statements on the underlying database management system.

MitigationApply vendor-supplied security patches for Guardian and CMC. As a compensating control, review and restrict user permissions to the minimum required, and monitor database activity for suspicious queries.

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:< 22.6.2
GuardianApplication
Affected:< 22.6.2

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
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

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 the installed product and version
    Access the web interface and navigate to the About or Help section to find the version number. Alternatively, log into the device via SSH and run the command: 'version' or 'show system info' to retrieve the installed version.
    Affected if The product is Nozomi Networks Guardian or CMC and the version is below 22.6.2
  2. Confirm the web application is accessible
    Verify that the Guardian or CMC web interface is reachable by accessing the login page via HTTPS on the configured IP or hostname.
    Affected if The web interface is exposed and running, which is required for the sorting parameter to be exploitable
  3. Verify authentication is enabled
    Check the web application security settings to confirm user authentication is required for access. Review the user management configuration to see what accounts exist.
    Affected if User authentication is configured, as the SQL injection requires an authenticated attacker to inject malicious sorting parameter values

You are affected if you are running Nozomi Networks Guardian or CMC with a version lower than 22.6.2 and the web interface is accessible with authentication enabled.

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 22.6.2 or later
Fixed in 22.6.2
Interim mitigation

Apply vendor-supplied security patches for Guardian and CMC. As a compensating control, review and restrict user permissions to the minimum required, and monitor database activity for suspicious queries.

Recommended fix High confidence

22.6.2

  1. 1. Identify current version of Nozomi Networks Guardian or CMC by checking the system administration interface or running: `system status`
  2. 2. Create a complete backup of the system including database and configuration files before proceeding with the upgrade
  3. 3. Download the fixed version (22.6.2) from the official Nozomi Networks support portal or authorized distribution channel
  4. 4. Follow the standard Nozomi Networks upgrade procedure: stop services, apply the upgrade package, verify integrity, and restart services
  5. 5. After upgrade completes, verify the new version is 22.6.2 or later using: `system status` or the web UI
  6. 6. Confirm the SQL injection vulnerability is resolved by testing the sorting parameter functionality in the web application

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

Fix this in Cmc Scoped from the published advisory
  • Consultation8.0 h
  • Implementation4.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,840
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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