Remote code execution via fixed-size URN buffer
Published Aug 1, 2025 · Updated Nov 5, 2025
Heap buffer overflow in Squid before 6.4 allows remote attackers to execute code through a crafted URN Trivial-HTTP response. urnHandleReply passes a fixed 4 KB destination to storeClientCopy while mixing serialized header and body offsets, allowing response data to exceed its buffer accounting. The remote server must answer a proxy-initiated URN resolution request; exploitation can also disclose up to 4 KB of heap data, including credentials.
Summary
What happened
Heap buffer overflow in Squid before 6.4 allows remote attackers to execute code through a crafted URN Trivial-HTTP response. urnHandleReply passes a fixed 4 KB destination to storeClientCopy while mixing serialized header and body offsets, allowing response data to exceed its buffer accounting. The remote server must answer a proxy-initiated URN resolution request; exploitation can also disclose up to 4 KB of heap data, including credentials.
The record
- CVE
- CVE-2025-54574
- Published
- Aug 1, 2025
- Updated
- Nov 5, 2025
- Vendor
- The Squid Software Foundation
- Product
- Squid
- Classifications
- CWE-122, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 1, 2025CVE publishedPublication date reported by the CVE source.
- Nov 5, 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.4
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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.
Public exploit references
No public exploit references are available in this record.
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