CVE-2010-3072: Null Pointer Dereference

Published Sep 3, 2010
·
Updated

A denial of service flaw was found in the way Squid proxy caching server internally processed NULL buffers. A remote, trusted client could use this flaw to cause squid daemon crash (dereference NULL pointer) when processing specially-crafted request.

References: [1] http://www.squid-cache.org/Advisories/SQUID-20103.txt

Upstream patch (against Squid v3.0): [2] http://www.squid-cache.org/Versions/v3/3.0/changesets/squid-3.0-9189.patch

Upstream patch (against Squid v3.1): [3] http://www.squid-cache.org/Versions/v3/3.1/changesets/squid-3.1-10090.patch

Credit: The vulnerability was discovered by Phil Oester.

Other sources

The string-comparison functions in String.cci in Squid 3.x before 3.1.8 and 3.2.x before 3.2.0.2 allow remote attackers to cause a denial of service (NULL pointer dereference and daemon crash) via a crafted request.

Affected Software

56 affected componentsFixes available
redhat/squid<7:3.1.10-1.el6
7:3.1.10-1.el6
Squid-Cache Squid=3.0
Squid-Cache Squid=3.0.stable1
Squid-Cache Squid=3.0.stable2
Squid-Cache Squid=3.0.stable3
Squid-Cache Squid=3.0.stable4
Squid-Cache Squid=3.0.stable5
Squid-Cache Squid=3.0.stable6
Squid-Cache Squid=3.0.stable7
Squid-Cache Squid=3.0.stable8
Squid-Cache Squid=3.0.stable9
Squid-Cache Squid=3.0.stable10
Squid-Cache Squid=3.0.stable11
Squid-Cache Squid=3.0.stable11-rc1
Squid-Cache Squid=3.0.stable12
Squid-Cache Squid=3.0.stable13
Squid-Cache Squid=3.0.stable14
Squid-Cache Squid=3.0.stable15
Squid-Cache Squid=3.0.stable16
Squid-Cache Squid=3.0.stable16-rc1
Squid-Cache Squid=3.0.stable17
Squid-Cache Squid=3.0.stable18
Squid-Cache Squid=3.0.stable19
Squid-Cache Squid=3.0.stable20
Squid-Cache Squid=3.0.stable21
Squid-Cache Squid=3.0.stable22
Squid-Cache Squid=3.0.stable23
Squid-Cache Squid=3.0.stable24
Squid-Cache Squid=3.0.stable25
Squid-Cache Squid=3.1
Squid-Cache Squid=3.1.0.1
Squid-Cache Squid=3.1.0.2
Squid-Cache Squid=3.1.0.3
Squid-Cache Squid=3.1.0.4
Squid-Cache Squid=3.1.0.5
Squid-Cache Squid=3.1.0.6
Squid-Cache Squid=3.1.0.7
Squid-Cache Squid=3.1.0.8
Squid-Cache Squid=3.1.0.9
Squid-Cache Squid=3.1.0.10
Squid-Cache Squid=3.1.0.11
Squid-Cache Squid=3.1.0.12
Squid-Cache Squid=3.1.0.13
Squid-Cache Squid=3.1.0.14
Squid-Cache Squid=3.1.0.15
Squid-Cache Squid=3.1.0.16
Squid-Cache Squid=3.1.0.17
Squid-Cache Squid=3.1.0.18
Squid-Cache Squid=3.1.1
Squid-Cache Squid=3.1.2
Squid-Cache Squid=3.1.3
Squid-Cache Squid=3.1.4
Squid-Cache Squid=3.1.5
Squid-Cache Squid=3.1.5.1
Squid-Cache Squid=3.1.6
Squid-Cache Squid=3.1.7

Event History

Sep 3, 2010
CVE Published
12:00 AM
Sep 5, 2010
Data Sourced
04:09 PM
DescriptionSeverityAffected Software
Sep 20, 2010
CVE Published
via MITRE·08:00 PM
Data Sourced
via MITRE·08:00 PM
Description

Parent advisories

This vulnerability appears in the following advisories.

Frequently Asked Questions

1

What is the severity of CVE-2010-3072?

CVE-2010-3072 has a severity rating that indicates it can lead to a denial of service attack on the Squid proxy caching server.

2

How do I fix CVE-2010-3072?

To fix CVE-2010-3072, upgrade Squid to version 3.1.10 or later.

3

Which versions of Squid are affected by CVE-2010-3072?

CVE-2010-3072 affects Squid versions 3.0 and 3.1 prior to 3.1.10.

4

Can CVE-2010-3072 be exploited by unauthenticated users?

No, CVE-2010-3072 can only be exploited by a remote, trusted client.

5

What type of vulnerability is CVE-2010-3072?

CVE-2010-3072 is classified as a denial of service vulnerability.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203