# CVE-2020-3197: Cisco Meetings App Missing TURN Server Credentials Expiration Vulnerability

> An attacker can intercept traffic to steal TURN server credentials, allowing them to place calls and forward packets through the configured server.

- **Severity:** Medium 4.3 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 16 Jul 2020
- **Updated:** 15 Nov 2024
- **Also known as:** GHSA-3jhm-f5jx-jwjj

## What is CVE-2020-3197?

CVE-2020-3197 is a medium-severity vulnerability in Cisco Meeting App, published on 16 Jul 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A vulnerability in the API subsystem of Cisco Meetings App could allow an unauthenticated, remote attacker to retain and reuse the Traversal Using Relay NAT (TURN) server credentials that are configured in an affected system. The vulnerability is due to insufficient protection mechanisms for the TURN server credentials. An attacker could exploit this vulnerability by intercepting the legitimate traffic that is generated by an affected system. An exploit could allow the attacker to obtain the TURN server credentials, which the attacker could use to place audio/video calls and forward packets through the configured TURN server. The attacker would not be able to take control of the TURN server unless the same credentials were used in multiple systems.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2020-3197?

It affects 1 product.


Products: Cisco Meeting Server.

## How do I fix CVE-2020-3197?

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

## Is CVE-2020-3197 being exploited?

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

## Other vulnerabilities in Cisco Meeting App

- [CVE-2016-6448](https://insights.sbomify.com/CVE-2016-6448/): Memory corruption in Cisco Meeting Server before 2.0.3 and Acano Server before 1.9.5 (critical 9.8)
- [CVE-2017-12249](https://insights.sbomify.com/CVE-2017-12249/): Misconfiguration in Cisco Meeting Server (critical 9.1)
- [CVE-2016-6445](https://insights.sbomify.com/CVE-2016-6445/): Auth bypass in Cisco Meeting Server (CMS) before 2.0.6 and Acano Server before 1.8.18 and 1.9.x before 1.9.6 (critical 9.1)
- [CVE-2018-0439](https://insights.sbomify.com/CVE-2018-0439/): Cisco Meeting Server Cross-Site Request Forgery Vulnerability (high 8.8)
- [CVE-2016-6444](https://insights.sbomify.com/CVE-2016-6444/): Cross-site request forgery in Cisco Meeting Server 1.8, 1.9, 2.0 (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-3197 and fix it if it is affected.

What it is: CVE-2020-3197 is a medium-severity vulnerability in Cisco Meeting App, published on 16 Jul 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2020-3197 in the wild and no public exploit code.

Affected product: Cisco Meeting App. 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-2020-3197/ (Markdown: https://insights.sbomify.com/CVE-2020-3197/index.md)
```

## Sources

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

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