# CVE-2024-20457: Cisco Unified Communications Manager IM & Presence Service Information Disclosure Vulnerability

> An authenticated attacker can view unencrypted credentials in logs, potentially gaining access to sensitive information on Cisco Unified CM IM&P systems.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Nov 2024
- **Updated:** 6 Nov 2024
- **Also known as:** GHSA-3c6f-r64x-4f7r

## What is CVE-2024-20457?

CVE-2024-20457 is a medium-severity vulnerability in Cisco Unified Communications Manager IM and Presence Service, published on 6 Nov 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability in the logging component of Cisco Unified Communications Manager IM & Presence Service (Unified CM IM&P) could allow an authenticated, remote attacker to view sensitive information in clear text on an affected system.

This vulnerability is due to the storage of unencrypted credentials in certain logs. An attacker could exploit this vulnerability by accessing the logs on an affected system and obtaining credentials that they may not normally have access to. A successful exploit could allow the attacker to access sensitive information from the device.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Cisco Unified Communications Manager Im and Presence Service.

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

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

## Is CVE-2024-20457 being exploited?

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

## Other vulnerabilities in Cisco Unified Communications Manager IM and Presence Service

- [CVE-2018-0363](https://insights.sbomify.com/CVE-2018-0363/): Cross-site request forgery in Cisco Unified Communications Manager IM & Presence Service unknown (high 8.8)
- [CVE-2023-20108](https://insights.sbomify.com/CVE-2023-20108/): Denial of service in Cisco Unified Communications Manager IM and Presence Service (high 7.5)
- [CVE-2016-6464](https://insights.sbomify.com/CVE-2016-6464/): Information disclosure in Cisco Unified Communications Manager (high 7.5)
- [CVE-2016-1466](https://insights.sbomify.com/CVE-2016-1466/): Denial of service in n/a (high 7.5)
- [CVE-2021-1363](https://insights.sbomify.com/CVE-2021-1363/): Cisco Unified Communications Manager IM & Presence Service SQL Injection Vulnerabilities (high 7.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-20457 is a medium-severity vulnerability in Cisco Unified Communications Manager IM and Presence Service, published on 6 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-2024-20457 in the wild and no public exploit code.

Affected product: Cisco Unified Communications Manager IM and Presence Service. 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-20457/ (Markdown: https://insights.sbomify.com/CVE-2024-20457/index.md)
```

## Sources

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

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