# CVE-2018-21245: Other in n/a

> Attackers can exploit HTTP request smuggling in Pound to bypass security controls or access sensitive data.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Jun 2020
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2018-21245, GHSA-r344-4jmp-54g4, UBUNTU-CVE-2018-21245

## What is CVE-2018-21245?

CVE-2018-21245 is a critical vulnerability in n/a, published on 15 Jun 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Pound before 2.8 allows HTTP request smuggling, a related issue to CVE-2016-10711.

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

## Which versions are affected by CVE-2018-21245?

It affects 1 product.


Products: Apsis Pound.

## How do I fix CVE-2018-21245?

Upgrade to a fixed version.

## Is CVE-2018-21245 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2016-10711](https://insights.sbomify.com/CVE-2016-10711/): Other in n/a (critical 9.8)
- [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-2018-21245 and fix it if it is affected.

What it is: CVE-2018-21245 is a critical vulnerability in n/a, published on 15 Jun 2020. 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-2018-21245 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-2018-21245/ (Markdown: https://insights.sbomify.com/CVE-2018-21245/index.md)
```

## Sources

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

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