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 allows remote attackers to cause a denial of service (assertion failure and daemon exit) via vectors that trigger an IPv4 DNS response with the TC bit set.
CVE-2010-2951
NONECVSS 0.0Elevated
0.0
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- No confirmed exploitation signals yet
CISA-KEV: Not listedEPSS: 31%CVSS: —Exploit: NoneExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- —
- EG Score
- 0.0(none)
- EPSS
- 98.1%
- KEV
- Not listed
Published
October 12, 2010
Last Modified
April 29, 2026
References (22)
- secalert@redhathttp://bazaar.launchpad.net/~squid/squid/3.1/revision/10072
- secalert@redhathttp://bugs.gentoo.org/show_bug.cgi?id=334263
- secalert@redhathttp://bugs.squid-cache.org/show_bug.cgi?id=3009
- secalert@redhathttp://bugs.squid-cache.org/show_bug.cgi?id=3021
- secalert@redhathttp://marc.info/?l=squid-users&m=128263555724981&w=2
- secalert@redhathttp://www.openwall.com/lists/oss-security/2010/08/24/6
- secalert@redhathttp://www.openwall.com/lists/oss-security/2010/08/24/7
- secalert@redhathttp://www.openwall.com/lists/oss-security/2010/08/25/2
- secalert@redhathttp://www.openwall.com/lists/oss-security/2010/08/25/6
- secalert@redhathttp://www.squid-cache.org/Versions/v3/3.1/changesets/squid-3.1-10072.patch
- secalert@redhathttps://bugzilla.redhat.com/show_bug.cgi?id=626927
- af854a3a-2127-422b-91ae-364da2661108http://bazaar.launchpad.net/~squid/squid/3.1/revision/10072
- af854a3a-2127-422b-91ae-364da2661108http://bugs.gentoo.org/show_bug.cgi?id=334263
- af854a3a-2127-422b-91ae-364da2661108http://bugs.squid-cache.org/show_bug.cgi?id=3009
- af854a3a-2127-422b-91ae-364da2661108http://bugs.squid-cache.org/show_bug.cgi?id=3021
Data Freshness Timeline
(refreshed 5× in last 7d / 29× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-06 02:19 UTCEPSS rescore
- 2026-07-06 02:19 UTCEPSS rescore
- 2026-07-02 14:01 UTCEPSS rescore
- 2026-07-01 15:02 UTCEPSS rescore
- 2026-06-30 23:19 UTCEPSS rescore
- 2026-06-29 14:02 UTCEPSS rescore
- 2026-06-29 14:02 UTCEPSS rescore
- 2026-06-28 04:52 UTCEPSS rescore
- 2026-06-28 04:52 UTCEPSS rescore
- 2026-06-27 03:05 UTCEPSS rescore
- 2026-06-25 13:46 UTCEPSS rescore
- 2026-06-24 14:02 UTCEPSS rescore
- 2026-06-24 14:02 UTCEPSS rescore
- 2026-06-23 21:30 UTCEPSS rescore
- 2026-06-23 21:29 UTCEPSS rescore
- 2026-06-21 01:56 UTCEPSS rescore
- 2026-06-21 01:56 UTCEPSS rescore
- 2026-06-18 17:49 UTCEPSS rescore
- 2026-06-18 17:49 UTCEPSS rescore
- 2026-06-17 17:49 UTCEPSS rescore
- 2026-06-17 17:49 UTCEPSS rescore
- 2026-06-16 17:49 UTCEPSS rescore
- 2026-06-15 17:44 UTCEPSS rescore
- 2026-06-14 23:14 UTCEPSS rescore
- 2026-06-12 23:08 UTCEPSS rescore
Show 37 moreShow fewer
- 2026-06-12 23:08 UTCEPSS rescore
- 2026-06-11 13:56 UTCEPSS rescore
- 2026-06-10 22:14 UTCEPSS rescore
- 2026-06-08 14:13 UTCEPSS rescore
- 2026-06-06 13:44 UTCEPSS rescore
- 2026-06-06 13:44 UTCEPSS rescore
- 2026-06-05 22:44 UTCEPSS rescore
- 2026-06-05 22:44 UTCEPSS rescore
- 2026-06-05 06:07 UTCEPSS rescore
- 2026-06-05 06:07 UTCEPSS rescore
- 2026-06-04 13:09 UTCEPSS rescore
- 2026-06-04 13:09 UTCEPSS rescore
- 2026-06-02 20:10 UTCEPSS rescore
- 2026-06-02 20:10 UTCEPSS rescore
- 2026-06-01 13:49 UTCEPSS rescore
- 2026-06-01 13:49 UTCEPSS rescore
- 2026-05-31 22:28 UTCEPSS rescore
- 2026-05-31 22:28 UTCEPSS rescore
- 2026-05-29 13:40 UTCEPSS rescore
- 2026-05-29 10:08 UTCEG score recompute
- 2026-05-29 10:08 UTCGHSA enrichment
- 2026-05-28 13:42 UTCEPSS rescore
- 2026-05-28 13:42 UTCEPSS rescore
- 2026-05-27 13:38 UTCEPSS rescore
- 2026-05-27 13:38 UTCEPSS rescore
- 2026-05-24 16:43 UTCEPSS rescore
- 2026-05-22 21:15 UTCEPSS rescore
- 2026-05-22 21:15 UTCEPSS rescore
- 2026-05-22 21:15 UTCEPSS rescore
- 2026-05-21 22:39 UTCEPSS rescore
- 2026-05-20 22:37 UTCEPSS rescore
- 2026-05-20 22:37 UTCEPSS rescore
- 2026-05-20 22:37 UTCEPSS rescore
- 2026-05-20 11:21 UTCEPSS rescore
- 2026-05-20 11:21 UTCEPSS rescore
- 2026-05-18 21:29 UTCEPSS rescore
- 2026-05-18 21:29 UTCEPSS rescore
Frequently asked(4)
What is CVE-2010-2951?
CVE-2010-2951 is a none vulnerability published on October 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 allows remote attackers to cause a denial of service (assertion failure and daemon exit) via vectors that trigger an IPv4 DNS response with the TC bit set.
When was CVE-2010-2951 disclosed?
CVE-2010-2951 was first published in the National Vulnerability Database on October 12, 2010, with the most recent update on April 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2010-2951 actively exploited?
CVE-2010-2951 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 98.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
How do I remediate CVE-2010-2951?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2010-2951, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2010-2951
Is Your Infrastructure Affected by CVE-2010-2951?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.