CVE-2009-3853 in the critical feed json
Stack-based buffer overflow in the client acceptor daemon (CAD) scheduler in the client in IBM Tivoli Storage Manager (TSM) 5.3 before 5.3.…
published 2009-11-04 17 y ago modified 2026-06-16 4 mo ago also EUVD-2009-3824
- cvss
- 9.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 36.7%
- EPSS 36.7% chance of exploitation in 30 days, percentile 98%
- public exploits
- 2
- Metasploit, Exploit-DB
Summary
Stack-based buffer overflow in the client acceptor daemon (CAD) scheduler in the client in IBM Tivoli Storage Manager (TSM) 5.3 before 5.3.6.7, 5.4 before 5.4.3, 5.5 before 5.5.2.2, and 6.1 before 6.1.0.2, and TSM Express 5.3.3.0 through 5.3.6.6, allows remote attackers to execute arbitrary code via crafted data in a TCP packet.
Patch / fix
Timeline
- First public exploit (Metasploit exploit/windows/misc/ibm_tsm_cad_ping)
- Published
Exploit prediction
36.72% 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/misc/ibm_tsm_cad_ping IBM Tivoli Storage Manager Express CAD Service Buffer Overflow metasploit exploit, good rank, 2009-11-04
- EDB-16421 IBM Tivoli Storage Manager Express CAD Service - Remote Buffer Overflow (Metasploit) (1) remote, 2010-05-09
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
-
vupen.com
/english/advisories/2009/3132
vdb-entry, patch, vendor-advisory
-
www-01.ibm.com
/support/docview.wss?uid=swg21405562
patch, vendor-advisory
-
www-01.ibm.com
/support/docview.wss?uid=swg1IC61036
vendor-advisory
-
securitytracker.com
/id?1023136
vdb-entry
-
securityfocus.com
/archive/1/507654/100/0/threaded
mailing-list
- secunia.com /secunia_research/2008-51/
-
secunia.com
/advisories/32534
third-party-advisory
Sources
- CVE List CVE-2009-3853
- NVD CVE-2009-3853
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.