CVE-2021-26724
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 · uneditedOS Command Injection vulnerability when changing date settings or hostname using web GUI of Nozomi Networks Guardian and CMC allows authenticated administrators to perform remote code execution. This issue affects: Nozomi Networks Guardian 20.0.7.3 version 20.0.7.3 and prior versions. Nozomi Networks CMC 20.0.7.3 version 20.0.7.3 and prior versions.
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 confidenceOS command injection vulnerability in Nozomi Networks Guardian and CMC web GUI allows authenticated administrators to execute arbitrary OS commands by injecting malicious payloads into date settings or hostname fields. The vulnerability stems from insufficient input sanitization when processing these configuration parameters.
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>= 19.0.0, <= 19.0.12>= 20.0.0.0, < 20.0.7.4>= 19.0.0, < 19.0.12>= 20.0.0.0, < 20.0.7.4CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed product and versionLocate the Nozomi Networks installation and determine its exact version number (for Guardian or Central Management Control)Affected if The version falls within 19.0.0 to 19.0.12, 20.0.0.0 to 20.0.7.3, or any 20.0.x version below 20.0.7.4
-
Verify web GUI is accessibleConfirm the Nozomi web interface is running and reachable (typically on port 443 or 8443)Affected if The web GUI is exposed and reachable from network segments where untrusted users could potentially obtain administrative access
-
Confirm administrative authentication is possibleCheck if administrator accounts exist and the web login page is accessibleAffected if Administrative credentials are configured and the login interface is available, making exploitation possible for anyone with valid admin credentials
-
Inspect hostname configuration for unexpected valuesNavigate to the system hostname settings in the web GUI or check the configuration backend for the hostname fieldAffected if The hostname field contains or recently contained unexpected characters that could indicate command injection (such as semicolons, backticks, $() subshells, or pipe characters)
-
Inspect date/time settings for unexpected valuesNavigate to the date/time configuration in the web GUI or check the configuration backend for date-related parametersAffected if The date settings contain or recently contained unexpected characters that could indicate command injection attempts
You are affected if the installed Guardian or CMC version is between 19.0.0 and 19.0.12, between 20.0.0.0 and 20.0.7.3, or any 20.0.x version below 20.0.7.4, and the web GUI is accessible to authenticated administrators.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor data19.0.1220.0.7.4
Upgrade to a version newer than 20.0.7.3; if upgrade is not immediately feasible, restrict administrative GUI access to trusted networks and monitor for suspicious hostname/date configuration changes.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-26724 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-26724 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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