# CVE-2021-34750: Cisco Firepower Management Center Software Configuration Information Disclosure Vulnerability

> An authenticated attacker with low privileges can view sensitive configuration parameters in clear text due to lack of encryption in the Cisco Firepower Management Center GUI.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **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:** 15 Nov 2024
- **Updated:** 15 Nov 2024
- **Also known as:** GHSA-g3v8-p89r-mf62

## What is CVE-2021-34750?

CVE-2021-34750 is a medium-severity vulnerability in Cisco Secure Firewall Management Center, published on 15 Nov 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability in the administrative web-based GUI configuration manager of Cisco Firepower Management Center Software could allow an authenticated, remote attacker to access sensitive configuration information. The attacker would require low privilege credentials on an affected device.
This vulnerability is due to lack of proper encryption of sensitive information stored within the GUI configuration manager. An attacker could exploit this vulnerability by logging into the FMC GUI and navigating to certain sensitive configurations. A successful exploit could allow the attacker to view sensitive configuration parameters in clear text.Cisco has released software updates that address this vulnerability. There are no workarounds that address this vulnerability.[[Publication_URL{Layout()}]]This advisory is part of the October 2021 release of the Cisco ASA, FTD, and FMC Security Advisory Bundled publication. For a complete list of the advisories and links to them, see .

Weakness: CWE-317 (Cleartext Storage of Sensitive Information in GUI)

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

It affects 1 product.


Products: Cisco Secure Firewall Management Center.

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

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

## Is CVE-2021-34750 being exploited?

There is no known exploitation of CVE-2021-34750 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-34750 and fix it if it is affected.

What it is: CVE-2021-34750 is a medium-severity vulnerability in Cisco Secure Firewall Management Center, published on 15 Nov 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-34750 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-34750/ (Markdown: https://insights.sbomify.com/CVE-2021-34750/index.md)
```

## Sources

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

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