# CVE-2016-9037: Memory corruption in Tarantool

> An attacker can cause a denial of service in Tarantool by sending a specially crafted packet that triggers an out-of-bounds read.

- **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:** Yes
- **Published:** 23 Dec 2016
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2016-9037, GHSA-84pj-3xv4-7g42, UBUNTU-CVE-2016-9037

## What is CVE-2016-9037?

CVE-2016-9037 is a high-severity memory corruption vulnerability in Tarantool, published on 23 Dec 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An exploitable out-of-bounds array access vulnerability exists in the xrow_header_decode function of Tarantool 1.7.2.0-g8e92715. A specially crafted packet can cause the function to access an element outside the bounds of a global array that is used to determine the type of the specified key's value. This can lead to an out of bounds read within the context of the server. An attacker who exploits this vulnerability can cause a denial of service vulnerability on the server.

Weakness: CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2016-9037?

It affects 1 product.


Products: Tarantool Tarantool.

## How do I fix CVE-2016-9037?

Upgrade to a fixed version.

## Is CVE-2016-9037 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-9037 and fix it if it is affected.

What it is: CVE-2016-9037 is a high-severity memory corruption vulnerability in Tarantool, published on 23 Dec 2016. 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-2016-9037 in the wild and no public exploit code.

Affected product: Tarantool. 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-2016-9037/ (Markdown: https://insights.sbomify.com/CVE-2016-9037/index.md)
```

## Sources

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

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