# CVE-2024-45802: Squid Denial of Service

> A trusted server can cause a denial of service against all clients using the Squid proxy due to input validation and resource management flaws.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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:** 28 Oct 2024
- **Updated:** 3 Nov 2025
- **Also known as:** ALSA-2024:9625, AZL-51819, CLSA-2024-1732699822, CLSA-2024-1732701268, CLSA-2024-1732701755, CLSA-2024-1732702046, CLSA-2024-1732702216, CLSA-2024-1732702350, CLSA-2024-1732703448, CLSA-2024-1732704094, CLSA-2024-1733141124, CLSA-2026-1777389615, DEBIAN-CVE-2024-45802, GHSA-f975-v7qw-q7hj, OESA-2024-2309, RHSA-2024:9624, RHSA-2024:9625, RHSA-2024:9677, RHSA-2024:9678, RHSA-2024:9729, RHSA-2024:9738, RHSA-2024:9813, RHSA-2024:9814, RHSA-2024:9815, RLSA-2024:9625, UBUNTU-CVE-2024-45802, openSUSE-SU-2024:14566-1

## What is CVE-2024-45802?

CVE-2024-45802 is a high-severity denial of service vulnerability in Squid-Cache Squid, published on 28 Oct 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Squid is an open source caching proxy for the Web supporting HTTP, HTTPS, FTP, and more. Due to Input Validation, Premature Release of Resource During Expected Lifetime, and Missing Release of Resource after Effective Lifetime bugs, Squid is vulnerable to Denial of Service attacks by a trusted server against all clients using the proxy. This bug is fixed in the default build configuration of Squid version 6.10.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `squid` | AlmaLinux:9 | All versions | 7:5.5-14.el9_5.3 |
| `squid` | Red Hat:enterprise_linux:9::appstream | All versions | 7:5.5-14.el9_5.3 |
| `squid-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 7:5.5-14.el9_5.3 |
| `squid-debugsource` | Red Hat:enterprise_linux:9::appstream | All versions | 7:5.5-14.el9_5.3 |
| `libecap` | Red Hat:rhel_aus:8.2::appstream | All versions | 0:1.0.1-2.module+el8.1.0+4044+36416a77 |
| `libecap-debuginfo` | Red Hat:rhel_aus:8.2::appstream | All versions | 0:1.0.1-2.module+el8.1.0+4044+36416a77 |
| `libecap-debugsource` | Red Hat:rhel_aus:8.2::appstream | All versions | 0:1.0.1-2.module+el8.1.0+4044+36416a77 |
| `libecap-devel` | Red Hat:rhel_aus:8.2::appstream | All versions | 0:1.0.1-2.module+el8.1.0+4044+36416a77 |
| `squid` | Red Hat:rhel_aus:8.2::appstream | All versions | 7:4.4-8.module+el8.2.0+22482+3b9510d6.10 |
| `squid-debuginfo` | Red Hat:rhel_aus:8.2::appstream | All versions | 7:4.4-8.module+el8.2.0+22482+3b9510d6.10 |
| `squid-debugsource` | Red Hat:rhel_aus:8.2::appstream | All versions | 7:4.4-8.module+el8.2.0+22482+3b9510d6.10 |
| `libecap` | Red Hat:rhel_aus:8.4::appstream | All versions | 0:1.0.1-2.module+el8.1.0+4044+36416a77 |
| `libecap-debuginfo` | Red Hat:rhel_aus:8.4::appstream | All versions | 0:1.0.1-2.module+el8.1.0+4044+36416a77 |
| `libecap-debugsource` | Red Hat:rhel_aus:8.4::appstream | All versions | 0:1.0.1-2.module+el8.1.0+4044+36416a77 |
| `libecap-devel` | Red Hat:rhel_aus:8.4::appstream | All versions | 0:1.0.1-2.module+el8.1.0+4044+36416a77 |
| `squid` | Red Hat:rhel_aus:8.4::appstream | All versions | 7:4.11-4.module+el8.4.0+22483+0c92772a.9 |
| `squid-debuginfo` | Red Hat:rhel_aus:8.4::appstream | All versions | 7:4.11-4.module+el8.4.0+22483+0c92772a.9 |
| `squid-debugsource` | Red Hat:rhel_aus:8.4::appstream | All versions | 7:4.11-4.module+el8.4.0+22483+0c92772a.9 |
| `libecap` | Red Hat:rhel_aus:8.6::appstream | All versions | 0:1.0.1-2.module+el8.1.0+4044+36416a77 |
| `libecap-debuginfo` | Red Hat:rhel_aus:8.6::appstream | All versions | 0:1.0.1-2.module+el8.1.0+4044+36416a77 |
| `libecap-debugsource` | Red Hat:rhel_aus:8.6::appstream | All versions | 0:1.0.1-2.module+el8.1.0+4044+36416a77 |
| `libecap-devel` | Red Hat:rhel_aus:8.6::appstream | All versions | 0:1.0.1-2.module+el8.1.0+4044+36416a77 |
| `squid` | Red Hat:rhel_aus:8.6::appstream | All versions | 7:4.15-3.module+el8.6.0+22491+132fca59.7 |
| `squid-debuginfo` | Red Hat:rhel_aus:8.6::appstream | All versions | 7:4.15-3.module+el8.6.0+22491+132fca59.7 |
| `squid-debugsource` | Red Hat:rhel_aus:8.6::appstream | All versions | 7:4.15-3.module+el8.6.0+22491+132fca59.7 |
| `libecap` | Red Hat:rhel_e4s:8.4::appstream | All versions | 0:1.0.1-2.module+el8.1.0+4044+36416a77 |
| `libecap-debuginfo` | Red Hat:rhel_e4s:8.4::appstream | All versions | 0:1.0.1-2.module+el8.1.0+4044+36416a77 |
| `libecap-debugsource` | Red Hat:rhel_e4s:8.4::appstream | All versions | 0:1.0.1-2.module+el8.1.0+4044+36416a77 |
| `libecap-devel` | Red Hat:rhel_e4s:8.4::appstream | All versions | 0:1.0.1-2.module+el8.1.0+4044+36416a77 |
| `squid` | Red Hat:rhel_e4s:8.4::appstream | All versions | 7:4.11-4.module+el8.4.0+22483+0c92772a.9 |
| `squid-debuginfo` | Red Hat:rhel_e4s:8.4::appstream | All versions | 7:4.11-4.module+el8.4.0+22483+0c92772a.9 |
| `squid-debugsource` | Red Hat:rhel_e4s:8.4::appstream | All versions | 7:4.11-4.module+el8.4.0+22483+0c92772a.9 |
| `libecap` | Red Hat:rhel_e4s:8.6::appstream | All versions | 0:1.0.1-2.module+el8.1.0+4044+36416a77 |
| `libecap-debuginfo` | Red Hat:rhel_e4s:8.6::appstream | All versions | 0:1.0.1-2.module+el8.1.0+4044+36416a77 |
| `libecap-debugsource` | Red Hat:rhel_e4s:8.6::appstream | All versions | 0:1.0.1-2.module+el8.1.0+4044+36416a77 |
| `libecap-devel` | Red Hat:rhel_e4s:8.6::appstream | All versions | 0:1.0.1-2.module+el8.1.0+4044+36416a77 |
| `squid` | Red Hat:rhel_e4s:8.6::appstream | All versions | 7:4.15-3.module+el8.6.0+22491+132fca59.7 |
| `squid-debuginfo` | Red Hat:rhel_e4s:8.6::appstream | All versions | 7:4.15-3.module+el8.6.0+22491+132fca59.7 |
| `squid-debugsource` | Red Hat:rhel_e4s:8.6::appstream | All versions | 7:4.15-3.module+el8.6.0+22491+132fca59.7 |
| `squid` | Red Hat:rhel_e4s:9.0::appstream | All versions | 7:5.2-1.el9_0.7 |

Products: Squid-Cache Squid.

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

Upgrade to a fixed version.

## Is CVE-2024-45802 being exploited?

There is no known exploitation of CVE-2024-45802 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-45802 and fix it if it is affected.

What it is: CVE-2024-45802 is a high-severity denial of service vulnerability in Squid-Cache Squid, published on 28 Oct 2024. 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-2024-45802 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-45802/ (Markdown: https://insights.sbomify.com/CVE-2024-45802/index.md)
```

## Sources

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

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