# CVE-2024-20412: Hardcoded credentials in Cisco Firepower Threat Defense Software

> An unauthenticated local attacker can use hard-coded credentials to access the CLI, retrieve sensitive data, modify configurations, or prevent the device from booting.

- **Severity:** Critical 9.3 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Oct 2024
- **Updated:** 26 Oct 2024
- **Also known as:** GHSA-p38m-32qc-f4cg

## What is CVE-2024-20412?

CVE-2024-20412 is a critical vulnerability in Cisco Secure Firewall Threat Defense, published on 23 Oct 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability in Cisco Firepower Threat Defense (FTD) Software for Cisco Firepower 1000, 2100, 3100, and 4200 Series could allow an unauthenticated, local attacker to access an affected system using static credentials.

 This vulnerability is due to the presence of static accounts with hard-coded passwords on an affected system. An attacker could exploit this vulnerability by logging in to the CLI of an affected device with these credentials. A successful exploit could allow the attacker to access the affected system and retrieve sensitive information, perform limited troubleshooting actions, modify some configuration options, or render the device unable to boot to the operating system, requiring a reimage of the device.

Weakness: CWE-798 (Use of Hard-coded Credentials), CWE-259 (Use of Hard-coded Password)

## Which versions are affected by CVE-2024-20412?

It affects 1 product.


Products: Cisco Secure Firewall Threat Defense.

## How do I fix CVE-2024-20412?

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

## Is CVE-2024-20412 being exploited?

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

## Other vulnerabilities in Cisco Secure Firewall Threat Defense

- [CVE-2024-20330](https://insights.sbomify.com/CVE-2024-20330/): Memory corruption in Cisco Firepower Threat Defense Software (high 8.6)
- [CVE-2024-20339](https://insights.sbomify.com/CVE-2024-20339/): Cisco Firepower Threat Defense Software for Firepower 2100 Series TLS Denial of Service Vulnerability (high 8.6)
- [CVE-2024-20351](https://insights.sbomify.com/CVE-2024-20351/): Cisco Firepower Threat Defense Software Snort Firewall Denial of Service Vulnerability (high 8.6)
- [CVE-2023-20083](https://insights.sbomify.com/CVE-2023-20083/): Denial of service in Cisco Firepower Threat Defense Software (high 8.6)
- [CVE-2023-20244](https://insights.sbomify.com/CVE-2023-20244/): Denial of service in Cisco Firepower Threat Defense Software (high 8.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-20412 and fix it if it is affected.

What it is: CVE-2024-20412 is a critical vulnerability in Cisco Secure Firewall Threat Defense, published on 23 Oct 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-20412 in the wild and no public exploit code.

Affected product: Cisco Secure Firewall Threat Defense. 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-2024-20412/ (Markdown: https://insights.sbomify.com/CVE-2024-20412/index.md)
```

## Sources

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

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