CVE-2024-45802

Description

A flaw was found in Squid. When configured as a reverse proxy with Edge Side Includes (ESI) enabled, improper input validation and resource handling during the processing of ESI response content allow an upstream server to cause a Denial of Service (DoS). By returning specially crafted ESI markup or oversized headers, a malicious server can crash the proxy process or exhaust system resources, disrupting service for all connected clients.

Statement

This vulnerability is rated as Important severity because an unauthenticated remote entity can trigger an unhandled failure in the Squid daemon, leading to an immediate denial of service that disrupts caching and proxying operations for all users. In Red Hat Enterprise Linux, Squid packages are built with Edge Side Includes (ESI) support active, which exposes instances configured in reverse-proxy or accelerator topologies to malformed responses from upstream servers. Standard forward proxy deployments that do not inspect or parse ESI elements from backend HTTP servers are not vulnerable to this condition.

Mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

Common Vulnerability Scoring System (CVSS) Score Details

Info alert:Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).

CVSS v3 Score Breakdown

Red HatNVDcve.org
Base Score7.57.57.5
Attack VectorNetworkNetworkNetwork
Attack ComplexityLowLowLow
Privileges RequiredNoneNoneNone
User InteractionNoneNoneNone
ScopeUnchangedUnchangedUnchanged
ConfidentialityNoneNoneNone
Integrity ImpactNoneNoneNone
Availability ImpactHighHighHigh

Vector

Red Hat: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

NVD: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

cve.org: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Understanding the Weakness (CWE)

Confidentiality

Technical Impact: Read Application Data; Read Memory

If the released resource is subsequently reused or reallocated, then a read operation on the original resource might access sensitive data that is associated with a different user or entity.

Availability

Technical Impact: Unexpected State; DoS: Crash, Exit, or Restart

When the resource is released, the software might modify some of its structure, or close associated channels (such as a file descriptor). When the software later accesses the resource as if it is valid, the resource might not be in an expected state, leading to resultant errors that may lead to a crash.

Integrity,Confidentiality,Availability

Technical Impact: Execute Unauthorized Code or Commands; Modify Application Data; Modify Memory

When the resource is released, the software might modify some of its structure. This might affect logic in the sections of code that still assume the resource is active. If the released resource is related to memory and is used in a function call, or points to unexpected data in a write operation, then code execution may be possible upon subsequent accesses.

Frequently Asked Questions

Want to get errata notifications? Sign up here.