CVE intelligence and bounded remediation
CVE-2020-24606 — Squid-Cache Squid security vulnerability
High
CVSS 8.6
Squid before 4.13 and 5.x before 5.0.4 allows a trusted peer to perform Denial of Service by consuming all available CPU cycles during handling of a crafted Cache Digest response message. This only occurs when cache_peer is used with the cache digests feature. The problem exists because peerDigestHandleReply() livelocking in peer_digest.cc mishandles EOF.
- Severity
- High
- CVSS
- 8.6 (3.1)
- Published
- 2020-08-24
- CISA KEV
- Not currently listed
- Ecosystem
- software/application
- Weaknesses
- CWE-667
Affected products
- squid-cache / squid
- canonical / ubuntu_linux / 16.04
- canonical / ubuntu_linux / 18.04
- canonical / ubuntu_linux / 20.04
- debian / debian_linux / 9.0
- debian / debian_linux / 10.0
Matched remediation archetype
Race condition, TOCTOU, and lifecycle synchronization
This catalog composition supplies bounded fallback guidance. Explicitly reviewed curated workflows load with the complete record below.
Check exposure
- Map concurrent actors, shared state, lock boundaries, signals, callbacks, retries, and check-then-use sequences in the affected path.
- Determine whether untrusted users can influence timing, object names, filesystem state, or repeated state transitions.
- Identify clustered and multi-process behavior that repository-local tests may not represent.
Remediate safely
- Make the sensitive state transition atomic or protect it with a consistently ordered synchronization primitive.
- Perform authorization and invariant checks on the same authoritative object and transaction used for the operation.
- Use unique private resources, safe ownership transfer, and idempotent operations; add deterministic concurrency regression tests.
Authoritative sources
Complete CVE record and remediation plan
The detailed catalog view below loads this exact record, its source evidence, and the full seven-phase agentic change plan.