Skip to content
Noroxi
CVE-2016-2571· NVD / CVE Program· CNA mitre

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 al

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.

HighCVSS 7.5 · v3.0—No exploit Fix available
Published
Feb 27, 2016
Updated
Jun 16, 2026
EPSS
9.3% · 95th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

33

Monitor

Low priority for now.

CVSS
30 / 40 · 7.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
3 / 30 · 9.3%

Affected systems

VendorProduct
squid-cachesquid

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
  • 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.

EcosystemPackageAffected rangeFix
Debian:6.0squid3before 3.1.6-1.2+squeeze63.1.6-1.2+squeeze6
Debian:7squid3before 3.1.20-2.2+deb7u43.1.20-2.2+deb7u4
Debian:8squid3before 3.4.8-6+deb8u23.4.8-6+deb8u2
openSUSE:Tumbleweedsquidbefore 4.16-1.54.16-1.5
Red Hat:enterprise_linux:7::serversquidbefore 7:3.5.20-2.el77:3.5.20-2.el7
Red Hat:enterprise_linux:7::serversquid-debuginfobefore 7:3.5.20-2.el77:3.5.20-2.el7
Red Hat:enterprise_linux:7::serversquid-migration-scriptbefore 7:3.5.20-2.el77:3.5.20-2.el7
Red Hat:enterprise_linux:7::serversquid-sysvinitbefore 7:3.5.20-2.el77:3.5.20-2.el7
SUSE:Linux Enterprise Server 11 SP4squid3before 3.1.23-8.16.30.13.1.23-8.16.30.1
SUSE:Linux Enterprise Server 12 SP1squidbefore 3.3.14-20.23.3.14-20.2

Other highest-scoring records for the same primary product.

  • CVE-2023-46847Squid: denial of service in http digest authentication
    57Plan
  • CVE-2024-25617Denial of Service in HTTP Header parser in squid proxy
    56Plan
  • CVE-2023-49285Denial of Service in HTTP Message Processing in Squid
    56Plan
  • CVE-2021-31806An issue was discovered in Squid before 4.15 and 5.x before 5.0.6.
    55Plan
  • CVE-2020-8450An issue was discovered in Squid before 4.10.
    51Plan
  • CVE-2024-25111SQUID-2024:1 Denial of Service in HTTP Chunked Decoding
    50Plan

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
debian:squid33.1.6-1.2+squeeze6 · Debian:6.0Package registry (OSV)
opensuse:squid4.16-1.5 · openSUSE:TumbleweedPackage registry (OSV)
red hat:squid7:3.5.20-2.el7 · Red Hat:enterprise_linux:7::serverPackage registry (OSV)
red hat:squid-debuginfo7:3.5.20-2.el7 · Red Hat:enterprise_linux:7::serverPackage registry (OSV)
red hat:squid-migration-script7:3.5.20-2.el7 · Red Hat:enterprise_linux:7::serverPackage registry (OSV)
red hat:squid-sysvinit7:3.5.20-2.el7 · Red Hat:enterprise_linux:7::serverPackage registry (OSV)
suse:squid3.3.14-20.2 · SUSE:Linux Enterprise Server 12 SP1Package registry (OSV)
suse:squid33.1.23-8.16.30.1 · SUSE:Linux Enterprise Server 11 SP4Package 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.

EPSS, last 120 days

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.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

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

CVSS vector

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

nvd-primary

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records