# CVE-2024-37894: Squid vulnerable to heap corruption in ESI assign

> An out-of-bounds write in Squid's ESI variable assignment allows attackers to cause a denial of service via memory corruption.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:N/I:N/A:H`)
- **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:** 25 Jun 2024
- **Updated:** 3 Nov 2025
- **Also known as:** AZL-42871, CLSA-2024-1725012247, CLSA-2024-1725012269, DEBIAN-CVE-2024-37894, DSA-5751-1, GHSA-wgvf-q977-9xjg, MGASA-2024-0265, OESA-2024-1785, RHSA-2024:5906, ROOT-OS-ALPINE-318-CVE-2024-37894, ROOT-OS-ALPINE-320-CVE-2024-37894, SUSE-SU-2024:2268-1, SUSE-SU-2024:2269-1, SUSE-SU-2024:2270-1, UBUNTU-CVE-2024-37894, USN-6907-1, openSUSE-SU-2024:14080-1

## What is CVE-2024-37894?

CVE-2024-37894 is a medium-severity memory corruption vulnerability in Squid-Cache Squid, published on 25 Jun 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Squid is a caching proxy for the Web supporting HTTP, HTTPS, FTP, and more. Due to an Out-of-bounds Write error when assigning ESI variables, Squid is susceptible to a Memory Corruption error. This error can lead to a Denial of Service attack.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2024-37894?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `squid` | Red Hat:rhel_eus:9.2::appstream | All versions | 7:5.5-5.el9_2.7 |
| `squid-debuginfo` | Red Hat:rhel_eus:9.2::appstream | All versions | 7:5.5-5.el9_2.7 |
| `squid-debugsource` | Red Hat:rhel_eus:9.2::appstream | All versions | 7:5.5-5.el9_2.7 |
| `squid` | SUSE:Linux Enterprise Module for Server Applications 15 SP5 | All versions | 5.7-150400.3.32.1 |
| `squid` | SUSE:Linux Enterprise Module for Server Applications 15 SP6 | All versions | 6.10-150600.3.6.1 |
| `squid` | SUSE:Linux Enterprise Server 12 SP5 | All versions | 4.17-4.50.1 |
| `squid` | SUSE:Linux Enterprise Server for SAP Applications 12 SP5 | All versions | 4.17-4.50.1 |
| `squid` | openSUSE:Leap 15.5 | All versions | 5.7-150400.3.32.1 |
| `squid` | openSUSE:Leap 15.6 | All versions | 6.10-150600.3.6.1 |
| `squid` | openSUSE:Tumbleweed | All versions | 6.10-1.1 |

Products: Squid-Cache Squid.

## How do I fix CVE-2024-37894?

Apply the vendor's patch.

## Is CVE-2024-37894 being exploited?

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

## Other vulnerabilities in Squid-Cache Squid

- [CVE-2025-62168](https://insights.sbomify.com/CVE-2025-62168/): Squid vulnerable to information disclosure via authentication credential leakage in error handling (critical 10.0)
- [CVE-2025-54574](https://insights.sbomify.com/CVE-2025-54574/): Squid's URN Handling can lead to Buffer Overflow (critical 9.3)
- [CVE-2026-33526](https://insights.sbomify.com/CVE-2026-33526/): Squid vulnerable to Denial of Service in ICP Request handling (critical 9.2)
- [CVE-2026-32748](https://insights.sbomify.com/CVE-2026-32748/): Squid has Denial of Service in ICP Response handling (high 8.7)
- [CVE-2023-50269](https://insights.sbomify.com/CVE-2023-50269/): SQUID-2023:10 Denial of Service in HTTP Request parsing (high 8.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-37894 and fix it if it is affected.

What it is: CVE-2024-37894 is a medium-severity memory corruption vulnerability in Squid-Cache Squid, published on 25 Jun 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-37894 in the wild and no public exploit code.

Affected product: Squid-Cache Squid. 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-2024-37894/ (Markdown: https://insights.sbomify.com/CVE-2024-37894/index.md)
```

## Sources

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

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