CVE-2025-1300

6.1 MEDIUM

📋 TL;DR

CodeChecker web server versions through 6.24.5 contain an open redirect vulnerability that allows attackers to redirect users to malicious websites. This occurs due to insufficient validation of multiple slashes in URLs, which bypasses previous security fixes. Organizations using vulnerable CodeChecker installations are affected.

💻 Affected Systems

Products:
  • CodeChecker
Versions: through 6.24.5
Operating Systems: All
Default Config Vulnerable: ⚠️ Yes
Notes: Only affects CodeChecker web server component; static analysis functionality remains unaffected.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Attackers could redirect authenticated users to phishing sites to steal credentials or deliver malware, potentially leading to full system compromise.

🟠

Likely Case

Attackers use the redirect in phishing campaigns to trick users into visiting malicious sites, potentially stealing session tokens or credentials.

🟢

If Mitigated

With proper network segmentation and user awareness training, impact is limited to potential phishing attempts that users should recognize.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ⚠️ Yes
Complexity: LOW

Exploitation requires user interaction (clicking a link) but is technically simple to execute.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 6.24.6 or later

Vendor Advisory: https://github.com/Ericsson/codechecker/security/advisories/GHSA-g839-x3p3-g5fm

Restart Required: Yes

Instructions:

1. Update CodeChecker to version 6.24.6 or later. 2. Restart the CodeChecker web server. 3. Verify the fix by testing the vulnerable URL pattern.

🔧 Temporary Workarounds

Web Server URL Filtering

all

Configure reverse proxy or web server to filter URLs with multiple slashes after the product name

# Example nginx configuration:
location ~* ^/codechecker//+ { return 403; }

Network Segmentation

linux

Restrict access to CodeChecker web interface to trusted networks only

# Example firewall rule (iptables):
iptables -A INPUT -p tcp --dport 8001 -s trusted_network -j ACCEPT
iptables -A INPUT -p tcp --dport 8001 -j DROP

🧯 If You Can't Patch

  • Implement strict Content Security Policy (CSP) headers to restrict redirect destinations
  • Deploy web application firewall (WAF) rules to detect and block open redirect attempts

🔍 How to Verify

Check if Vulnerable:

Test if accessing http://[codechecker-host]/codechecker//example.com redirects to example.com

Check Version:

codechecker-server --version

Verify Fix Applied:

After patching, the same test URL should return an error or normal page instead of redirecting

📡 Detection & Monitoring

Log Indicators:

  • HTTP 302 redirect responses with external domains in Location header
  • URLs containing multiple slashes after '/codechecker/'

Network Indicators:

  • Outbound HTTP requests from CodeChecker server to unexpected domains following redirect patterns

SIEM Query:

source="codechecker" AND (url="*//*" OR status=302)

🔗 References

📤 Share & Export