dbcve.org
SquidApplication · Squid Cache

CVE-2024-45802

HIGH · 7.5 CVSS v3.1 Published 2024-10-28
Fix available
A fix is available. Upgrade to 6.10 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Squid caching proxy contains multiple resource management vulnerabilities involving input validation failures, premature release of resources during expected lifetime, and missing release of resources after effective lifetime. A trusted upstream server can exploit these flaws to cause Denial of Service against all clients using the proxy.

MitigationUpgrade to Squid version 6.10 or later. As a temporary workaround, restrict which servers can communicate with the proxy and implement rate limiting on upstream connections.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
SquidApplication
Affected:>= 3.0, < 6.10

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Squid installation and version
    Run `squid -v` or check package manager (e.g., `rpm -q squid`, `dpkg -l squid`) to obtain the installed Squid version
    Affected if Installed version is 3.0 or higher but below 6.10
  2. Confirm Squid service is active
    Run `systemctl status squid` or check process list with `ps aux | grep squid` to verify Squid is running
    Affected if Squid is running and version falls within the affected range
  3. Identify upstream server access exposure
    Review Squid configuration file (typically `/etc/squid/squid.conf` or `/etc/squid/conf.d/`) for `cache_peer` directives that define upstream proxy servers, and check network ACLs allowing external upstream connections
    Affected if Squid is configured to accept connections from or forward requests to untrusted or any upstream servers (any `cache_peer` entry pointing to external networks)
  4. Check for rate limiting on upstream connections
    Inspect Squid configuration for `delay_pools` or similar rate-limiting directives applied to upstream traffic patterns
    Affected if No rate limiting is configured on upstream/server interactions and version is vulnerable

You are affected if Squid version 3.0 or higher but below 6.10 is running and can receive requests from upstream servers.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 6.10 or later
Fixed in 6.10
Interim mitigation

Upgrade to Squid version 6.10 or later. As a temporary workaround, restrict which servers can communicate with the proxy and implement rate limiting on upstream connections.

Recommended fix High confidence

Squid 6.10 or later

  1. Download Squid version 6.10 or later from the official Squid website or your distribution's package repository
  2. Backup your current Squid configuration file (typically /etc/squid/squid.conf)
  3. Stop the Squid service using 'systemctl stop squid' or 'service squid stop'
  4. Install the new Squid package using your package manager or compile from source with default build configuration
  5. Verify the installation by checking the version with 'squid -v'
  6. Start the Squid service using 'systemctl start squid' or 'service squid start'
  7. Test that the proxy is functioning correctly and monitor for any issues
Caveat Review the Squid 6.10 release notes for any configuration or feature changes that may affect your setup

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Squid Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-45802 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-45802 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data