A sandbox escape issue was discovered in TitanHQ SpamTitan Gateway 7.07.

published 2020-09-17 6y ago modified 2026-06-17 4mo ago also EUVD-2020-16781

cvss: 7.2; version 3.1, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 1.6%; EPSS 1.6% chance of exploitation in 30 days, percentile 75%
public exploits: 0; none known

A sandbox escape issue was discovered in TitanHQ SpamTitan Gateway 7.07. It limits the admin user to a restricted shell, allowing execution of a small number of tools of the operating system. The restricted shell can be bypassed by presenting a fake vmware-tools ISO image to the guest virtual machine running SpamTitan Gateway. This ISO image should contain a valid Perl script at the vmware-freebsd-tools/vmware-tools-distrib/vmware-install.pl path. The fake ISO image will be mounted and the script wmware-install.pl will be executed with super-user privileges as soon as the hidden option to install VMware Tools is selected in the main menu of the restricted shell (option number 5). The contents of the script can be whatever the attacker wants, including a backdoor or similar.

Is CVE-2020-24045 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

1.55% chance of exploitation in the next 30 days, higher than 75% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

sensepost.com https://sensepost.com/blog/2020/clash-of-the-spamtitan/ referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by	version	score	vector
NVD	3.1	7.2	CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
NVD	2.0	9.0	AV:N/AC:L/Au:S/C:C/I:C/A:C

Classification

Weakness

CWE-345 Insufficient Verification of Data Authenticity

References

sensepost.com /blog/2020/clash-of-the-spamtitan/
exploit, third-party-advisory
titanhq.com /
vendor-advisory
github.com /felmoltor
third-party-advisory
twitter.com /felmoltor
third-party-advisory

Sources

CVE List CVE-2020-24045
NVD CVE-2020-24045

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.