CVE-2024-45438
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn issue was discovered in TitanHQ SpamTitan Email Security Gateway 8.00.x before 8.00.101 and 8.01.x before 8.01.14. The file quarantine.php within the SpamTitan interface allows unauthenticated users to trigger account-level actions using a crafted GET request. Notably, when a non-existent email address is provided as part of the email parameter, SpamTitan will automatically create a user record and associate quarantine settings with it - all without requiring authentication.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe quarantine.php file in TitanHQ SpamTitan Email Security Gateway versions 8.00.x before 8.00.101 and 8.01.x before 8.01.14 contains an authentication bypass vulnerability. Attackers can send a crafted GET request with a non-existent email address to automatically create a user record and associate quarantine settings without any authentication, effectively creating unauthorized accounts in the system.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Determine installed SpamTitan versionAccess the SpamTitan admin interface and navigate to System > About or check the /etc/version file via CLI if you have shell accessAffected if The version is 8.00.x before 8.00.101 OR 8.01.x before 8.01.14
-
Verify quarantine.php is accessibleAttempt to access the quarantine.php endpoint via HTTP/HTTPS from an unauthorized network location: curl http(s)://<hostname>/quarantine.phpAffected if The page loads or responds without requiring authentication credentials
-
Check for unauthorized user account creationReview the SpamTitan user database or admin panel for newly created user accounts, particularly those with email addresses you do not recognizeAffected if Unexpected user accounts exist that were not created through legitimate admin processes
-
Examine access logs for exploit patternsSearch web server access logs (typically in /var/log/httpd or /var/log/nginx) for GET requests to quarantine.php containing non-existent email addresses, e.g., grep 'quarantine.php' access.log | grep -E '[a-zA-Z0-9]+@[a-zA-Z0-9]+\.[a-zA-Z]{2,}'Affected if Logs show GET requests to quarantine.php with random or unknown email addresses that resulted in HTTP 200 responses without prior authentication
You are affected if your SpamTitan version is 8.00.x before 8.00.101 or 8.01.x before 8.01.14 AND the quarantine.php endpoint is externally accessible or has been accessed without authentication.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade SpamTitan to version 8.00.101 or 8.01.14 or later to apply the vendor patch. Alternatively, restrict network access to the SpamTitan management interface using firewall rules or VPN access until the upgrade can be performed.
8.00.101 (for 8.00.x branch) or 8.01.14 (for 8.01.x branch)
- Identify the currently installed SpamTitan Email Security Gateway version by checking the web interface or system information
- If running 8.00.x, upgrade to version 8.00.101 or later
- If running 8.01.x, upgrade to version 8.01.14 or later
- After upgrading, verify the fix by attempting to access quarantine.php without authentication - the request should be rejected
- Review administrator accounts to ensure no unauthorized user accounts were created during any exploitation attempts
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,288.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-45438 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-45438 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data