dbcve.org
Connected Mobile ExperiencesApplication · Cisco

CVE-2020-3152

MEDIUM · 6.7 CVSS v3.1 Published 2020-08-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
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 Cisco Connected Mobile Experiences (CMX) could allow an authenticated, local attacker with administrative credentials to execute arbitrary commands with root privileges. The vulnerability is due to improper user permissions that are configured by default on an affected system. An attacker could exploit this vulnerability by sending crafted commands to the CLI. A successful exploit could allow the attacker to elevate privileges and execute arbitrary commands on the underlying operating system as root. To exploit this vulnerability, an attacker would need to have valid administrative credentials.

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 vulnerability in Cisco Connected Mobile Experiences (CMX) allows an authenticated attacker with administrative credentials to escalate privileges to root by sending crafted commands to the CLI. The root cause is improper default user permissions configured on the affected system that fail to properly restrict administrative users from executing arbitrary operating system commands with elevated privileges.

MitigationApply the vendor patch from Cisco for this vulnerability. Until patched, strictly control administrative credential access and monitor CLI activity for unusual commands.

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
Connected Mobile ExperiencesApplication
Affected:= 10.6.0= 10.6.1= 10.6.2

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

CVSS:3.1/AV:L/AC:L/PR:H/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 if Cisco CMX is installed
    Locate the Cisco Connected Mobile Experiences installation or running service. Check common installation paths or running processes for 'cmx' or 'Connected Mobile Experiences' references.
    Affected if The product is present in the environment
  2. Check installed CMX version
    Access the CMX CLI or web interface and retrieve the version number. Compare it against the affected versions: 10.6.0, 10.6.1, or 10.6.2.
    Affected if The installed version matches exactly 10.6.0, 10.6.1, or 10.6.2
  3. Verify administrative CLI access exists
    Confirm that the CMX administrative CLI is accessible and administrative user accounts are configured. Check if admin-level users can log into the CLI.
    Affected if Administrative CLI access is enabled and admin users exist in the system
  4. Inspect user permission configuration
    Review the default user permission settings in CMX. Examine whether administrative users have unrestricted ability to execute operating system commands through the CLI.
    Affected if Admin users have permission to run arbitrary OS commands with elevated (root) privileges

You are affected if Cisco CMX is installed at version 10.6.0, 10.6.1, or 10.6.2 and administrative CLI access is available, allowing privileged users to execute arbitrary OS commands.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor patch from Cisco for this vulnerability. Until patched, strictly control administrative credential access and monitor CLI activity for unusual commands.

Fix this in Connected Mobile Experiences Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,620
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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