Smart Software Manager On PremApplication · Cisco

CVE-2021-1222

HIGH · 8.1 CVSS v3.1 Published 2021-01-20
Fix available
A fix is available. Upgrade to after 5.1.0 or later.
See remediation →
87/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
A vulnerability in the web-based management interface of Cisco Smart Software Manager Satellite could allow an authenticated, remote attacker to conduct SQL injection attacks on an affected system. The vulnerability exists because the web-based management interface improperly validates values within SQL queries. An attacker could exploit this vulnerability by authenticating to the application and sending malicious SQL queries to an affected system. A successful exploit could allow the attacker to modify values on or return values from the underlying database or the operating system.

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

SQL injection vulnerability in Cisco Smart Software Manager Satellite's web-based management interface allows authenticated attackers to inject malicious SQL queries due to improper input validation. Successful exploitation enables modification of database values and potentially command execution on the underlying operating system.

MitigationApply Cisco's patch when available. Until then, restrict access to the web-based management interface to trusted users only, and monitor for anomalous SQL patterns in logs.

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
Smart Software Manager On PremApplication
Affected:<= 5.1.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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Cisco Smart Software Manager On Prem installation
    Locate the Cisco Smart Software Manager On Prem installation in your environment and determine its version by checking the product's about page, administrative console, or version file provided with the installation
    Affected if Installed version is 5.1.0 or lower
  2. Verify web-based management interface is accessible
    Confirm the web-based management interface is enabled and reachable by attempting to access it or checking the service configuration
    Affected if Web-based management interface is exposed and accessible
  3. Review authentication configuration
    Examine the user authentication settings and access controls for the web-based management interface to determine what accounts have privileged access
    Affected if Multiple untrusted or unauthorized accounts have authenticated access to the interface
  4. Inspect database configuration and privileges
    Check the database user permissions and configuration used by the application to determine if the application database user has elevated privileges beyond what is necessary
    Affected if Database account used by the application has permissions allowing data modification or command execution capabilities

You are affected if Cisco Smart Software Manager On Prem version 5.1.0 or lower is installed and its web-based management interface is accessible to authenticated users.

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.

From vendor data
Upgrade available Upgrade to a release after 5.1.0
Interim mitigation

Apply Cisco's patch when available. Until then, restrict access to the web-based management interface to trusted users only, and monitor for anomalous SQL patterns in logs.

Fix this in Smart Software Manager On Prem Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-1222 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-1222 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