# CVE-2017-8290: Memory corruption in n/a

> A buffer overflow in TeamSpeak Server allows attackers to crash Windows clients by directing them to a vulnerable channel.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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:** 6 Jul 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-4qw9-g2c3-wj63

## What is CVE-2017-8290?

CVE-2017-8290 is a high-severity memory corruption vulnerability in n/a, published on 6 Jul 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A potential Buffer Overflow Vulnerability (from a BB Code handling issue) has been identified in TeamSpeak Server version 3.0.13.6 (08/11/2016 09:48:33), it enables the users to Crash any WINDOWS Client that clicked into a Vulnerable Channel of a TeamSpeak Server.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2017-8290?

It affects 2 products.


Products: Teamspeak Teamspeak Client, Teamspeak Teamspeak Server.

## How do I fix CVE-2017-8290?

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

## Is CVE-2017-8290 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-9982](https://insights.sbomify.com/CVE-2017-9982/): Denial of service in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-8290 and fix it if it is affected.

What it is: CVE-2017-8290 is a high-severity memory corruption vulnerability in n/a, published on 6 Jul 2017. 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-2017-8290 in the wild and no public exploit code.

Affected product: n/a. 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-2017-8290/ (Markdown: https://insights.sbomify.com/CVE-2017-8290/index.md)
```

## Sources

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

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