# CVE-2016-10711: Other in n/a

> Attackers can perform request smuggling via crafted headers in Pound reverse proxy, potentially bypassing security controls.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/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:** Yes
- **Published:** 29 Jan 2018
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2016-10711, DLA-1280-1, DLA-2196-1, GHSA-v3w2-x73g-vf6m, UBUNTU-CVE-2016-10711

## What is CVE-2016-10711?

CVE-2016-10711 is a critical vulnerability in Debian Debian Linux, published on 29 Jan 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Apsis Pound before 2.8a allows request smuggling via crafted headers, a different vulnerability than CVE-2005-3751.

Weakness: CWE-444 (Inconsistent Interpretation of HTTP Requests)

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

It affects 2 products.


Products: Apsis Pound, Debian Debian Linux.

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

Upgrade to a fixed version.

## Is CVE-2016-10711 being exploited?

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

## Other vulnerabilities in Debian Debian Linux

- [CVE-2018-21245](https://insights.sbomify.com/CVE-2018-21245/): Other in n/a (critical 9.1)
- [CVE-2004-2026](https://insights.sbomify.com/CVE-2004-2026/): Other in n/a (high 7.5)
- [CVE-2005-1391](https://insights.sbomify.com/CVE-2005-1391/): Memory corruption in n/a (high 7.5)
- [CVE-2005-3751](https://insights.sbomify.com/CVE-2005-3751/): Other in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2016-10711 is a critical vulnerability in Debian Debian Linux, published on 29 Jan 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-2016-10711 in the wild and no public exploit code.

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

## Sources

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

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