CVE-2006-0368 cisco call manager
cisco call manager: no CVSS score yet. EPSS 3.7% estimated probability of exploitation activity in the next 30 days.
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.
- EPSS
- 3.7% (unchanged from 3.7% a week ago; 3.7% 30 days ago) estimated probability of exploitation activity in the next 30 days; 90th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
- Published
- Modified
- NVD analysis
- Analyzed, since modified
- Record from
- the NVD, synced
Fix and patched versions
- Patch: http://secunia.com/advisories/18494
- Vendor advisory: http://secunia.com/advisories/18494
Ask an AI about this CVE
Show the prompt
Explain CVE-2006-0368 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2006-0368?via=ask-ai-copy and https://cve.bz/cve/CVE-2006-0368?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2006-0368 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Affected
Versions
From the NVD's CPE matches.
| Product | Affected |
|---|---|
| cisco:call_manager | 1.0 |
| cisco:call_manager | 2.0 |
| cisco:call_manager | 3.0 |
| cisco:call_manager | 3.1 |
| cisco:call_manager | 3.1(2) |
| cisco:call_manager | 3.1(3a) |
| cisco:call_manager | 3.2 |
| cisco:call_manager | 3.3 |
| cisco:call_manager | 3.3(3) |
| cisco:call_manager | 3.3(3)es61 |
| cisco:call_manager | 3.3(4)es25 |
| cisco:call_manager | 3.3(5) |
| cisco:call_manager | 3.3(5)es30 |
| cisco:call_manager | 4.0 |
| cisco:call_manager | 4.0(2a)es40 |
| cisco:call_manager | 4.0(2a)es62 |
| cisco:call_manager | 4.0(2a)sr2b |
| cisco:call_manager | 4.1(2)es33 |
| cisco:call_manager | 4.1(2)es55 |
| cisco:call_manager | 4.1(3)es07 |
| cisco:call_manager | 4.1(3)es32 |
| cisco:call_manager | 4.1(3)sr1 |
References
- http://secunia.com/advisories/18494
- http://securityreason.com/securityalert/359
- http://securitytracker.com/id?1015503
- http://www.cisco.com/warp/public/707/cisco-sa-20060118-ccmdos.shtml
- http://www.osvdb.org/22622
- http://www.osvdb.org/22623
- http://www.securityfocus.com/bid/16295
- http://www.vupen.com/english/advisories/2006/0249
- https://exchange.xforce.ibmcloud.com/vulnerabilities/24180