First published: Sun Jan 22 2006(Updated: )
Cisco CallManager 3.2 and earlier, 3.3 before 3.3(5)SR1, 4.0 before 4.0(2a)SR2c, and 4.1 before 4.1(3)SR2 allow remote attackers to (1) cause a denial of service (CPU and memory consumption) via a large number of open TCP connections to port 2000 and (2) cause a denial of service (fill the Windows Service Manager communication queue) via a large number of TCP connections to port 2001, 2002, or 7727.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
Cisco Call Manager | =4.1\(3\)es07 | |
Cisco Call Manager | =3.0 | |
Cisco Call Manager | =3.1\(3a\) | |
Cisco Call Manager | =4.1\(3\)es32 | |
Cisco Call Manager | =1.0 | |
Cisco Call Manager | =3.3\(5\) | |
Cisco Call Manager | =4.1\(3\)sr1 | |
Cisco Call Manager | =3.3\(3\)es61 | |
Cisco Call Manager | =3.3\(4\)es25 | |
Cisco Call Manager | =3.3\(5\)es30 | |
Cisco Call Manager | =3.2 | |
Cisco Call Manager | =3.1\(2\) | |
Cisco Call Manager | =4.0\(2a\)es40 | |
Cisco Call Manager | =3.3 | |
Cisco Call Manager | =2.0 | |
Cisco Call Manager | =4.1\(2\)es55 | |
Cisco Call Manager | =4.0\(2a\)es62 | |
Cisco Call Manager | =3.1 | |
Cisco Call Manager | ||
Cisco Call Manager | =4.0 | |
Cisco Call Manager | =4.1\(2\)es33 | |
Cisco Call Manager | =3.3\(3\) | |
Cisco Call Manager | =4.0\(2a\)sr2b |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.