dbcve.org
CmcApplication · Nozominetworks

CVE-2023-32649

HIGH · 7.5 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 →
84/100
Remediation priority · High
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
A Denial of Service (Dos) vulnerability in Nozomi Networks Guardian and CMC, due to improper input validation in certain fields used in the Asset Intelligence functionality of our IDS, allows an unauthenticated attacker to crash the IDS module by sending specially crafted malformed network packets. During the (limited) time window before the IDS module is automatically restarted, network traffic may not be analyzed.

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

A Denial of Service vulnerability in Nozomi Networks Guardian and CMC IDS products allows unauthenticated attackers to crash the IDS module by sending specially crafted malformed network packets with improper input validation in the Asset Intelligence functionality. During the automatic restart window, network traffic goes unanalyzed.

MitigationApply vendor-supplied patches for Guardian and CMC; consider network segmentation to limit exposure of IDS to untrusted network segments while awaiting patch deployment.

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.0, < 22.6.3>= 23.0.0, < 23.1.0
GuardianApplication
Affected:>= 22.6.0, < 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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 Nozomi product installed
    Run 'version' command or check system information to confirm whether the system is running Nozomi Networks Guardian or CMC.
    Affected if The product is Nozomi Networks Guardian or CMC.
  2. Determine the installed version
    Execute the product's CLI command to retrieve the firmware/software version (typically 'version' or 'show system info'). Compare the version number against the affected ranges: 22.6.0 through 22.6.3, or 23.0.0 through 23.1.0.
    Affected if The installed version falls within >= 22.6.0 and < 22.6.3, or >= 23.0.0 and < 23.1.0.
  3. Verify the IDS module is active
    Check the system status or configuration to confirm the IDS (Intrusion Detection System) module is currently enabled and running.
    Affected if The IDS module is enabled and processing network traffic.
  4. Confirm Asset Intelligence functionality is enabled
    Access the IDS or Asset Intelligence configuration settings via the management interface or CLI and verify whether the Asset Intelligence feature is turned on.
    Affected if Asset Intelligence is enabled in the IDS configuration.
  5. Assess network exposure of the IDS
    Review network configuration to determine if the IDS interface is bound to or reachable from untrusted network segments.
    Affected if The IDS is directly exposed to untrusted or external network segments without adequate segmentation.

A user is affected if they are running a vulnerable version of Guardian or CMC with the IDS module and Asset Intelligence feature enabled, and the IDS interface is accessible from untrusted networks.

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

Apply vendor-supplied patches for Guardian and CMC; consider network segmentation to limit exposure of IDS to untrusted network segments while awaiting patch deployment.

Recommended fix High confidence

22.6.3 or later for 22.6.x branches; 23.1.0 or later for 23.0.x branches

  1. Identify the currently installed version of Nozomi Networks Guardian or CMC
  2. For versions 22.6.x (>=22.6.0 and <22.6.3): Upgrade to version 22.6.3 or later
  3. For versions 23.0.x (>=23.0.0 and <23.1.0): Upgrade to version 23.1.0 or later
  4. After upgrade, verify the IDS module is running properly
  5. Confirm network traffic analysis is functioning as expected

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

Fix this in Cmc Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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