CVE-2023-23574
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 · uneditedA blind SQL Injection vulnerability in Nozomi Networks Guardian and CMC, due to improper input validation in the alerts_count component, 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 · high confidenceA blind SQL injection vulnerability exists in Nozomi Networks Guardian and CMC's alerts_count component due to improper input validation. An authenticated attacker can execute arbitrary SQL statements on the underlying database, potentially extracting sensitive data, modifying database structure, or disrupting availability.
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< 22.6.2< 22.6.2CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed productDetermine if the system is running Nozomi Networks CMC or Guardian. Check the system documentation or login banner for product name.Affected if Product is Nozomi Networks CMC or Guardian
-
Check CMC versionFor CMC installations: Navigate to Help > About or check the CMC web interface footer/version display. Alternatively, check the installed RPM package: rpm -q | grep -i cmc or check /opt/nozomi/version file if accessible.Affected if Version is lower than 22.6.2
-
Check Guardian versionFor Guardian installations: Navigate to Help > About in the Guardian web interface or check the version file in the installation directory. Use command: systemctl status guardian or check application logs for version info.Affected if Version is lower than 22.6.2
-
Verify alerts_count endpoint accessibilityCheck if the /alerts_count endpoint is accessible in the web application. Review web server access logs for requests to endpoints containing 'alerts_count'. Log location typically: /var/log/nginx/ or /opt/nozomi/logs/.Affected if The alerts_count endpoint is exposed and responds to requests
-
Confirm authentication is requiredVerify that authentication is enforced for the alerts_count component. Attempt to access the endpoint without credentials or check authentication configuration in the application settings.Affected if The endpoint can be accessed without valid authentication credentials (meaning any authenticated user could exploit this)
A system is affected if it is running Nozomi Networks CMC or Guardian with a version lower than 22.6.2, and the alerts_count component is accessible to authenticated users.
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.
dbcve · scoped22.6.2
Implement proper input validation and use parameterized queries (prepared statements) for all database interactions in the alerts_count component. Validate and sanitize all user-supplied input before incorporating it into SQL queries.
Guardian and CMC version 22.6.2 or later
- 1. Verify the currently installed version of Nozomi Networks Guardian or CMC by accessing the system console or web UI
- 2. Download the Nozomi Networks version 22.6.2 or later from the official Nozomi Networks support portal (https://www.nozominetworks.com/support/)
- 3. Review the upgrade guide specific to your product (Guardian or CMC) from Nozomi Networks documentation
- 4. Create a full system backup or snapshot before proceeding with the upgrade
- 5. Schedule a maintenance window as upgrades may require system downtime
- 6. Apply the upgrade following the documented procedure for your specific deployment type
- 7. After upgrade completion, verify the new version is 22.6.2 or higher
- 8. Confirm the alerts_count component is functioning normally and test that SQL injection is no longer possible
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-23574 — 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-2023-23574 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