# CVE-2019-16200: Integer overflow in n/a

> An integer overflow in GNU Serveez allows attackers to trigger a heap-based buffer over-read via crafted HTTP POST requests, leading to information disclosure.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Nov 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-37cx-2gj4-qw8v

## What is CVE-2019-16200?

CVE-2019-16200 is a high-severity vulnerability in n/a, published on 20 Nov 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

GNU Serveez through 0.2.2 has an Information Leak. An attacker may send an HTTP POST request to the /cgi-bin/reader URI. The attacker must include a Content-length header with a large positive value that, when represented in 32 bit binary, evaluates to a negative number. The problem exists in the http_cgi_write function under http-cgi.c; however, exploitation might show svz_envblock_add in libserveez/passthrough.c as the location of the heap-based buffer over-read.

Weakness: CWE-681 (Incorrect Conversion between Numeric Types)

## Which versions are affected by CVE-2019-16200?

It affects 1 product.


Products: Gnu Serveez.

## How do I fix CVE-2019-16200?

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

## Is CVE-2019-16200 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-16200 and fix it if it is affected.

What it is: CVE-2019-16200 is a high-severity vulnerability in n/a, published on 20 Nov 2019. 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-2019-16200 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-2019-16200/ (Markdown: https://insights.sbomify.com/CVE-2019-16200/index.md)
```

## Sources

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

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