dbcve.org
CmcApplication · Nozominetworks

CVE-2023-2567

HIGH · 8.8 CVSS v3.1 Published 2023-09-19
Fix available
A fix is available. Upgrade to 22.6.3 / 23.1.0 or later.
See remediation →
94/100
Remediation priority · Urgent
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 SQL Injection vulnerability has been found in Nozomi Networks Guardian and CMC, due to improper input validation in certain parameters used in the Query functionality. Authenticated users may be able to execute arbitrary SQL statements on the DBMS used by the web application.

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

SQL injection vulnerability in Nozomi Networks Guardian and CMC web application. Improper input validation in the Query functionality allows authenticated users to execute arbitrary SQL statements on the underlying database management system.

MitigationImplement parameterized queries/prepared statements for all database interactions in the Query functionality. Apply strict input validation and consider implementing a Web Application Firewall as an interim control.

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.3>= 23.0.0, < 23.1.0
GuardianApplication
Affected:< 22.6.3>= 23.0.0, < 23.1.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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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 the installed product
    Log into the Nozomi Networks management interface or check system documentation to confirm whether the deployment uses CMC (Central Management Console) or Guardian, or both.
    Affected if The system is running either CMC or Guardian software.
  2. Determine the installed version
    Access the web interface: click the user menu (usually top-right) and select 'About' or 'System Information' to view the version number. Alternatively, use the command line: run 'version' or check '/opt/nozomi/version' if SSH access is available.
    Affected if The installed version is < 22.6.3, or >= 23.0.0 and < 23.1.0.
  3. Verify the Query functionality is accessible
    In the web interface, navigate to the Query feature (often under 'Reports', 'Search', or a dedicated 'Query' menu item). Confirm the feature is enabled and accessible to your user account.
    Affected if The Query functionality is available and accessible to authenticated users.
  4. Confirm user authentication is enabled
    Check that the web application requires login and that user accounts with access to the Query feature are active. Review 'Users' or 'Access Control' settings in the administration section.
    Affected if Authenticated users can access the Query functionality.

A system is affected if it runs CMC or Guardian versions < 22.6.3, or >= 23.0.0 and < 23.1.0, and the Query functionality is accessible to authenticated users.

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.3 / 23.1.0 or later
Fixed in 22.6.323.1.0
Interim mitigation

Implement parameterized queries/prepared statements for all database interactions in the Query functionality. Apply strict input validation and consider implementing a Web Application Firewall as an interim control.

Recommended fix High confidence

Upgrade to version 22.6.3 or later for branches < 23.0.0; upgrade to version 23.1.0 or later for branches >= 23.0.0

  1. 1. Identify the current version of Nozomi Networks Guardian or CMC by accessing the web UI or using the system CLI
  2. 2. If running a version < 22.6.3, plan to upgrade to version 22.6.3 or later
  3. 3. If running a version >= 23.0.0 but < 23.1.0, plan to upgrade to version 23.1.0 or later
  4. 4. Before upgrading, create a complete system backup following Nozomi Networks backup procedures
  5. 5. Schedule a maintenance window as upgrades may require system downtime
  6. 6. Download the appropriate fixed version from the Nozomi Networks customer portal or official distribution channels
  7. 7. Apply the upgrade following the official Nozomi Networks upgrade documentation for your specific product (Guardian or CMC)
  8. 8. After upgrade completion, verify the new version matches the expected fixed release
Caveat Review Nozomi Networks release notes for any configuration or feature changes between your current version and the target fixed version

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

Fix this in Cmc Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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