CVE-2023-29245
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 SQL Injection vulnerability in Nozomi Networks Guardian and CMC, due to improper input validation in certain fields used in the Asset Intelligence functionality of our IDS, may allow an unauthenticated attacker to execute arbitrary SQL statements on the DBMS used by the web application by sending specially crafted malicious network packets. Malicious users with extensive knowledge on the underlying system 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 confidenceSQL injection vulnerability in Nozomi Networks Guardian and CMC's IDS Asset Intelligence functionality allows unauthenticated attackers to execute arbitrary SQL statements via specially crafted malicious network packets due to improper input validation in certain fields.
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.0, < 22.6.3>= 23.0.0, < 23.1.0>= 22.6.0, < 22.6.3>= 23.0.0, < 23.1.0CVSS 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
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 your Nozomi product typeDetermine whether the system is Nozomi Networks Guardian or CMC (Central Management Console) - this can typically be found in the product UI header, about page, or system information sectionAffected if The product is either Guardian or CMC
-
Check installed version against affected rangesLocate the installed version number in the product's system information, about page, or CLI (commonly via 'version' or 'show version' command). Compare it to the affected ranges: 22.6.0 through 22.6.2, or 23.0.0Affected if The installed version falls within >= 22.6.0 and < 22.6.3, OR >= 23.0.0 and < 23.1.0
-
Verify IDS Asset Intelligence module statusCheck whether the IDS (Intrusion Detection System) Asset Intelligence functionality is enabled or configured on the appliance. This is typically found in the IDS/Asset settings, monitoring configuration, or intelligence feature toggles within the product UIAffected if IDS Asset Intelligence is actively enabled or configured on the system
-
Review network logs for SQL injection indicatorsExamine IDS/asset intelligence network logs, SQL database logs, or security event logs for unusual or malformed SQL statements, unexpected database queries, or signs of injection attempts arriving via network packetsAffected if Suspicious SQL-like patterns or unauthorized database queries are present in the logs
-
Audit database for unauthorized changes or anomaliesReview the underlying database (PostgreSQL or similar) for unexpected tables, unauthorized records in asset tables, or SQL statements that were not originated from legitimate application codeAffected if Database contains unexpected changes, unauthorized records, or evidence of arbitrary SQL execution
A system is affected if it is Nozomi Networks Guardian or CMC with a version in the listed ranges AND the IDS Asset Intelligence feature is enabled, making it vulnerable to unauthenticated SQL injection via specially crafted network packets.
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.323.1.0
Apply vendor-provided patches for Guardian and CMC; implement strict input validation and parameterized queries in the affected Asset Intelligence fields; consider WAF deployment as additional layer of protection.
22.6.3 or 23.1.0 (depending on current branch)
- Identify the currently installed version of Nozomi Networks Guardian or CMC by checking the system management interface or using the command line tool
- If running version 22.6.0, 22.6.1, or 22.6.2: Upgrade to version 22.6.3
- If running version 23.0.0 through 23.0.x: Upgrade to version 23.1.0
- Follow the standard upgrade procedure documented in the Nozomi Networks installation guide, ensuring to backup the system before upgrading
- After upgrade, verify the Asset Intelligence functionality is working correctly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-29245 — 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-29245 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