dbcve.org
Cgr1000 Compute ModulePlugin / extension · Cisco

CVE-2022-20726

HIGH · 7.5 CVSS v3.1 Published 2022-04-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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 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 · high confidence

Multiple critical vulnerabilities in Cisco IOx application hosting environment allow attackers to inject arbitrary commands into the host OS, execute arbitrary code, install applications without authentication, or conduct XSS attacks against users. The vulnerabilities stem from insufficient input validation and missing authentication controls in the IOx management interface.

MitigationApply Cisco-provided security patches for IOx; if patches are unavailable, disable the IOx service and 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:all versions
Ic3000 Industrial Compute GatewayApplication
Affected:all versions
iOSOperating system
Affected:all versions= 15.2\(5\)e1= 15.2\(5\)e2c= 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

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
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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
    Use 'show version' or 'show inventory' command to determine the hardware model. For Cisco iOS devices, also run 'show version' to see the iOS version number.
    Affected if The device is a Cisco Cgr1000 Compute Module, Cisco Ic3000 Industrial Compute Gateway, or runs a Cisco iOS version matching 15.2(5)e1, 15.2(5)e2c, 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, or 15.6(1)t3
  2. Verify if IOx is enabled
    Execute 'show iox' or 'show app-hosting' command in privileged exec mode to check the IOx service status.
    Affected if IOx application hosting is listed as 'enabled' or 'active' on the device
  3. Check IOx management interface configuration
    Run 'show running-config | include iox' or 'show app-hosting detail' to inspect IOx-related configuration, including whether the management interface is exposed.
    Affected if IOx management interface is configured and reachable (typically on port 8443 or similar)
  4. Confirm IOx web UI access
    Attempt to access the IOx web interface via https://device-ip:8443/iox or check if the service listens on the management interface using 'show ip interface brief' and port scanning.
    Affected if The IOx web management interface is accessible from any network segment beyond the trusted management network

A device is affected if it is an affected product model or iOS version AND has IOx enabled and its management interface is 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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Cisco-provided security patches for IOx; if patches are unavailable, disable the IOx service and restrict network access to IOx management interfaces.

Recommended fix Moderate confidence

Upgrade to the fixed IOS/IOS-XE version specified in the Cisco security advisory for your product (check tools.cisco.com for exact version numbers)

  1. 1. Identify the specific device model from the affected product list (Cgr1000 Compute Module, Ic3000 Industrial Compute Gateway, or iOS device)
  2. 2. Navigate to Cisco's official security advisory for CVE-2022-20726 on tools.cisco.com
  3. 3. Locate the Fixed Releases section for your specific product to determine the minimum fixed version
  4. 4. Download the appropriate fixed IOS/IOS-XE release from Cisco's software download center
  5. 5. Review release notes for any migration requirements or prerequisites
  6. 6. Back up current device configuration
  7. 7. Upgrade the device to the fixed release following standard Cisco upgrade procedures
  8. 8. Verify the IOx package manager functionality after upgrade
Caveat Review release notes for potential compatibility or configuration changes when upgrading major versions

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

Fix this in Cgr1000 Compute Module Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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