CVE-2011-4096: The idnsGrokReply function in Squid before 3.1.16 does not properly free memory, which allows remote attackers to cause a denial of service…
Noroxi assessment
Priority: Monitor (action score 31/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: 37.1% (FIRST EPSS); higher than 98.5% of all records.
- No special conditions are required; it is repeatable.
- Fixed version: squid3 (Debian:6.0) 3.1.6-1.2+squeeze2; squid (Red Hat:enterprise_linux:6::server) 7:3.1.10-1.el6_2.1; squid-debuginfo (Red Hat:enterprise_linux:6::server) 7:3.1.10-1.el6_2.1.
Low priority for now. Upgrade to squid3 (Debian:6.0) 3.1.6-1.2+squeeze2; squid (Red Hat:enterprise_linux:6::server) 7:3.1.10-1.el6_2.1; squid-debuginfo (Red Hat:enterprise_linux:6::server) 7:3.1.10-1.el6_2.1 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
The idnsGrokReply function in Squid before 3.1.16 does not properly free memory, which allows remote attackers to cause a denial of service (daemon abort) via a DNS reply containing a CNAME record that references another CNAME record that contains an empty A record.
- Published
- Nov 17, 2011
- Updated
- Jun 16, 2026
- EPSS
- 37.1% · 98th percentile
- CWE
- CWE-399
Report tools
Action score
31
Low priority for now.
- CVSS
- 20 / 40 · 5.0 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 11 / 30 · 37.1%
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 squidup to 3.1.15 inclusive
- 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
+12 more rows
- 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
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+squeeze2 | 3.1.6-1.2+squeeze2 |
| Red Hat:enterprise_linux:6::server | squid | before 7:3.1.10-1.el6_2.1 | 7:3.1.10-1.el6_2.1 |
| Red Hat:enterprise_linux:6::server | squid-debuginfo | before 7:3.1.10-1.el6_2.1 | 7:3.1.10-1.el6_2.1 |
| SUSE:Linux Enterprise Server 11 SP4 | squid3 | before 3.1.23-8.16.30.1 | 3.1.23-8.16.30.1 |
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-2010-2951Oct 12, 2010 · dns_internal.cc in Squid 3.1.6, when IPv6 DNS resolution is not enabled, accesses an invalid socket during an IPv4 TCP DNS query, which…29Monitor
- ← EarlierCVE-2011-3205Sep 6, 2011 · Buffer overflow in the gopherToHTML function in gopher.cc in the Gopher reply parser in Squid 3.0 before 3.0.STABLE26, 3.1 before 3.1.15…35Monitor
- Later →CVE-2012-2213Apr 28, 2012 · Squid 3.1.9 allows remote attackers to bypass the access configuration for the CONNECT method by providing an arbitrary allowed hostname in…24Monitor
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+squeeze2 · Debian:6.0 | Package registry (OSV) |
| red hat:squid | 7:3.1.10-1.el6_2.1 · Red Hat:enterprise_linux:6::server | Package registry (OSV) |
| red hat:squid-debuginfo | 7:3.1.10-1.el6_2.1 · Red Hat:enterprise_linux:6::server | 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.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- P · the service can be disrupted
- Attack complexity
- Low
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- P
Weakness class (CWE)
CWE-399 · Resource Management ErrorsCVSS vector
AV:N/AC:L/Au:N/C:N/I:N/A:P
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.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (10 more)Show less
- lists.opensuse.org/opensuse-security-announce/2016-08/msg00010.html
- lists.opensuse.org/opensuse-security-announce/2016-08/msg00040.html
- secunia.com/advisories/46609
- secunia.com/advisories/47459
- www.mandriva.com/security/advisories?name=MDVSA-2011:193
- www.openwall.com/lists/oss-security/2011/10/31/5
- www.openwall.com/lists/oss-security/2011/11/01/3
- www.redhat.com/support/errata/RHSA-2011-1791.html
- www.securitytracker.com/id?1026265
- www.squid-cache.org/Versions/v3/3.1/changesets/SQUID_3_1_16.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.