Service crash via continued processing after write errors
Published Jan 23, 2024 · Updated Jun 17, 2025
Expired pointer dereference in Squid before 6.6 allows remote authenticated users to crash the proxy through Cache Manager error responses. After a client write failure, Server::clientWriteDone calls afterClientWrite instead of terminating all transactions, allowing a null reply to reach Http::One::Server::handleReply and trigger an assertion. Cache Manager access must be permitted to the client; successful exploitation aborts Squid and interrupts proxy service.
Summary
What happened
Expired pointer dereference in Squid before 6.6 allows remote authenticated users to crash the proxy through Cache Manager error responses. After a client write failure, Server::clientWriteDone calls afterClientWrite instead of terminating all transactions, allowing a null reply to reach Http::One::Server::handleReply and trigger an assertion. Cache Manager access must be permitted to the client; successful exploitation aborts Squid and interrupts proxy service.
The record
- CVE
- CVE-2024-23638
- Published
- Jan 23, 2024
- Updated
- Jun 17, 2025
- Vendor
- The Squid Software Foundation
- Product
- Squid
- Classifications
- CWE-825, CWE-672, T1499
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 23, 2024CVE publishedPublication date reported by the CVE source.
- Jun 17, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 6.6
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Implicit Assertion in Stream Handling crash demonstrationproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo