dbcve.org
Cgr1000 Compute ModulePlugin / extension · Cisco

CVE-2022-20727

MEDIUM · 6.7 CVSS v3.1 Published 2022-04-15
Fix available
A fix is available. Upgrade to 1.4.1 / 1.15.0.1 or later.
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
Multiple vulnerabilities in the Cisco IOx application hosting environment on multiple Cisco platforms could allow an attacker to inject arbitrary commands into the underlying host operating system, execute arbitrary code on the underlying host operating system, install applications without being authenticated, or conduct a cross-site scripting (XSS) attack against a user of the affected software. 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 vulnerabilities in Cisco IOx application hosting environment on multiple Cisco platforms allow command injection into the host OS, arbitrary code execution on the host, unauthenticated application installation, and XSS attacks against users.

MitigationApply Cisco patches for IOx per the official advisory; disable IOx if not needed; restrict network access to IOx management interfaces.

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
Cgr1000 Compute ModulePlugin / extension
Affected:< 1.15.0.1
Ic3000 Industrial Compute GatewayApplication
Affected:< 1.4.1
Ir510 Operating SystemApplication
Affected:< 6.5.9
iOSOperating system
Affected:= 15.2\(5\)e1= 15.2\(6\)e0a= 15.2\(6\)e1= 15.2\(6\)e2a= 15.2\(7\)e= 15.2\(7\)e0b= 15.2\(7\)e0s= 15.6\(1\)t1= 15.6\(1\)t2= 15.6\(1\)t3= 15.6\(2\)t= 15.6\(2\)t0a
Ios XeOperating system
Affected:= 16.3.1= 16.3.1a= 16.3.2= 16.3.3= 16.3.4= 16.3.5= 16.3.5b= 16.3.6= 16.3.7= 16.3.8= 16.3.9= 16.3.10

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 the device model
    Run 'show version' or check the physical device label to determine the Cisco product model (Cgr1000, Ic3000, Ir510, iOS device, or IOS XE device)
    Affected if The device model is one of: Cgr1000 Compute Module, Ic3000 Industrial Compute Gateway, Ir510, or a Cisco iOS/IOS XE device that supports IOx
  2. Check the installed software version
    Run 'show version' to display the running software version. For IOS XE, also run 'show version' and note the Cisco IOS XE version number.
    Affected if The version matches or falls below the affected ranges: Cgr1000 < 1.15.0.1, Ic3000 < 1.4.1, Ir510 < 6.5.9, iOS = 15.2(5)e1/15.2(6)e0a/15.2(6)e1/15.2(6)e2a/15.2(7)e/15.2(7)e0b/15.2(7)e0s/15.6(1)t1/15.6(1)t2/15.6(1)t3/15.6(2)t/15.6(2)t0a, IOS XE = 16.3.1 through 16.3.10
  3. Verify if IOx is enabled
    Run 'show iox' or 'show app-hosting list' (depending on platform) to check the IOx service status
    Affected if IOx is enabled and running on the device
  4. Check IOx application hosting configuration
    Run 'show running-config | include iox' or 'show app-hosting detail' to see active IOx configurations and installed applications
    Affected if IOx application hosting is configured or any applications are installed via IOx

The device is affected if it is a listed product model, runs an affected software version, AND has IOx enabled (if IOx is disabled, the attack surface does not exist even on vulnerable versions).

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 1.4.1 / 1.15.0.1 / 6.5.9 or later
Fixed in 1.4.11.15.0.16.5.9
Interim mitigation

Apply Cisco patches for IOx per the official advisory; disable IOx if not needed; restrict network access to IOx management interfaces.

Fix this in Cgr1000 Compute Module Scoped from the published advisory
  • Consultation8.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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