dbcve.org
CmcApplication · Nozominetworks

CVE-2022-0550

HIGH · 7.2 CVSS v3.1 Published 2022-03-24
Fix available
A fix is available. Upgrade to 22.0.0 or later.
See remediation →
78/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
Improper Input Validation vulnerability in custom report logo upload in Nozomi Networks Guardian, and CMC allows an authenticated attacker with admin or report manager roles to execute unattended commands on the appliance using web server user privileges. This issue affects: Nozomi Networks Guardian versions prior to 22.0.0. Nozomi Networks CMC versions prior to 22.0.0.

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

This is an authenticated command injection vulnerability via improper input validation in the custom report logo upload functionality. An authenticated attacker with admin or report manager roles can upload a malicious file (disguised as a logo) that allows execution of arbitrary commands with web server user privileges on the affected Nozomi Networks Guardian and CMC appliances.

MitigationUpgrade to Nozomi Networks Guardian and CMC version 22.0.0 or later. Until patched, restrict admin and report manager role assignments to trusted personnel only and monitor for suspicious file upload activity.

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.0.0
GuardianApplication
Affected:< 22.0.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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/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. Check appliance version
    Access the system administration interface or use the CLI command to retrieve the installed version of Nozomi Networks Guardian or CMC. Compare this version number against the vulnerable range (versions prior to 22.0.0).
    Affected if The installed version is earlier than 22.0.0 (e.g., 21.x.x or earlier).
  2. Verify logo upload feature access
    Examine the custom report settings or logo upload configuration within the web interface. Determine whether the logo upload functionality is enabled and accessible to users with admin or report manager roles.
    Affected if The custom report logo upload feature is enabled and available to admin or report manager role users.
  3. Identify privileged role assignments
    Review user role assignments in the administration panel. List all users assigned to either the admin role or the report manager role.
    Affected if One or more user accounts hold admin or report manager privileges, providing the authentication level required to exploit this vulnerability.
  4. Inspect for suspicious uploaded files
    Check the directories used for storing uploaded logo files (typically found in the reports or configuration storage area). Look for files with unexpected extensions, unusual sizes, or files that do not match expected image formats.
    Affected if Unexpected files exist in the logo upload directory that are not standard image files or were not uploaded by trusted administrators.

A user is affected if their Guardian or CMC installation version is prior to 22.0.0 AND the custom report logo upload feature is accessible to authenticated users with admin or report manager roles.

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.0.0 or later
Fixed in 22.0.0
Interim mitigation

Upgrade to Nozomi Networks Guardian and CMC version 22.0.0 or later. Until patched, restrict admin and report manager role assignments to trusted personnel only and monitor for suspicious file upload activity.

Recommended fix High confidence

Guardian 22.0.0 or CMC 22.0.0 (or later stable release)

  1. Identify which Nozomi Networks product is affected (Guardian or CMC)
  2. Check current installed version using system administration interface or CLI
  3. Obtain version 22.0.0 or later of the affected product from the official Nozomi Networks vendor portal
  4. Review Nozomi Networks upgrade documentation for your specific product
  5. Apply the upgrade following vendor-provided upgrade procedures
  6. Verify the installed version is 22.0.0 or higher after upgrade
  7. Confirm the custom report logo upload functionality works correctly post-upgrade

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

Fix this in Cmc Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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