CVE-2006-2233 json
Buffer overflow in BankTown Client Control (aka BtCxCtl20Com) 1.4.2.51817, and possibly 1.5.2.50209, allows remote attackers to execute arb…
published 2006-05-05 20 y ago modified 2026-06-16 4 mo ago also EUVD-2006-2234
- cvss
- 7.5
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 7.3%
- EPSS 7.3% chance of exploitation in 30 days, percentile 94%
- public exploits
- 1
- Exploit-DB
Summary
Buffer overflow in BankTown Client Control (aka BtCxCtl20Com) 1.4.2.51817, and possibly 1.5.2.50209, allows remote attackers to execute arbitrary code via a long string in the first argument to SetBannerUrl. NOTE: portions of these details are obtained from third party information.
Timeline
- First public exploit (EDB-27806)
- Published
Exploit prediction
7.31% chance of exploitation in the next 30 days, higher than 94% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-27806 BankTown ActiveX Control 1.4.2.51817/1.5.2.50209 - Remote Buffer Overflow remote, 2006-05-03
- securityfocus.com http://www.securityfocus.com/bid/17815 referenced PoC, tagged "exploit" by a source, unverified
- archives.neohapsis.com http://archives.neohapsis.com/archives/fulldisclosure/2006-05/0037.html referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
References
-
securityfocus.com
/bid/17815
vdb-entry, exploit
-
archives.neohapsis.com
/archives/fulldisclosure/2006-05/0037.html
mailing-list, exploit
-
secunia.com
/advisories/19942
third-party-advisory, vendor-advisory
-
securityreason.com
/securityalert/855
third-party-advisory
-
vupen.com
/english/advisories/2006/1638
vdb-entry
-
securityfocus.com
/archive/1/432862/100/0/threaded
mailing-list
-
securityfocus.com
/archive/1/433242/100/0/threaded
mailing-list
-
osvdb.org
/25212
vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/26214
vdb-entry
Sources
- CVE List CVE-2006-2233
- NVD CVE-2006-2233
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.