Skip to content
Fencer Vulns
critical 9.3

CVE-2008-1724 in the critical feed json

Stack-based buffer overflow in the IActiveXTransfer.FileTransfer method in the SecureTransport FileTransfer ActiveX control in vcst_en.dll…

published 2008-04-11 18 y ago modified 2026-06-16 4 mo ago also EUVD-2008-1725

cvss
9.3
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
35.1%
EPSS 35.1% chance of exploitation in 30 days, percentile 98%
public exploits
3
Metasploit, Exploit-DB

Summary

Stack-based buffer overflow in the IActiveXTransfer.FileTransfer method in the SecureTransport FileTransfer ActiveX control in vcst_en.dll 1.0.0.5 in Tumbleweed SecureTransport Server before 4.6.1 Hotfix 20 allows remote attackers to execute arbitrary code via a long remoteFile parameter.

Timeline

  1. First public exploit (Metasploit exploit/windows/browser/tumbleweed_filetransfer)
  2. Published

Exploit prediction

35.13% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • Metasploit exploit/windows/browser/tumbleweed_filetransfer Tumbleweed FileTransfer vcst_eu.dll ActiveX Control Buffer Overflow metasploit exploit, great rank, 2008-04-07
  • EDB-16563 Tumbleweed SecureTransport FileTransfer - 'vcst_eu.dll' ActiveX Control Buffer Overflow (Metasploit) remote, 2010-06-15
  • EDB-5398 Tumbleweed SecureTransport 4.6.1 FileTransfer - ActiveX Buffer Overflow remote, 2008-04-07
  • securityreason.com http://securityreason.com/securityalert/3806 referenced PoC, tagged "exploit" by a source, unverified
  • securityfocus.com http://www.securityfocus.com/bid/28662 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 2.0 9.3 AV:N/AC:M/Au:N/C:C/I:C/A:C

Classification

Weakness
  • CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer

References

Sources

Fencer Vulns 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.