CVE-2016-2571: http.cc in Squid 3.x before 3.5.15 and 4.x before 4.0.7 proceeds with the storage of certain data after a response-parsing failure, which…
Noroxi assessment
Priority: Monitor (action score 33/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 9.2% (FIRST EPSS); higher than 95.4% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: squid3 (Debian:6.0) 3.1.6-1.2+squeeze6; squid3 (Debian:7) 3.1.20-2.2+deb7u4; squid3 (Debian:8) 3.4.8-6+deb8u2.
Low priority for now. Upgrade to squid3 (Debian:6.0) 3.1.6-1.2+squeeze6; squid3 (Debian:7) 3.1.20-2.2+deb7u4; squid3 (Debian:8) 3.4.8-6+deb8u2 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
http.cc in Squid 3.x before 3.5.15 and 4.x before 4.0.7 proceeds with the storage of certain data after a response-parsing failure, which allows remote HTTP servers to cause a denial of service (assertion failure and daemon exit) via a malformed response.
- Published
- Feb 27, 2016
- Updated
- Jun 16, 2026
- EPSS
- 9.2% · 95th percentile
- CWE
- CWE-20
Report tools
Action score
33
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 3 / 30 · 9.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| squid-cache | squid | cpe:2.3:a:squid-cache:squid |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- squid-cache squid3.0
- squid-cache squid3.0.stable1
- squid-cache squid3.0.stable10
- squid-cache squid3.0.stable11
- squid-cache squid3.0.stable12
- squid-cache squid3.0.stable13
- squid-cache squid3.0.stable14
- squid-cache squid3.0.stable15
+12 more rows
- squid-cache squid3.0.stable16
- squid-cache squid3.0.stable17
- squid-cache squid3.0.stable18
- squid-cache squid3.0.stable19
- squid-cache squid3.0.stable2
- squid-cache squid3.0.stable20
- squid-cache squid3.0.stable21
- squid-cache squid3.0.stable22
- squid-cache squid3.0.stable23
- squid-cache squid3.0.stable24
- squid-cache squid3.0.stable25
- squid-cache squid3.0.stable3
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:6.0 | squid3 | before 3.1.6-1.2+squeeze6 | 3.1.6-1.2+squeeze6 |
| Debian:7 | squid3 | before 3.1.20-2.2+deb7u4 | 3.1.20-2.2+deb7u4 |
| Debian:8 | squid3 | before 3.4.8-6+deb8u2 | 3.4.8-6+deb8u2 |
| openSUSE:Tumbleweed | squid | before 4.16-1.5 | 4.16-1.5 |
| Red Hat:enterprise_linux:7::server | squid | before 7:3.5.20-2.el7 | 7:3.5.20-2.el7 |
| Red Hat:enterprise_linux:7::server | squid-debuginfo | before 7:3.5.20-2.el7 | 7:3.5.20-2.el7 |
| Red Hat:enterprise_linux:7::server | squid-migration-script | before 7:3.5.20-2.el7 | 7:3.5.20-2.el7 |
| Red Hat:enterprise_linux:7::server | squid-sysvinit | before 7:3.5.20-2.el7 | 7:3.5.20-2.el7 |
| SUSE:Linux Enterprise Server 11 SP4 | squid3 | before 3.1.23-8.16.30.1 | 3.1.23-8.16.30.1 |
| SUSE:Linux Enterprise Server 12 SP1 | squid | before 3.3.14-20.2 | 3.3.14-20.2 |
Same product
squid-cache: all recordsOther highest-scoring records for the same primary product.
- CVE-2024-25617Denial of Service in HTTP Header parser in squid proxy57Plan
- CVE-2023-49285Denial of Service in HTTP Message Processing in Squid56Plan
- CVE-2021-31806An issue was discovered in Squid before 4.15 and 5.x before 5.0.6.55Plan
Published before and after this one in the same product
- ← EarlierCVE-2016-2569Feb 27, 2016 · Squid 3.x before 3.5.15 and 4.x before 4.0.7 does not properly append data to String objects, which allows remote servers to cause a denial…39Monitor
- ← EarlierCVE-2016-2570Feb 27, 2016 · The Edge Side Includes (ESI) parser in Squid 3.x before 3.5.15 and 4.x before 4.0.7 does not check buffer limits during XML parsing, which…33Monitor
- Later →CVE-2016-2572Feb 27, 2016 · http.cc in Squid 4.x before 4.0.7 relies on the HTTP status code after a response-parsing failure, which allows remote HTTP servers to…33Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:squid3 | 3.1.6-1.2+squeeze6 · Debian:6.0 | Package registry (OSV) |
| opensuse:squid | 4.16-1.5 · openSUSE:Tumbleweed | Package registry (OSV) |
| red hat:squid | 7:3.5.20-2.el7 · Red Hat:enterprise_linux:7::server | Package registry (OSV) |
| red hat:squid-debuginfo | 7:3.5.20-2.el7 · Red Hat:enterprise_linux:7::server | Package registry (OSV) |
| red hat:squid-migration-script | 7:3.5.20-2.el7 · Red Hat:enterprise_linux:7::server | Package registry (OSV) |
| red hat:squid-sysvinit | 7:3.5.20-2.el7 · Red Hat:enterprise_linux:7::server | Package registry (OSV) |
| suse:squid | 3.3.14-20.2 · SUSE:Linux Enterprise Server 12 SP1 | Package registry (OSV) |
| suse:squid3 | 3.1.23-8.16.30.1 · SUSE:Linux Enterprise Server 11 SP4 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Not on record for this CVE: researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-20 · Improper Input ValidationCVSS vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Buffer Overflow via Environment VariablesCAPEC-10likelihood: High · High
- Server Side Include (SSI) InjectionCAPEC-101likelihood: High · High
- Cross Zone ScriptingCAPEC-104likelihood: Medium · High
- Command Line Execution through SQL InjectionCAPEC-108likelihood: Low · Very High
- Object Relational Mapping InjectionCAPEC-109likelihood: Low · High
- SQL Injection through SOAP Parameter TamperingCAPEC-110likelihood: High · Very High
- Double EncodingCAPEC-120likelihood: Low · Medium
- Subverting Environment Variable ValuesCAPEC-13likelihood: High · Very High
ATT&CK techniques
- Obfuscated Files or InformationT1027
- Masquerading: Invalid Code SignatureT1036.001
- Steal Web Session CookieT1539
- Subvert Trust Controls: Code SigningT1553.002
- Impair Defenses:Impair Command History LoggingT1562.003
- Hijack Execution Flow:Dynamic Linker HijackingT1574.006
- Hijack Execution Flow:Path Interception by PATH Environment VariableT1574.007
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (12 more)Show less
- lists.opensuse.org/opensuse-security-announce/2016-08/msg00040.html
- lists.opensuse.org/opensuse-updates/2016-08/msg00069.html
- rhn.redhat.com/errata/RHSA-2016-2600.html
- www.debian.org/security/2016/dsa-3522
- www.openwall.com/lists/oss-security/2016/02/26/2
- www.securitytracker.com/id/1035101
- www.squid-cache.org/Advisories/SQUID-2016_2.txt
- www.squid-cache.org/Versions/v3/3.5/changesets/squid-3.5-13990.patch
- www.squid-cache.org/Versions/v4/changesets/squid-4-14548.patch
- www.ubuntu.com/usn/USN-2921-1
- security.gentoo.org/glsa/201607-01
- usn.ubuntu.com/3557-1/
Vendor advisories and official records. Exploit/PoC links are deliberately left out.