CVE Vulnerabilities

CVE-2023-46724

Out-of-bounds Read

Published: Nov 01, 2023 | Modified: Nov 21, 2024
CVSS 3.x
7.5
HIGH
Source:
NVD
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
CVSS 2.x
RedHat/V2
RedHat/V3
7.5 IMPORTANT
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Ubuntu
MEDIUM

Squid is a caching proxy for the Web. Due to an Improper Validation of Specified Index bug, Squid versions 3.3.0.1 through 5.9 and 6.0 prior to 6.4 compiled using --with-openssl are vulnerable to a Denial of Service attack against SSL Certificate validation. This problem allows a remote server to perform Denial of Service against Squid Proxy by initiating a TLS Handshake with a specially crafted SSL Certificate in a server certificate chain. This attack is limited to HTTPS and SSL-Bump. This bug is fixed in Squid version 6.4. In addition, patches addressing this problem for the stable releases can be found in Squids patch archives. Those who you use a prepackaged version of Squid should refer to the package vendor for availability information on updated packages.

Weakness

The product reads data past the end, or before the beginning, of the intended buffer.

Affected Software

Name Vendor Start Version End Version
Squid Squid-cache 3.3.0.1 (including) 6.4 (excluding)
Red Hat Enterprise Linux 7 RedHat squid-7:3.5.20-17.el7_9.10 *
Red Hat Enterprise Linux 8 RedHat squid:4-8090020231207155957.a75119d5 *
Red Hat Enterprise Linux 8.2 Advanced Update Support RedHat squid:4-8020020240122164331.4cda2c84 *
Red Hat Enterprise Linux 8.2 Telecommunications Update Service RedHat squid:4-8020020240122164331.4cda2c84 *
Red Hat Enterprise Linux 8.2 Update Services for SAP Solutions RedHat squid:4-8020020240122164331.4cda2c84 *
Red Hat Enterprise Linux 8.4 Advanced Mission Critical Update Support RedHat squid:4-8040020240122165847.522a0ee4 *
Red Hat Enterprise Linux 8.4 Telecommunications Update Service RedHat squid:4-8040020240122165847.522a0ee4 *
Red Hat Enterprise Linux 8.4 Update Services for SAP Solutions RedHat squid:4-8040020240122165847.522a0ee4 *
Red Hat Enterprise Linux 8.6 Extended Update Support RedHat squid:4-8060020231222131040.ad008a3a *
Red Hat Enterprise Linux 8.8 Extended Update Support RedHat squid:4-8080020231222130009.63b34585 *
Red Hat Enterprise Linux 9 RedHat squid-7:5.5-6.el9_3.5 *
Red Hat Enterprise Linux 9.0 Extended Update Support RedHat squid-7:5.2-1.el9_0.4 *
Red Hat Enterprise Linux 9.2 Extended Update Support RedHat squid-7:5.5-5.el9_2.3 *
Squid Ubuntu bionic *
Squid Ubuntu devel *
Squid Ubuntu jammy *
Squid Ubuntu lunar *
Squid Ubuntu mantic *
Squid Ubuntu noble *
Squid Ubuntu oracular *
Squid Ubuntu trusty *
Squid Ubuntu xenial *
Squid3 Ubuntu bionic *
Squid3 Ubuntu trusty *
Squid3 Ubuntu xenial *

Potential Mitigations

  • Assume all input is malicious. Use an “accept known good” input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
  • When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, “boat” may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as “red” or “blue.”
  • Do not rely exclusively on looking for malicious or malformed inputs. This is likely to miss at least one undesirable input, especially if the code’s environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.
  • To reduce the likelihood of introducing an out-of-bounds read, ensure that you validate and ensure correct calculations for any length argument, buffer size calculation, or offset. Be especially careful of relying on a sentinel (i.e. special character such as NUL) in untrusted inputs.

References