# CVE-2022-20918: Hardcoded credentials in Cisco FirePOWER Services Software for ASA

> An unauthenticated remote attacker can retrieve sensitive information from Cisco Firepower devices using default SNMP credentials if SNMP is enabled.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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:** 10 Nov 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-2cx7-566f-cvrr

## What is CVE-2022-20918?

CVE-2022-20918 is a high-severity vulnerability in Cisco Secure Firewall Management Center, published on 10 Nov 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability in the Simple Network Management Protocol (SNMP) access controls for Cisco FirePOWER Software for Adaptive Security Appliance (ASA) FirePOWER module, Cisco Firepower Management Center (FMC) Software, and Cisco Next-Generation Intrusion Prevention System (NGIPS) Software could allow an unauthenticated, remote attacker to perform an SNMP GET request using a default credential.

 This vulnerability is due to the presence of a default credential for SNMP version 1 (SNMPv1) and SNMP version 2 (SNMPv2). An attacker could exploit this vulnerability by sending an SNMPv1 or SNMPv2 GET request to an affected device. A successful exploit could allow the attacker to retrieve sensitive information from the device using the default credential.

 This attack will only be successful if SNMP is configured, and the attacker can only perform SNMP GET requests; write access using SNMP is not allowed.

Weakness: CWE-287 (Improper Authentication), CWE-284 (Improper Access Control)

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

It affects 2 products.


Products: Cisco Firepower Services Software for Asa, Cisco Secure Firewall Management Center.

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

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

## Is CVE-2022-20918 being exploited?

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

## Other vulnerabilities in Cisco Secure Firewall Management Center

- [CVE-2019-1978](https://insights.sbomify.com/CVE-2019-1978/): Cisco Firepower Threat Defense Software Stream Reassembly Bypass Vulnerability (medium 5.8)
- [CVE-2019-1980](https://insights.sbomify.com/CVE-2019-1980/): Cisco Firepower Threat Defense Software Nonstandard Protocol Detection Bypass Vulnerability (medium 5.8)
- [CVE-2019-1981](https://insights.sbomify.com/CVE-2019-1981/): Cisco Firepower Threat Defense Software NULL Character Obfuscation Detection Bypass Vulnerability (medium 5.8)
- [CVE-2019-1982](https://insights.sbomify.com/CVE-2019-1982/): Cisco Firepower Threat Defense Software HTTP Filtering Bypass Vulnerability (medium 5.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-20918 is a high-severity vulnerability in Cisco Secure Firewall Management Center, published on 10 Nov 2022. 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-2022-20918 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-2022-20918/ (Markdown: https://insights.sbomify.com/CVE-2022-20918/index.md)
```

## Sources

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

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