# CVE-2021-1372: Information disclosure in Cisco Webex Productivity Tools

> Local authenticated attackers can read sensitive data like tokens from shared memory in Cisco Webex desktop applications.

- **Severity:** Medium 5.5 (`CVSS:3.1/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:** 17 Feb 2021
- **Updated:** 8 Nov 2024
- **Also known as:** GHSA-r5cq-f6p7-hpq4

## What is CVE-2021-1372?

CVE-2021-1372 is a medium-severity vulnerability in Cisco Webex Meetings, published on 17 Feb 2021. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability in Cisco Webex Meetings Desktop App and Webex Productivity Tools for Windows could allow an authenticated, local attacker to gain access to sensitive information on an affected system. This vulnerability is due to the unsafe usage of shared memory by the affected software. An attacker with permissions to view system memory could exploit this vulnerability by running an application on the local system that is designed to read shared memory. A successful exploit could allow the attacker to retrieve sensitive information from the shared memory, including usernames, meeting information, or authentication tokens. Note: To exploit this vulnerability, an attacker must have valid credentials on a Microsoft Windows end-user system and must log in after another user has already authenticated with Webex on the same end-user system.

Weakness: CWE-202 (Exposure of Sensitive Information Through Data Queries)

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

It affects 2 products.


Products: Cisco Webex Meetings, Cisco Webex Meetings Server.

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

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

## Is CVE-2021-1372 being exploited?

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

## Other vulnerabilities in Cisco Webex Meetings

- [CVE-2017-12368](https://insights.sbomify.com/CVE-2017-12368/): Memory corruption in Cisco WebEx Recording Format and Advanced Recording Format Players (critical 9.6)
- [CVE-2017-12369](https://insights.sbomify.com/CVE-2017-12369/): Memory corruption in Cisco WebEx Recording Format and Advanced Recording Format Players (critical 9.6)
- [CVE-2017-12370](https://insights.sbomify.com/CVE-2017-12370/): Memory corruption in Cisco WebEx Recording Format and Advanced Recording Format Players (critical 9.6)
- [CVE-2017-12371](https://insights.sbomify.com/CVE-2017-12371/): Memory corruption in Cisco WebEx Recording Format and Advanced Recording Format Players (critical 9.6)
- [CVE-2017-12372](https://insights.sbomify.com/CVE-2017-12372/): Memory corruption in Cisco WebEx Recording Format and Advanced Recording Format Players (critical 9.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2021-1372 is a medium-severity vulnerability in Cisco Webex Meetings, published on 17 Feb 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-1372 in the wild and no public exploit code.

Affected product: Cisco Webex Meetings. 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-1372/ (Markdown: https://insights.sbomify.com/CVE-2021-1372/index.md)
```

## Sources

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

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