CVE-2016-4053: Squid 3.x before 3.5.17 and 4.x before 4.0.9 allow remote attackers to obtain sensitive stack layout information via crafted Edge Side…
Noroxi assessment
Priority: Monitor (action score 18/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: 14.3% (FIRST EPSS); higher than 96.6% 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. Special conditions such as timing or configuration are required.
- Fixed version: squid3 (Debian:7) 3.1.20-2.2+deb7u5; squid3 (Debian:8) 3.4.8-6+deb8u3; squid (Red Hat:enterprise_linux:6::server) 7:3.1.23-16.el6_8.4.
Low priority for now. Upgrade to squid3 (Debian:7) 3.1.20-2.2+deb7u5; squid3 (Debian:8) 3.4.8-6+deb8u3; squid (Red Hat:enterprise_linux:6::server) 7:3.1.23-16.el6_8.4 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
Squid 3.x before 3.5.17 and 4.x before 4.0.9 allow remote attackers to obtain sensitive stack layout information via crafted Edge Side Includes (ESI) responses, related to incorrect use of assert and compiler optimization.
- Published
- Apr 25, 2016
- Updated
- Jun 16, 2026
- EPSS
- 14.3% · 96th percentile
- CWE
- CWE-119
Report tools
Action score
18
Low priority for now.
- CVSS
- 14 / 40 · 3.7 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 4 / 30 · 14.3%
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 |
| oracle | linux | cpe:2.3:o:oracle:linux |
| canonical | ubuntu linux | cpe:2.3:o:canonical:ubuntu_linux |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- canonical ubuntu linux12.04
- canonical ubuntu linux14.04
- canonical ubuntu linux15.10
- canonical ubuntu linux16.04
- oracle linux6
- oracle linux7
- squid-cache squid3.0
- squid-cache squid3.1
+12 more rows
- squid-cache squid3.1.0.1
- squid-cache squid3.1.0.10
- squid-cache squid3.1.0.11
- squid-cache squid3.1.0.12
- squid-cache squid3.1.0.13
- squid-cache squid3.1.0.14
- squid-cache squid3.1.0.15
- squid-cache squid3.1.0.16
- squid-cache squid3.1.0.17
- squid-cache squid3.1.0.18
- squid-cache squid3.1.0.2
- squid-cache squid3.1.0.3
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:7 | squid3 | before 3.1.20-2.2+deb7u5 | 3.1.20-2.2+deb7u5 |
| Debian:8 | squid3 | before 3.4.8-6+deb8u3 | 3.4.8-6+deb8u3 |
| Red Hat:enterprise_linux:6::server | squid | before 7:3.1.23-16.el6_8.4 | 7:3.1.23-16.el6_8.4 |
| Red Hat:enterprise_linux:6::server | squid-debuginfo | before 7:3.1.23-16.el6_8.4 | 7:3.1.23-16.el6_8.4 |
| Red Hat:enterprise_linux:6::server | squid34 | before 7:3.4.14-9.el6_8.3 | 7:3.4.14-9.el6_8.3 |
| Red Hat:enterprise_linux:6::server | squid34-debuginfo | before 7:3.4.14-9.el6_8.3 | 7:3.4.14-9.el6_8.3 |
| Red Hat:enterprise_linux:7::server | squid | before 7:3.3.8-26.el7_2.3 | 7:3.3.8-26.el7_2.3 |
| Red Hat:enterprise_linux:7::server | squid-debuginfo | before 7:3.3.8-26.el7_2.3 | 7:3.3.8-26.el7_2.3 |
| Red Hat:enterprise_linux:7::server | squid-sysvinit | before 7:3.3.8-26.el7_2.3 | 7:3.3.8-26.el7_2.3 |
| 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-3948Apr 7, 2016 · Squid 3.x before 3.5.16 and 4.x before 4.0.8 improperly perform bounds checking, which allows remote attackers to cause a denial of service…41Plan
- ← EarlierCVE-2016-2390Apr 19, 2016 · The FwdState::connectedToPeer method in FwdState.cc in Squid before 3.5.14 and 4.0.x before 4.0.6 does not properly handle SSL handshake…31Monitor
- Later →CVE-2016-4555May 10, 2016 · client_side_request.cc in Squid 3.x before 3.5.18 and 4.x before 4.0.10 allows remote servers to cause a denial of service (crash) via…35Monitor
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.20-2.2+deb7u5 · Debian:7 | Package registry (OSV) |
| red hat:squid | 7:3.1.23-16.el6_8.4 · Red Hat:enterprise_linux:6::server | Package registry (OSV) |
| red hat:squid-debuginfo | 7:3.1.23-16.el6_8.4 · Red Hat:enterprise_linux:6::server | Package registry (OSV) |
| red hat:squid-sysvinit | 7:3.3.8-26.el7_2.3 · Red Hat:enterprise_linux:7::server | Package registry (OSV) |
| red hat:squid34 | 7:3.4.14-9.el6_8.3 · Red Hat:enterprise_linux:6::server | Package registry (OSV) |
| red hat:squid34-debuginfo | 7:3.4.14-9.el6_8.3 · Red Hat:enterprise_linux:6::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).
Not on record for this CVE: patch commit or PR link · 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.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- low · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- Low
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-119 · Improper Restriction of Operations within the Bounds of a Memory BufferCVSS vector
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
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
- Overflow BuffersCAPEC-100likelihood: High · Very High
- Buffer ManipulationCAPEC-123likelihood: High · Very High
- Client-side Injection-induced Buffer OverflowCAPEC-14likelihood: Medium · High
- Filter Failure through Buffer OverflowCAPEC-24likelihood: High · High
- MIME ConversionCAPEC-42likelihood: High · High
- Overflow Binary Resource FileCAPEC-44likelihood: High · Very High
- Buffer Overflow via Symbolic LinksCAPEC-45likelihood: High · High
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (16 more)Show less
- lists.opensuse.org/opensuse-security-announce/2016-08/msg00010.html
- lists.opensuse.org/opensuse-security-announce/2016-08/msg00040.html
- lists.opensuse.org/opensuse-updates/2016-08/msg00069.html
- www.openwall.com/lists/oss-security/2016/04/20/6
- www.openwall.com/lists/oss-security/2016/04/20/9
- www.oracle.com/technetwork/security-advisory/cpujul2016-2881720.html
- www.oracle.com/technetwork/topics/security/linuxbulletinapr2016-2952096.html
- www.securityfocus.com/bid/86788
- www.securityfocus.com/bid/91787
- www.securitytracker.com/id/1035647
- www.squid-cache.org/Advisories/SQUID-2016_6.txt
- www.ubuntu.com/usn/USN-2995-1
- access.redhat.com/errata/RHSA-2016:1138
- access.redhat.com/errata/RHSA-2016:1139
- access.redhat.com/errata/RHSA-2016:1140
- security.gentoo.org/glsa/201607-01
Vendor advisories and official records. Exploit/PoC links are deliberately left out.