# CVE-2021-1126: Cisco Firepower Management Center Information Disclosure Vulnerability

> An authenticated local attacker can view proxy server credentials stored in clear text within configuration files on Cisco Firepower Management Center.

- **Severity:** Medium 5.5 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Jan 2021
- **Updated:** 12 Nov 2024
- **Also known as:** GHSA-p733-729j-99xq

## What is CVE-2021-1126?

CVE-2021-1126 is a medium-severity vulnerability in Cisco Secure Firewall Management Center, published on 13 Jan 2021. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability in the storage of proxy server credentials of Cisco Firepower Management Center (FMC) could allow an authenticated, local attacker to view credentials for a configured proxy server. The vulnerability is due to clear-text storage and weak permissions of related configuration files. An attacker could exploit this vulnerability by accessing the CLI of the affected software and viewing the contents of the affected files. A successful exploit could allow the attacker to view the credentials that are used to access the proxy server.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource), CWE-522 (Insufficiently Protected Credentials), CWE-256 (Plaintext Storage of a Password)

## Which versions are affected by CVE-2021-1126?

It affects 1 product.


Products: Cisco Secure Firewall Management Center.

## How do I fix CVE-2021-1126?

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

## Is CVE-2021-1126 being exploited?

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

## Other vulnerabilities in Cisco Secure Firewall Management Center

- [CVE-2026-20079](https://insights.sbomify.com/CVE-2026-20079/): Cisco Firewall Management Center Authentication Bypass Using an Alternate Path or Channel (critical 10.0, exploited in the wild)
- [CVE-2026-20131](https://insights.sbomify.com/CVE-2026-20131/): Cisco Secure Firewall Management Center (FMC) Software and Cisco Security Cloud Control (SCC) Firewall Management Deserialization of Untrusted Data (critical 10.0, exploited in the wild)
- [CVE-2026-20316](https://insights.sbomify.com/CVE-2026-20316/): Cisco Secure Firewall Management Center Use of Hard-coded Password (medium 5.3, exploited in the wild)
- [CVE-2025-20265](https://insights.sbomify.com/CVE-2025-20265/): Cisco Secure Firewall Management Center Software Radius Remote Code Execution Vulnerability (critical 10.0)
- [CVE-2024-20424](https://insights.sbomify.com/CVE-2024-20424/): Command injection in Cisco Firepower Management Center (critical 9.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-1126 and fix it if it is affected.

What it is: CVE-2021-1126 is a medium-severity vulnerability in Cisco Secure Firewall Management Center, published on 13 Jan 2021. 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-2021-1126 in the wild and no public exploit code.

Affected product: Cisco Secure Firewall Management Center. 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-2021-1126/ (Markdown: https://insights.sbomify.com/CVE-2021-1126/index.md)
```

## Sources

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

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