
CVE-2025-54574
Severity: Critical (CVSS 9.3) Affected Software: Squid Proxy (versions 6.3 and earlier) Vulnerability Type: Heap-based buffer overflow Discovered in: URN (Uniform Resource Name) processing Impact: Possible remote code execution or denial-of-service, exploitable over the network with no authentication required
The flaw occurs during how Squid parses URN responses. Improper memory handling leads to heap overflows, meaning a malicious HTTP response could corrupt memory, potentially letting an attacker crash Squid or run arbitrary code.
| Metric | Detail |
|---|---|
| Attack Vector | Remote (over network) |
| Attack Complexity | Low |
| Privileges Required | None |
| User Interaction | None |
| Scope | Changed (can affect system) |
| Confidentiality | Not impacted |
| Integrity | Limited impact |
| Availability | High impact (DoS possible) |
To use your CVE-2025-54574.sh script safely and effectively on a Linux system (like Kali), follow these steps:
If you haven’t already saved it, create the script file:
nano CVE-2025-54574.sh
Paste your script into the editor, then save with CTRL+O, Enter, and exit with CTRL+X.
Give the script permission to run:
chmod +x CVE-2025-54574.sh
Because it modifies /etc/squid/squid.conf and restarts services, you must run it with sudo or as root:
sudo ./CVE-2025-54574.sh
Checks if your installed Squid version ≤ 6.3
If vulnerable:
/etc/squid/squid.conf.bak)sudo systemctl status squid
sudo squid -k parse
If you want to undo the script's changes, restore the backup config:
sudo cp /etc/squid/squid.conf.bak /etc/squid/squid.conf
sudo systemctl restart squid
/etc/squid/squid.conf (default path). If it’s somewhere else, update the script.bc is installed (used for version comparison). Install with:sudo apt install bc
This script and accompanying information are provided “as is” without any warranties or guarantees. Use this material at your own risk. The author(s) assume no responsibility for any damage, data loss, or service interruptions that may result from running or modifying this script.
It is strongly recommended to test all changes in a controlled environment before deploying to production. Always review configuration changes thoroughly and back up your data and settings prior to applying any fixes or mitigations.