# CVE-2018-0262: Misconfiguration in Cisco Meeting Server

> Incorrect default configuration exposes internal interfaces, allowing remote attackers to access sensitive data and execute code via TURN service exploitation.

- **Severity:** High 8.1 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 May 2018
- **Updated:** 29 Nov 2024
- **Also known as:** GHSA-jr24-4pv3-cjgv

## What is CVE-2018-0262?

CVE-2018-0262 is a high-severity vulnerability in Cisco Meeting Server, published on 2 May 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability in Cisco Meeting Server could allow an unauthenticated, remote attacker to gain unauthorized access to components of, or sensitive information in, an affected system, leading to Remote Code Execution. The vulnerability is due to incorrect default configuration of the device, which can expose internal interfaces and ports on the external interface of the system. A successful exploit could allow the attacker to gain unauthenticated access to configuration and database files as well as sensitive meeting information on an affected system. Additionally, if the Traversal Using Relay NAT (TURN) service is enabled and utilizing Transport Layer Security (TLS) connections, an attacker could utilize TURN credentials to forward traffic to device daemons, allowing for remote exploitation. This vulnerability affects Cisco Meeting Server (CMS) Acano X-series platforms that are running a CMS Software release prior to 2.2.11. Cisco Bug IDs: CSCvg76469.

Weakness: CWE-16

## Which versions are affected by CVE-2018-0262?

It affects 1 product.


Products: Cisco Meeting Server.

## How do I fix CVE-2018-0262?

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

## Is CVE-2018-0262 being exploited?

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

## Other vulnerabilities in Cisco Meeting Server

- [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-2018-0262 and fix it if it is affected.

What it is: CVE-2018-0262 is a high-severity vulnerability in Cisco Meeting Server, published on 2 May 2018. 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-2018-0262 in the wild and no public exploit code.

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

## Sources

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

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