CVE-2023-20110
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 vulnerability in the web-based management interface of Cisco Smart Software Manager On-Prem (SSM On-Prem) could allow an authenticated, remote attacker to conduct SQL injection attacks on an affected system. This vulnerability exists because the web-based management interface inadequately validates user input. An attacker could exploit this vulnerability by authenticating to the application as a low-privileged user and sending crafted SQL queries to an affected system. A successful exploit could allow the attacker to read sensitive data on the underlying database.
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 confidenceSQL injection vulnerability in Cisco SSM On-Prem web-based management interface due to inadequate user input validation. An authenticated attacker with low-privileged access can send crafted SQL queries to read sensitive data from the underlying database.
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< 8-202303CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 if Cisco Smart Software Manager On Prem is installedLocate the Cisco SSM On-Prem installation directory or check system inventory for this product nameAffected if The product is not present on the system, then this CVE does not apply
-
Determine the installed version of Cisco SSM On PremAccess the web-based management interface and navigate to the About or version information page, or use the command-line interface if available to retrieve the version numberAffected if The installed version is lower than 8-202303 (for example, 7-202212, 8-202301, etc.)
-
Verify the web-based management interface is enabledCheck if the web interface service is running and accessible on the configured port (typically 443 or 8443)Affected if The web management interface is enabled and accessible, providing the attack surface for SQL injection
-
Confirm low-privileged user authentication is permittedReview the user role configurations in the administration settings to verify that low-privileged accounts (such as standard user or read-only roles) can access the web interfaceAffected if Low-privileged users are allowed to authenticate to the web interface, enabling the attack vector described in the CVE
You are affected if Cisco Smart Software Manager On Prem is running with a version lower than 8-202303 and the web-based management interface is accessible to low-privileged 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 · scoped8-202303
Apply the Cisco patch when available; ensure all user inputs in the web interface are properly sanitized using parameterized queries or input validation controls.
8-202303 or later
- 1. Determine current version of Cisco Smart Software Manager On-Prem by accessing the web-based management interface or running: show version
- 2. Confirm the current version is below 8-202303
- 3. Download Cisco Smart Software Manager On-Prem version 8-202303 or later from the Cisco Software Download center (requires valid Cisco service contract)
- 4. Review Cisco SSM On-Prem upgrade documentation for backup and migration requirements
- 5. Back up the current SSM On-Prem configuration and database
- 6. Perform the upgrade to version 8-202303 following the documented upgrade procedure
- 7. Verify the upgrade was successful by checking the new version number
- 8. Log in to the web interface and confirm the SQL injection vulnerability is remediated by verifying low-privileged users can no longer inject SQL queries
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation16.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 $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-20110 — 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-20110 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