# CVE-2022-20964: Command injection in Cisco Identity Services Engine Software

> Authenticated attackers can inject arbitrary OS commands via the web interface, leading to code execution with web service privileges.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Jan 2023
- **Updated:** 21 Nov 2024
- **Also known as:** GHSA-fvm6-h6r9-qcr2

## What is CVE-2022-20964?

CVE-2022-20964 is a medium-severity command injection vulnerability in Cisco Identity Services Engine, published on 18 Jan 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability in the web-based management interface of Cisco Identity Services Engine could allow an authenticated, remote attacker to inject arbitrary commands on the underlying operating system.

 This vulnerability is due to improper validation of user input within requests as part of the web-based management interface. An attacker could exploit this vulnerability by manipulating requests to the web-based management interface to contain operating system commands. A successful exploit could allow the attacker to execute arbitrary operating system commands on the underlying operating system with the privileges of the web services user.

 Cisco has not yet released software updates that address this vulnerability.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2022-20964?

It affects 1 product.


Products: Cisco Identity Services Engine.

## How do I fix CVE-2022-20964?

No fix has been published for CVE-2022-20964 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-20964 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-20964 exists.

## Other vulnerabilities in Cisco Identity Services Engine

- [CVE-2026-76460](https://insights.sbomify.com/CVE-2026-76460/): Cisco Identity Services Engine Incorrect Use of Privileged APIs (critical 10.0, exploited in the wild)
- [CVE-2025-20337](https://insights.sbomify.com/CVE-2025-20337/): Cisco Identity Services Engine Injection (critical 10.0, exploited in the wild)
- [CVE-2025-20281](https://insights.sbomify.com/CVE-2025-20281/): Cisco Identity Services Engine Injection (critical 10.0, exploited in the wild)
- [CVE-2026-20130](https://insights.sbomify.com/CVE-2026-20130/): Cisco Identity Services Engine Hardening Release - Improper Neutralization Vulnerabilities (critical 10.0)
- [CVE-2026-20192](https://insights.sbomify.com/CVE-2026-20192/): Cisco Identity Services Engine Hardening Release - Access Control Vulnerabilities (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-20964 and fix it if it is affected.

What it is: CVE-2022-20964 is a medium-severity command injection vulnerability in Cisco Identity Services Engine, published on 18 Jan 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-20964 exists.

Affected product: Cisco Identity Services Engine. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-20964/ (Markdown: https://insights.sbomify.com/CVE-2022-20964/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-20964
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-20964
- OSV: https://osv.dev/vulnerability/CVE-2022-20964

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-20964/
Summaries are generated and may contain mistakes; the official description above is the record.