Smart Software Manager SatelliteApplication · Cisco

CVE-2021-1140

CRITICAL · 9.8 CVSS v3.1 Published 2021-01-20
Fix available
A fix is available. Upgrade to after 5.1.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
Multiple vulnerabilities in the web UI of Cisco Smart Software Manager Satellite could allow an unauthenticated, remote attacker to execute arbitrary commands on the underlying operating system. For more information about these vulnerabilities, see the Details section of this advisory.

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 confidence

Multiple command injection vulnerabilities in the Cisco Smart Software Manager Satellite web UI allow an unauthenticated remote attacker to execute arbitrary operating system commands on the underlying host. The critical severity (CVSS 9.8) stems from the lack of authentication requirements and the ability to achieve full system compromise.

MitigationApply the vendor-supplied patch or upgrade to a fixed version of Cisco Smart Software Manager Satellite. As an interim measure, restrict network access to the web UI interface to trusted IPs only.

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 SatelliteApplication
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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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

  1. Confirm Cisco Smart Software Manager Satellite is installed
    Locate the installation directory or check system services for Cisco Smart Software Manager Satellite. On Linux, check for /opt/cssc/satellite or similar installation paths. On Windows, check Program Files for Cisco SSM Satellite.
    Affected if The product is not installed on the system
  2. Check the installed version
    Access the web UI and navigate to the Administration or System Info page to view the version number. Alternatively, check the installation directory for a version file or run 'show version' via CLI if available.
    Affected if The version is 5.1.0 or any version lower than 5.1.0
  3. Verify the web UI is accessible
    Attempt to reach the web interface by accessing the hostname or IP on the configured HTTP/HTTPS port (typically 8443 or 443). Confirm the login page loads.
    Affected if The web UI is reachable from the network and the version is 5.1.0 or lower
  4. Assess network exposure of the web UI
    Review firewall rules, ACLs, or network segmentation to determine if the web UI interface is exposed to untrusted or external networks. Check if the management interface is on a DMZ or directly internet-facing.
    Affected if The web UI is accessible from untrusted networks and the version is 5.1.0 or lower

A system is affected if Cisco Smart Software Manager Satellite version 5.1.0 or lower is installed and its web UI interface is network-accessible.

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 the vendor-supplied patch or upgrade to a fixed version of Cisco Smart Software Manager Satellite. As an interim measure, restrict network access to the web UI interface to trusted IPs only.

Fix this in Smart Software Manager Satellite Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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