CVE-2005-2242
Description
Cisco CallManager (CCM) 3.2 and earlier, 3.3 before 3.3(5), 4.0 before 4.0(2a)SR2b, and 4.1 4.1 before 4.1(3)SR1 allows remote attackers to cause a denial of service (memory consumption and restart) via crafted packets to (1) the CTI Manager (ctimgr.exe) or (2) the CallManager (ccm.exe).
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
Cisco CallManager versions before specific patches are vulnerable to denial of service via crafted packets to CTI Manager or CallManager, causing memory consumption and restart.
Vulnerability
Cisco CallManager (CCM) versions 3.2 and earlier, 3.3 before 3.3(5), 4.0 before 4.0(2a)SR2b, and 4.1 before 4.1(3)SR1 are vulnerable to a denial of service condition. The vulnerability exists in the CTI Manager (ctimgr.exe) and CallManager (ccm.exe) components. An attacker can send crafted packets to these services, leading to excessive memory consumption and subsequent restart of the affected service. [1]
Exploitation
An attacker with network access to the affected Cisco CallManager system can exploit this vulnerability by sending specially crafted packets to the CTI Manager or CallManager services. No authentication is required. The attacker simply needs to send the malicious packets to the appropriate ports (typically TCP 2748 for CTI Manager and TCP 2000 for CallManager, though not specified in the description). The crafted packets trigger a memory leak or memory allocation error, causing the service to consume all available memory and eventually crash or restart. [1]
Impact
Successful exploitation results in a denial of service (DoS) condition. The affected service (CTI Manager or CallManager) will consume excessive memory and restart, disrupting voice communications and call processing. This can lead to complete loss of telephony services until the service recovers or is manually restarted. The impact is limited to availability; no data confidentiality or integrity is compromised. [1]
Mitigation
Cisco has released fixed versions: 3.3(5), 4.0(2a)SR2b, and 4.1(3)SR1. Users should upgrade to these or later versions. For versions 3.2 and earlier, no fix is mentioned; they are likely end-of-life and should be upgraded to a supported version. Workarounds may include restricting network access to the affected services via access control lists. The vulnerability is not listed on CISA's Known Exploited Vulnerabilities catalog as of the publication date. [1]
AI Insight generated on May 24, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected products
1- Range: 3.2 and earlier, 3.3 before 3.3(5), 4.0 before 4.0(2a)SR2b, 4.1 before 4.1(3)SR1
Patches
0No patches discovered yet.
Vulnerability mechanics
AI mechanics synthesis has not run for this CVE yet.
References
3News mentions
0No linked articles in our index yet.