# CVE-2022-20829: Code injection in Cisco Adaptive Security Appliance (ASA) Software

> An authenticated admin can upload a malicious ASDM image to execute arbitrary code on the client machine of a targeted user.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Jun 2022
- **Updated:** 1 Nov 2024
- **Also known as:** GHSA-qq3x-ppcw-6fmq

## What is CVE-2022-20829?

CVE-2022-20829 is a critical code injection vulnerability in Cisco Adaptive Security Appliance (ASA) Software, published on 24 Jun 2022. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A vulnerability in the packaging of Cisco Adaptive Security Device Manager (ASDM) images and the validation of those images by Cisco Adaptive Security Appliance (ASA) Software could allow an authenticated, remote attacker with administrative privileges to upload an ASDM image that contains malicious code to a device that is running Cisco ASA Software. This vulnerability is due to insufficient validation of the authenticity of an ASDM image during its installation on a device that is running Cisco ASA Software. An attacker could exploit this vulnerability by installing a crafted ASDM image on the device that is running Cisco ASA Software and then waiting for a targeted user to access that device using ASDM. A successful exploit could allow the attacker to execute arbitrary code on the machine of the targeted user with the privileges of that user on that machine. Notes: To successfully exploit this vulnerability, the attacker must have administrative privileges on the device that is running Cisco ASA Software. Potential targets are limited to users who manage the same device that is running Cisco ASA Software using ASDM. Cisco has released and will release software updates that address this vulnerability.

Weakness: CWE-345 (Insufficient Verification of Data Authenticity)

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

It affects 5 products.


Products: Cisco Adaptive Security Device Manager, Cisco Asa 5512-X Firmware, Cisco Asa 5515-X Firmware, Cisco Asa 5585-X Firmware, Cisco Isa 3000 Firmware.

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

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

## Is CVE-2022-20829 being exploited?

There is no known exploitation of CVE-2022-20829 in the wild and no public exploit code.

Public exploit code:

- A tool for extracting, modifying, and crafting ASDM binary packages (CVE-2022-20829) (github_poc): https://github.com/jbaines-r7/theway

## Other vulnerabilities in Cisco Adaptive Security Appliance (ASA) Software

- [CVE-2021-1585](https://insights.sbomify.com/CVE-2021-1585/): Cisco Adaptive Security Device Manager Remote Code Execution Vulnerability (high 7.5)
- [CVE-2022-20651](https://insights.sbomify.com/CVE-2022-20651/): Cisco Adaptive Security Device Manager Information Disclosure Vulnerability (medium 5.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-20829 is a critical code injection vulnerability in Cisco Adaptive Security Appliance (ASA) Software, published on 24 Jun 2022. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-20829 in the wild and no public exploit code.

Affected product: Cisco Adaptive Security Appliance (ASA) Software. 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-20829/ (Markdown: https://insights.sbomify.com/CVE-2022-20829/index.md)
```

## Sources

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

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