Skip to content
KitploitKITPLOIT
ToolsExploitsBlog
Log in
Submit
ToolsExploitsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

FeedsContactPrivacy© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
Blackash-CVE-2025-54574 — Exploit script for CVE-2025-54574, a critical heap buffer overflow in Squid proxy (≤6.3) enabling remote code execution or denial-of-service with no authentication required. | Kitploit
Tools/GitHubGitHub/gmh5225/blackash-cve-2025-54574
Vulnerability AnalysisExploitationWeb SecurityPenetration TestingRemote Access Tool
GitHubgmh5225/blackash-cve-2025-54574

Blackash-CVE-2025-54574

Exploit script for CVE-2025-54574, a critical heap buffer overflow in Squid proxy (≤6.3) enabling remote code execution or denial-of-service with no authentication required.

View Repository
1281 year agoNot yet reviewed
Share

🛑 CVE-2025-54574 — Heap Buffer Overflow in Squid (≤ 6.3) 🛑

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


🔍 What’s the issue?

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.


✅ How to Fix It

  • Upgrade to Squid 6.4 or later. This version patches the vulnerability.
  • As a temporary mitigation, you can disable URN access in your Squid configuration.

🧯 Risk Breakdown

MetricDetail
Attack VectorRemote (over network)
Attack ComplexityLow
Privileges RequiredNone
User InteractionNone
ScopeChanged (can affect system)
ConfidentialityNot impacted
IntegrityLimited impact
AvailabilityHigh impact (DoS possible)

🕒 Timeline

  • Vulnerability announced: August 1, 2025
  • Patch released in: Squid 6.4 (released late July 2025)

🛡 What Should You Do?

  1. Check your current Squid version. If you’re on 6.3 or earlier, upgrade immediately.
  2. If you cannot upgrade right away, disable URN handling in Squid’s ACL or configuration.
  3. Keep your operating system's package manager up to date — patched versions may already be available.
  4. Review proxy logs for unusual behavior or exploitation attempts targeting URNs.

To use your CVE-2025-54574.sh script safely and effectively on a Linux system (like Kali), follow these steps:


✅ How to Use the Script

1. Save the Script

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.


2. Make It Executable

Give the script permission to run:

chmod +x CVE-2025-54574.sh

3. Run the Script as Root

Because it modifies /etc/squid/squid.conf and restarts services, you must run it with sudo or as root:

sudo ./CVE-2025-54574.sh

What it does:

  • Checks if your installed Squid version ≤ 6.3

  • If vulnerable:

    • Backs up your config file (/etc/squid/squid.conf.bak)
    • Adds rules to block URN access
    • Restarts Squid to apply changes

🧪 Optional: Test After Running

Check if Squid is running correctly:

sudo systemctl status squid

Look for syntax errors in the config (optional but good practice):

sudo squid -k parse

🔄 Optional: Revert Changes

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

📝 Notes:

  • Works only if your config is in /etc/squid/squid.conf (default path). If it’s somewhere else, update the script.
  • Make sure bc is installed (used for version comparison). Install with:
sudo apt install bc

⚠️ Disclaimer !!!

  • 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.

Download Tool

Most Popular

View all →

Discover the most used tools by our community.

  • 1

    OsintHunter

    letox4/osinthunter

    🎯 The ultimate OSINT toolkit: investigation graph, confidence scoring, alias families, map, timeline and reports. 49 modules, 400+ sites, no API keys required.

    916
  • 2

    ghostlock-app

    yukonga/ghostlock-app

    GhostLock One-Tap Execution App (CVE-2026-43499)

    558
  • 3

    redforge

    cybersecurity91/redforge

    Browser-side red team toolkit with 102 offline tools for recon, payload generation, credential attacks, crypto, encoding and engagement reporting.

    370
  • 4

    ARTEX

    baarai/artex

    LLM multi-agent autonomous penetration testing platform with planner/worker agents, asset and exploration graphs, MITM traffic recording, and vulnerability retesting.

    360
  • 5

    looking-glass

    anonghosty/looking-glass

    CSIRT platform that ingests Shadowserver reports into MongoDB and replays them as interactive maps, analysis, findings, advisories and executive dashboards.

    317
  • 6

    CyberStrikeAI

    ed1s0nz/cyberstrikeai

    The system of action for AI-native cybersecurity—where intent becomes governed execution, evidence becomes operational memory, and every operation improves the next.

    289

Explore all tools

Browse our collection of tools

View all tools →