# CVE-2023-20107: Cisco Adaptive Security Appliance Software and Firepower Threat Defense Software Low-Entropy Keys Vulnerability

> Insufficient entropy in key generation allows attackers to discover private keys, enabling traffic decryption and device impersonation on Cisco ASA and FTD firewalls.

- **Severity:** Medium 5.3 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Mar 2023
- **Updated:** 28 Oct 2024
- **Also known as:** GHSA-p33m-2g5r-vx6v

## What is CVE-2023-20107?

CVE-2023-20107 is a medium-severity vulnerability in Cisco Adaptive Security Appliance, published on 23 Mar 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability in the deterministic random bit generator (DRBG), also known as pseudorandom number generator (PRNG), in Cisco Adaptive Security Appliance (ASA) Software and Cisco Firepower Threat Defense (FTD) Software for Cisco ASA 5506-X, ASA 5508-X, and ASA 5516-X Firewalls could allow an unauthenticated, remote attacker to cause a cryptographic collision, enabling the attacker to discover the private key of an affected device. This vulnerability is due to insufficient entropy in the DRBG for the affected hardware platforms when generating cryptographic keys. An attacker could exploit this vulnerability by generating a large number of cryptographic keys on an affected device and looking for collisions with target devices. A successful exploit could allow the attacker to impersonate an affected target device or to decrypt traffic secured by an affected key that is sent to or from an affected target device.

Weakness: CWE-331 (Insufficient Entropy), CWE-332 (Insufficient Entropy in PRNG)

## Which versions are affected by CVE-2023-20107?

It affects 2 products.


Products: Cisco Adaptive Security Appliance, Cisco Secure Firewall Threat Defense.

## How do I fix CVE-2023-20107?

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

## Is CVE-2023-20107 being exploited?

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

## Other vulnerabilities in Cisco Adaptive Security Appliance

- [CVE-2021-1573](https://insights.sbomify.com/CVE-2021-1573/): Denial of service in Cisco Adaptive Security Appliance Software (high 8.6)
- [CVE-2021-34793](https://insights.sbomify.com/CVE-2021-34793/): Denial of service in Cisco Adaptive Security Appliance (ASA) Software (high 8.6)
- [CVE-2021-40117](https://insights.sbomify.com/CVE-2021-40117/): Denial of service in Cisco Adaptive Security Appliance (ASA) Software (high 8.6)
- [CVE-2021-40118](https://insights.sbomify.com/CVE-2021-40118/): Denial of service in Cisco Adaptive Security Appliance (ASA) Software (high 8.6)
- [CVE-2020-3304](https://insights.sbomify.com/CVE-2020-3304/): Denial of service in Cisco Adaptive Security Appliance (ASA) Software (high 8.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-20107 and fix it if it is affected.

What it is: CVE-2023-20107 is a medium-severity vulnerability in Cisco Adaptive Security Appliance, published on 23 Mar 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-20107 in the wild and no public exploit code.

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

## Sources

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

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