CVE-2024-45438

9.1 CRITICAL

📋 TL;DR

CVE-2024-45438 is an authentication bypass vulnerability in TitanHQ SpamTitan Email Security Gateway that allows unauthenticated attackers to create user accounts and modify quarantine settings via crafted GET requests. This affects organizations using vulnerable versions of SpamTitan Email Security Gateway. The vulnerability enables unauthorized account creation and configuration changes without any authentication.

💻 Affected Systems

Products:
  • TitanHQ SpamTitan Email Security Gateway
Versions: 8.00.x before 8.00.101 and 8.01.x before 8.01.14
Operating Systems: All supported platforms for SpamTitan
Default Config Vulnerable: ⚠️ Yes
Notes: All deployments with the vulnerable versions are affected regardless of configuration. The quarantine.php endpoint is accessible by default.

⚠️ Manual Verification Required

This CVE does not have specific version information in our database, so automatic vulnerability detection cannot determine if your system is affected.

Why? The CVE database entry doesn't specify which versions are vulnerable (no version ranges provided by the vendor/NVD).

🔒 Custom verification scripts are available for registered users. Sign up free to download automated test scripts.

Recommended Actions:
  1. Review the CVE details at NVD
  2. Check vendor security advisories for your specific version
  3. Test if the vulnerability is exploitable in your environment
  4. Consider updating to the latest version as a precaution

⚠️ Risk & Real-World Impact

🔴

Worst Case

Attackers create administrative accounts, modify email filtering rules to bypass security controls, redirect or delete legitimate emails, and potentially gain persistent access to the email security infrastructure.

🟠

Likely Case

Attackers create unauthorized user accounts to bypass spam filtering, modify quarantine settings to release malicious emails, or disrupt email security operations.

🟢

If Mitigated

With proper network segmentation and access controls, impact is limited to the SpamTitan appliance itself, though unauthorized configuration changes could still affect email security.

🌐 Internet-Facing: HIGH - The vulnerability is exploitable via unauthenticated HTTP requests, making internet-facing instances immediately vulnerable to remote attacks.
🏢 Internal Only: HIGH - Even internally deployed instances are vulnerable to any network-accessible attacker, including compromised internal hosts or malicious insiders.

🎯 Exploit Status

Public PoC: ⚠️ Yes
Weaponized: LIKELY
Unauthenticated Exploit: ⚠️ Yes
Complexity: LOW

Exploitation requires only HTTP GET requests to the vulnerable endpoint with crafted parameters. Public disclosure includes technical details sufficient for exploitation.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 8.00.101 or 8.01.14

Vendor Advisory: https://docs.titanhq.com/en/13161-spamtitan-release-notes.html

Restart Required: Yes

Instructions:

1. Backup current configuration. 2. Download the patched version from TitanHQ support portal. 3. Apply the update through the SpamTitan web interface. 4. Restart the SpamTitan service. 5. Verify the update completed successfully.

🔧 Temporary Workarounds

Network Access Restriction

all

Restrict access to the SpamTitan web interface to trusted IP addresses only

Configure firewall rules to allow only administrative networks to access SpamTitan web interface ports (typically 80/443)

Web Server Configuration

linux

Add authentication requirements to the quarantine.php endpoint

Add location block in nginx: location ~* /quarantine\.php$ { auth_basic "Restricted"; auth_basic_user_file /etc/nginx/.htpasswd; }
Add Directory block in Apache: <Location "/quarantine.php"> AuthType Basic AuthName "Restricted" Require valid-user </Location>

🧯 If You Can't Patch

  • Implement strict network segmentation to isolate SpamTitan management interface from untrusted networks
  • Deploy a web application firewall (WAF) with rules to block requests to quarantine.php with email parameter containing non-existent addresses

🔍 How to Verify

Check if Vulnerable:

Check if HTTP GET requests to /quarantine.php with email parameter containing a non-existent address result in successful response without authentication. Monitor for unexpected user account creation in logs.

Check Version:

Login to SpamTitan web interface and check version in System Status or About page, or run: grep 'Version' /usr/local/spamtitan/etc/version.txt

Verify Fix Applied:

After patching, attempt the same unauthenticated request and verify it fails with proper authentication requirement. Check that no new user accounts are created.

📡 Detection & Monitoring

Log Indicators:

  • Unauthenticated access to /quarantine.php in web server logs
  • Unexpected user account creation events in SpamTitan audit logs
  • GET requests with email parameter containing unusual or non-existent addresses

Network Indicators:

  • HTTP GET requests to /quarantine.php from untrusted sources
  • Unusual patterns of requests to the quarantine endpoint

SIEM Query:

source="spamtitan" AND (uri="/quarantine.php" AND NOT user_agent="*admin*" AND status=200) OR (event_type="user_creation" AND source_ip NOT IN trusted_networks)

🔗 References

📤 Share & Export