CVE Vulnerabilities

CVE-2025-54574

Heap-based Buffer Overflow

Published: Aug 01, 2025 | Modified: Aug 04, 2025
CVSS 3.x
N/A
Source:
NVD
CVSS 2.x
RedHat/V2
RedHat/V3
8.9 IMPORTANT
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:L
Ubuntu
MEDIUM

Squid is a caching proxy for the Web. In versions 6.3 and below, Squid is vulnerable to a heap buffer overflow and possible remote code execution attack when processing URN due to incorrect buffer management. This has been fixed in version 6.4. To work around this issue, disable URN access permissions.

Weakness

A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc().

Affected Software

Name Vendor Start Version End Version
Red Hat Enterprise Linux 8 RedHat squid:4-8090020231130092412.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.2 *
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 focal *
Squid Ubuntu jammy *
Squid Ubuntu upstream *

Potential Mitigations

  • Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking.
  • D3-SFCV (Stack Frame Canary Validation) from D3FEND [REF-1334] discusses canary-based detection in detail.
  • Run or compile the software using features or extensions that randomly arrange the positions of a program’s executable and libraries in memory. Because this makes the addresses unpredictable, it can prevent an attacker from reliably jumping to exploitable code.
  • Examples include Address Space Layout Randomization (ASLR) [REF-58] [REF-60] and Position-Independent Executables (PIE) [REF-64]. Imported modules may be similarly realigned if their default memory addresses conflict with other modules, in a process known as “rebasing” (for Windows) and “prelinking” (for Linux) [REF-1332] using randomly generated addresses. ASLR for libraries cannot be used in conjunction with prelink since it would require relocating the libraries at run-time, defeating the whole purpose of prelinking.
  • For more information on these techniques see D3-SAOR (Segment Address Offset Randomization) from D3FEND [REF-1335].

References