# CVE-2024-20491: Cisco Nexus Dashboard Insights Information Disclosure Vulnerability

> An attacker with access to a tech support file can view remote controller admin credentials in clear text, potentially leading to account takeover.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 2 Oct 2024
- **Updated:** 2 Oct 2024
- **Also known as:** GHSA-xxc2-9vrh-pfjm

## What is CVE-2024-20491?

CVE-2024-20491 is a medium-severity vulnerability in Cisco Nexus Dashboard Insights, published on 2 Oct 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

A vulnerability in a logging function of Cisco Nexus Dashboard Insights could allow an attacker with access to a tech support file to view sensitive information.

This vulnerability exists because remote controller credentials are recorded in an internal log that is stored in the tech support file. An attacker could exploit this vulnerability by accessing a tech support file that is generated from an affected system. A successful exploit could allow the attacker to view remote controller admin credentials in clear text.
Note: Best practice is to store debug logs and tech support files safely and to share them only with trusted parties because they may contain sensitive information.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 3 products.


Products: Cisco Nexus Dashboard Fabric Controller, Cisco Nexus Dashboard Insights, Cisco Nexus Dashboard Orchestrator.

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

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

## Is CVE-2024-20491 being exploited?

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

## Other vulnerabilities in Cisco Nexus Dashboard Insights

- [CVE-2024-20432](https://insights.sbomify.com/CVE-2024-20432/): Cisco Nexus Dashboard Fabric Controller Web UI Command Injection Vulnerability (critical 9.9)
- [CVE-2024-20536](https://insights.sbomify.com/CVE-2024-20536/): Cisco Nexus Dashboard Fabric Controller SQL Injection Vulnerability (high 8.8)
- [CVE-2024-20449](https://insights.sbomify.com/CVE-2024-20449/): Cisco Nexus Dashboard Fabric Controller Remote Code Execution Vulnerability (high 8.8)
- [CVE-2024-20348](https://insights.sbomify.com/CVE-2024-20348/): Path traversal in Cisco Data Center Network Manager (high 7.5)
- [CVE-2024-20448](https://insights.sbomify.com/CVE-2024-20448/): Cisco Nexus Dashboard Fabric Controller Credential Information Disclosure Vulnerability (medium 6.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-20491 is a medium-severity vulnerability in Cisco Nexus Dashboard Insights, published on 2 Oct 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-20491 in the wild and no public exploit code.

Affected product: Cisco Nexus Dashboard Insights. 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-20491/ (Markdown: https://insights.sbomify.com/CVE-2024-20491/index.md)
```

## Sources

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

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