# CVE-2014-9351: engine/server/server.cpp in Teeworlds 0.6.x before 0.6.3 allows remote attackers to read memory and cause a denial of service (crash) via unspecified vectors.


- **Severity:** Medium 6.4 (`AV:N/AC:L/Au:N/C:P/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 9 Dec 2014
- **Updated:** 17 Sep 2024
- **Also known as:** DEBIAN-CVE-2014-9351, GHSA-67qr-qj94-6wp3, UBUNTU-CVE-2014-9351

## What is CVE-2014-9351?

CVE-2014-9351 is a medium-severity vulnerability in n/a, published on 9 Dec 2014. 

### Official description

engine/server/server.cpp in Teeworlds 0.6.x before 0.6.3 allows remote attackers to read memory and cause a denial of service (crash) via unspecified vectors.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2014-9351?

It affects 1 product.


Products: Teeworlds Teeworlds.

## How do I fix CVE-2014-9351?

Upgrade to a fixed version.

## Is CVE-2014-9351 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-10877](https://insights.sbomify.com/CVE-2019-10877/): Integer overflow in n/a (critical 9.8)
- [CVE-2019-10878](https://insights.sbomify.com/CVE-2019-10878/): Memory corruption in n/a (critical 9.8)
- [CVE-2019-10879](https://insights.sbomify.com/CVE-2019-10879/): Integer overflow in n/a (critical 9.8)
- [CVE-2023-31517](https://insights.sbomify.com/CVE-2023-31517/): Denial of service in n/a (high 7.5)
- [CVE-2023-31518](https://insights.sbomify.com/CVE-2023-31518/): Use after free in n/a (medium 5.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-9351 and fix it if it is affected.

What it is: CVE-2014-9351 is a medium-severity vulnerability in n/a, published on 9 Dec 2014. 
Exploitation: There is no known exploitation of CVE-2014-9351 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-2014-9351/ (Markdown: https://insights.sbomify.com/CVE-2014-9351/index.md)
```

## Sources

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

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