dbcve.org
Ic3000 Industrial Compute GatewayHardware / appliance · Cisco

CVE-2023-20076

HIGH · 8.8 CVSS v3.1 Published 2023-02-12
Fix available
A fix is available. Upgrade to 1.4.2 / 1.10.0.1 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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 Cisco IOx application hosting environment could allow an authenticated, remote attacker to execute arbitrary commands as root on the underlying host operating system. This vulnerability is due to incomplete sanitization of parameters that are passed in for activation of an application. An attacker could exploit this vulnerability by deploying and activating an application in the Cisco IOx application hosting environment with a crafted activation payload file. A successful exploit could allow the attacker to execute arbitrary commands as root on the underlying host operating system.

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 command injection vulnerability in Cisco IOx's application activation process. An authenticated attacker can deploy a malicious application with a crafted activation payload containing shell commands. Due to insufficient parameter sanitization, these commands execute with root privileges on the underlying host OS when the application is activated.

MitigationRestrict IOx application deployment permissions to only trusted, authenticated users and apply Cisco's available patches for this vulnerability. Monitor IOx activity logs for suspicious application deployments.

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
Ic3000 Industrial Compute GatewayHardware / appliance
Affected:< 1.4.2
IoxApplication
Affected:all versions
Ios XeOperating system
Affected:< 17.6.5>= 17.9.0, < 17.9.2= 17.10.0
Cgr1240 FirmwareOperating system
Affected:< 1.16.0.1
Cgr1000 FirmwareOperating system
Affected:< 1.16.0.1
Ir510 Wpan FirmwareOperating system
Affected:< 1.10.0.1
829 Industrial Integrated Services Router FirmwareOperating system
Affected:< 15.9\(3\)= 15.9\(3\)m= 15.9\(3\)m1= 15.9\(3\)m2= 15.9\(3\)m2a= 15.9\(3\)m3= 15.9\(3\)m4= 15.9\(3\)m4a= 15.9\(3\)m5= 15.9\(3\)m6a= 15.9\(3\)m6b
807 Industrial Integrated Services Router FirmwareOperating system
Affected:< 15.9\(3\)= 15.9\(3\)m= 15.9\(3\)m1= 15.9\(3\)m2= 15.9\(3\)m2a= 15.9\(3\)m3= 15.9\(3\)m4= 15.9\(3\)m4a= 15.9\(3\)m5= 15.9\(3\)m6a= 15.9\(3\)m6b

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

CVSS:3.1/AV:N/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 your Cisco product and firmware version
    Run 'show version' or check the device management interface to determine the exact model and firmware/software version. For Ic3000, check the web UI or run 'show iox' if available. For IOS Xe devices, run 'show version' and note the IOS Xe release number.
    Affected if The installed version falls outside the fixed releases: for Ic3000 < 1.4.2 is vulnerable; for IOS Xe < 17.6.5, 17.9.0 to < 17.9.2, or 17.10.0 are vulnerable; for Cgr1240/Cgr1000 < 1.16.0.1 is vulnerable; for Ir510 < 1.10.0.1 is vulnerable; for 829/807 firmware matching any of the listed 15.9(3) vari
  2. Verify if IOx is enabled on the device
    Run the command 'show iox' or 'show iox-server' depending on the platform. For IOS Xe, use 'show iox' to check the IOx service status. For industrial routers, check the configuration with 'show run | include iox' or access the device manager.
    Affected if IOx is not enabled or not configured on the device, the command injection vulnerability cannot be exploited since the attack surface does not exist.
  3. Review IOx application deployment logs
    Check system logs and IOx-specific logs for application deployment events. Use 'show logging' or access the IOx management logs. Look for application activation commands, especially those with unusual or unexpected parameters.
    Affected if There are logs of IOx application deployments with suspicious activation payloads containing shell metacharacters, unexpected commands, or applications from untrusted sources.
  4. Check for unauthorized IOx applications
    Run 'show iox-app' or 'show iox application list' to enumerate deployed IOx applications. Verify each application is expected and from a trusted source.
    Affected if There are IOx applications installed that were not authorized or that contain unexpected activation configurations.
  5. Inspect IOx application configurations
    For each deployed IOx application, review the activation configuration using 'show iox-app detail <app-name>' or by accessing the application manifest. Look for custom scripts or activation parameters that may contain injected commands.
    Affected if Application activation configurations contain shell commands, unusual environment variables, or parameter values that suggest injection attempts.

Your environment is affected if you are running any of the vulnerable product versions listed AND IOx is enabled, because the command injection flaw exists in the IOx activation process which allows authenticated attackers to execute root-privilege commands via malicious application payloads.

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 1.4.2 / 1.10.0.1 / 1.16.0.1 or later
Fixed in 1.4.21.10.0.11.16.0.1
Interim mitigation

Restrict IOx application deployment permissions to only trusted, authenticated users and apply Cisco's available patches for this vulnerability. Monitor IOx activity logs for suspicious application deployments.

Recommended fix Moderate confidence

Device-specific: Ic3000 to 1.4.2+; Cgr1240/Cgr1000 to 1.16.0.1+; Ir510 to 1.10.0.1+; IOS Xe to 17.6.5/17.9.2/17.11+

  1. 1. Identify the exact Cisco IOx-enabled device model from the affected list (Ic3000, Cgr1240, Cgr1000, Ir510, 829 ISR, 807 ISR, or IOS Xe device)
  2. 2. Determine the current firmware/software version running on the device
  3. 3. For Ic3000 Industrial Compute Gateway: Upgrade to version 1.4.2 or later
  4. 4. For Cgr1240 and Cgr1000 Firmware: Upgrade to version 1.16.0.1 or later
  5. 5. For Ir510 Wpan Firmware: Upgrade to version 1.10.0.1 or later
  6. 6. For 829/807 Industrial Integrated Services Router: Upgrade to a version higher than 15.9(3)m2 (Cisco has not specified the exact fixed release in the advisory - contact Cisco TAC)
  7. 7. For IOS Xe: Upgrade to 17.6.5, 17.9.2, or a version higher than 17.10.0 (e.g., 17.11 or later)
  8. 8. After upgrade, verify the IOx application hosting environment functions normally
Caveat Verify compatibility of existing IOx applications with new firmware versions before production deployment; some legacy IOx app configurations may need adjustment

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

Fix this in Ic3000 Industrial Compute Gateway Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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