dbcve.org
Ultra Cloud Core Subscriber Microservices InfrastructureApplication · Cisco

CVE-2022-20762

HIGH · 7.8 CVSS v3.1 Published 2022-04-06
Fix available
A fix is available. Upgrade to 2020.02.2.47 / 2020.02.7.07 or later.
See remediation →
80/100
Remediation priority · High
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 Common Execution Environment (CEE) ConfD CLI of Cisco Ultra Cloud Core - Subscriber Microservices Infrastructure (SMI) software could allow an authenticated, local attacker to escalate privileges on an affected device. This vulnerability is due to insufficient access control in the affected CLI. An attacker could exploit this vulnerability by authenticating as a CEE ConfD CLI user and executing a specific CLI command. A successful exploit could allow an attacker to access privileged containers with root privileges.

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

This is a local privilege escalation vulnerability in the Cisco Ultra Cloud Core Subscriber Microservices Infrastructure (SMI) Common Execution Environment (CEE) ConfD CLI. An authenticated attacker with standard ConfD CLI credentials can execute a specific CLI command to bypass access controls and gain root access to privileged containers. The vulnerability stems from insufficient access control enforcement in the CLI interface.

MitigationApply the Cisco patch for this vulnerability when available, and review ConfD CLI user permissions to limit exposure until the fix is deployed. Ensure least-privilege principles are followed for CLI user accounts.

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
Ultra Cloud Core Subscriber Microservices InfrastructureApplication
Affected:>= 2020.02.2.0, < 2020.02.2.47>= 2020.02.6.0, < 2020.02.7.07

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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

  1. Identify the installed product
    Confirm the system is running Cisco Ultra Cloud Core Subscriber Microservices Infrastructure (SMI) and note the exact software version number
    Affected if The product is Cisco Ultra Cloud Core SMI and the version falls within >= 2020.02.2.0 to < 2020.02.2.47 OR >= 2020.02.6.0 to < 2020.02.7.07
  2. Verify ConfD CLI is accessible
    Confirm the ConfD CLI interface is enabled and accessible on the system
    Affected if ConfD CLI is enabled and reachable (this is the attack surface for the vulnerability)
  3. Check ConfD CLI user accounts
    Review the ConfD CLI user accounts configured on the system and identify any accounts with standard user credentials
    Affected if Standard (non-admin) ConfD CLI user accounts exist - the vulnerability allows authenticated standard users to escalate privileges
  4. Verify user privilege levels
    Examine the privilege level assigned to ConfD CLI users - the vulnerability allows a standard authenticated user to bypass access controls
    Affected if Any ConfD CLI user has less than full administrative privileges, as the flaw permits privilege escalation from standard to root

The environment is affected if ConfD CLI is enabled and the installed version falls within the affected ranges, allowing an authenticated standard user to potentially escalate to root privileges via the CLI bypass.

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.

dbcve · scoped
Upgrade available Upgrade to 2020.02.2.47 / 2020.02.7.07 or later
Fixed in 2020.02.2.472020.02.7.07
Interim mitigation

Apply the Cisco patch for this vulnerability when available, and review ConfD CLI user permissions to limit exposure until the fix is deployed. Ensure least-privilege principles are followed for CLI user accounts.

Recommended fix High confidence

2020.02.2.47 or 2020.02.7.07 (or later stable releases)

  1. 1. Identify the currently installed version of Cisco Ultra Cloud Core Subscriber Microservices Infrastructure
  2. 2. If running 2020.02.2.x, upgrade to version 2020.02.2.47 or later
  3. 3. If running 2020.02.6.x or 2020.02.7.x, upgrade to version 2020.02.7.07 or later
  4. 4. Obtain the upgrade package from Cisco's official distribution channels
  5. 5. Follow Cisco's standard upgrade procedures for the SMI platform
  6. 6. After upgrade, verify the CEE ConfD CLI behaves with proper access controls
  7. 7. Confirm the upgrade was successful and the device is functioning normally

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Ultra Cloud Core Subscriber Microservices Infrastructure Scoped from the published advisory
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,300
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,680.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-20762 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-2022-20762 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