Squid Proxy up to 3.5.15/4.0.7 HTTP Response memory corruption

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
7.2$0-$5k0.00

Summaryinfo

A vulnerability, which was classified as problematic, has been found in Squid Proxy up to 3.5.15/4.0.7. Affected by this vulnerability is an unknown functionality of the component HTTP Response Handler. This manipulation causes memory corruption. This vulnerability is registered as CVE-2016-3948. Remote exploitation of the attack is possible. No exploit is available. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability was found in Squid Proxy up to 3.5.15/4.0.7 (Firewall Software). It has been declared as critical. Affected by this vulnerability is an unknown functionality of the component HTTP Response Handler. The manipulation with an unknown input leads to a memory corruption vulnerability. The CWE definition for the vulnerability is CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. As an impact it is known to affect availability. The summary by CVE is:

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 via a crafted HTTP response, related to Vary headers.

The weakness was published 04/02/2016 as SQUID-2016:4 as confirmed advisory (Website). The advisory is shared at squid-cache.org. This vulnerability is known as CVE-2016-3948 since 04/01/2016. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available.

The vulnerability scanner Nessus provides a plugin with the ID 90334 (FreeBSD : squid -- multiple vulnerabilities (297117ba-f92d-11e5-92ce-002590263bf5)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family FreeBSD Local Security Checks and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 169027 (SUSE Enterprise Linux Security Update for squid3 (SUSE-SU-2016:1996-1)).

Upgrading to version 3.5.16 or 4.0.8 eliminates this vulnerability. A possible mitigation has been published immediately after the disclosure of the vulnerability. Furthermore it is possible to detect and prevent this kind of attack with TippingPoint and the filter 24578.

The vulnerability is also documented in the databases at Tenable (90334), SecurityFocus (BID 85803†), SecurityTracker (ID 1035458†) and Vulnerability Center (SBV-58068†). Similar entries are available at VDB-4435, VDB-7183, VDB-9526 and VDB-67519. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 7.5
VulDB Meta Temp Score: 7.3

VulDB Base Score: 7.5
VulDB Temp Score: 7.2
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 7.5
NVD Vector: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Class: Memory corruption
CWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 90334
Nessus Name: FreeBSD : squid -- multiple vulnerabilities (297117ba-f92d-11e5-92ce-002590263bf5)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

OpenVAS ID: 103320
OpenVAS Name: Squid Multiple Denial of Service Vulnerabilities April16 (Windows)
OpenVAS File: 🔍
OpenVAS Family: 🔍

Qualys ID: 🔍
Qualys Name: 🔍

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍

Upgrade: Proxy 3.5.16/4.0.8
TippingPoint: 🔍

McAfee IPS: 🔍
McAfee IPS Version: 🔍

Fortigate IPS: 🔍

Timelineinfo

04/01/2016 🔍
04/02/2016 +1 days 🔍
04/02/2016 +0 days 🔍
04/02/2016 +0 days 🔍
04/04/2016 +2 days 🔍
04/04/2016 +0 days 🔍
04/05/2016 +1 days 🔍
04/05/2016 +0 days 🔍
04/07/2016 +1 days 🔍
04/12/2016 +5 days 🔍
02/04/2019 +1028 days 🔍

Sourcesinfo

Vendor: squid-cache.org

Advisory: SQUID-2016:4
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2016-3948 (🔍)
GCVE (CVE): GCVE-0-2016-3948
GCVE (VulDB): GCVE-100-81565
SecurityFocus: 85803 - Squid CVE-2016-3948 Incomplete Fix Denial of Service Vulnerability
SecurityTracker: 1035458
Vulnerability Center: 58068 - Squid 3.0 through 3.5.15 and 4.0 through 4.0.7 Remote DoS via a Crafted HTTP Response, Medium

See also: 🔍

Entryinfo

Created: 04/05/2016 09:01
Updated: 02/04/2019 11:45
Changes: 04/05/2016 09:01 (80), 02/04/2019 11:45 (14)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Want to know what is going to be exploited?

We predict KEV entries!