# CVE-2020-15049: Other in n/a

> Attackers can perform HTTP request smuggling and cache poisoning by manipulating Content-Length headers, affecting Squid proxy users.

- **Severity:** Critical 9.9 (`CVSS:3.1/AC:L/AV:N/A:H/C:H/I:H/PR:L/S:C/UI:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 30 Jun 2020
- **Updated:** 4 Aug 2024
- **Also known as:** ALPINE-CVE-2020-15049, DEBIAN-CVE-2020-15049, GHSA-qf3v-rc95-96j5, SUSE-SU-2020:1946-1, UBUNTU-CVE-2020-15049

## What is CVE-2020-15049?

CVE-2020-15049 is a critical vulnerability in Fedoraproject Fedora, published on 30 Jun 2020. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An issue was discovered in http/ContentLengthInterpreter.cc in Squid before 4.12 and 5.x before 5.0.3. A Request Smuggling and Poisoning attack can succeed against the HTTP cache. The client sends an HTTP request with a Content-Length header containing "+\ "-" or an uncommon shell whitespace character prefix to the length field-value.

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

## Which versions are affected by CVE-2020-15049?

It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `squid` | SUSE:Enterprise Storage 5 | All versions | 3.5.21-26.29.1 |
| `squid` | SUSE:HPE Helion OpenStack 8 | All versions | 3.5.21-26.29.1 |
| `squid` | SUSE:Linux Enterprise Server 12 SP2-BCL | All versions | 3.5.21-26.29.1 |
| `squid` | SUSE:Linux Enterprise Server 12 SP2-LTSS | All versions | 3.5.21-26.29.1 |
| `squid` | SUSE:Linux Enterprise Server 12 SP3-BCL | All versions | 3.5.21-26.29.1 |
| `squid` | SUSE:Linux Enterprise Server 12 SP3-LTSS | All versions | 3.5.21-26.29.1 |
| `squid` | SUSE:Linux Enterprise Server 12 SP4-LTSS | All versions | 3.5.21-26.29.1 |
| `squid` | SUSE:Linux Enterprise Server for SAP Applications 12 SP2 | All versions | 3.5.21-26.29.1 |
| `squid` | SUSE:Linux Enterprise Server for SAP Applications 12 SP3 | All versions | 3.5.21-26.29.1 |
| `squid` | SUSE:Linux Enterprise Server for SAP Applications 12 SP4 | All versions | 3.5.21-26.29.1 |
| `squid` | SUSE:OpenStack Cloud 7 | All versions | 3.5.21-26.29.1 |
| `squid` | SUSE:OpenStack Cloud 8 | All versions | 3.5.21-26.29.1 |
| `squid` | SUSE:OpenStack Cloud 9 | All versions | 3.5.21-26.29.1 |
| `squid` | SUSE:OpenStack Cloud Crowbar 8 | All versions | 3.5.21-26.29.1 |
| `squid` | SUSE:OpenStack Cloud Crowbar 9 | All versions | 3.5.21-26.29.1 |

Products: Fedoraproject Fedora, Squid-Cache Squid.

## How do I fix CVE-2020-15049?

Upgrade to a fixed version.

## Is CVE-2020-15049 being exploited?

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

## Other vulnerabilities in Fedoraproject Fedora

- [CVE-2024-4577](https://insights.sbomify.com/CVE-2024-4577/): PHP-CGI OS Command Injection (critical 9.8, exploited in the wild)
- [CVE-2021-39226](https://insights.sbomify.com/CVE-2021-39226/): Grafana Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2019-5544](https://insights.sbomify.com/CVE-2019-5544/): VMware ESXi and Horizon DaaS OpenSLP Heap-Based Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2024-4947](https://insights.sbomify.com/CVE-2024-4947/): Google Chromium V8 Type Confusion (critical 9.6, exploited in the wild)
- [CVE-2024-4671](https://insights.sbomify.com/CVE-2024-4671/): Google Chromium Visuals Use-After-Free (critical 9.6, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-15049 and fix it if it is affected.

What it is: CVE-2020-15049 is a critical vulnerability in Fedoraproject Fedora, published on 30 Jun 2020. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-15049 in the wild and no public exploit code.

Affected product: Fedoraproject Fedora. 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-2020-15049/ (Markdown: https://insights.sbomify.com/CVE-2020-15049/index.md)
```

## Sources

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

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