Cisco CallManager (CCM) is the software-based call-processing component of the Cisco IP telephony solution which extends enterprise telephony features and functions to packet telephony network devices such as IP phones, media processing devices, voice-over-IP (VoIP) gateways, and multimedia applications. Cisco CallManager 3.3 and earlier, 4.0, and 4.1 are vulnerable to Denial of Service (DoS) attacks, memory leaks, and memory corruption which may result in services being interrupted, servers rebooting, or arbitrary code being executed. Cisco has made free software available to address these vulnerabilities. This advisory will be posted at http://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20050712-ccm.
Cisco CallManager (CCM) is the software-based call-processing component of the Cisco IP telephony solution which extends enterprise telephony features and functions to packet telephony network devices such as IP phones, media processing devices, voice-over-IP (VoIP) gateways, and multimedia applications. Cisco CallManager 3.3 and earlier, 4.0, and 4.1 are vulnerable to Denial of Service (DoS) attacks, memory leaks, and memory corruption which may result in services being interrupted, servers rebooting, or arbitrary code being executed.
Cisco has made free software available to address these vulnerabilities.
This advisory will be posted at http://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20050712-ccm.
This section provides details on affected products.
These products are vulnerable:
No other Cisco products are currently known to be affected by these vulnerabilities.
This section provides detailed information about these vulnerabilities.
The effectiveness of any workaround is dependent on specific customer situations such as product mix, network topology, traffic behavior, and organizational mission. Due to the variety of affected products and releases, customers should consult with their service provider or support organization to ensure any applied workaround is the most appropriate for use in the intended network before it is deployed.
While there are no workarounds available on the Cisco CallManager to eliminate attacks, securing the voice network with Cisco CallManager security best practices may lessen the risk or mitigate the effects of these vulnerabilities. By using access lists to restrict access to the Cisco CallManager, the risk of successful attack is greatly reduced. Please refer to the SAFE: IP Telephony Security in Depth white paper located off the SAFE Blueprint http://www.cisco.com/go/safe introduction page. Also, Cisco provides Solution Reference Network Design (SRND) guides to help design and deploy networking solutions. http://www.cisco.com/warp/public/779/largeent/it/ese/srnd.html
The specific access list examples given below need to be tailored for each network's needs and added to the other access list entries in place. If you have gateways or other devices outside of the CallManager VLAN, you can configure specific ACL entries permitting access from those device IP addresses. See the list of CallManager ports used http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_tech_note09186a00801a62b9.shtml
When considering software upgrades, please also consult http://www.cisco.com/en/US/products/products_security_advisories_listing.html and any subsequent advisories to determine exposure and a complete upgrade solution.
In all cases, customers should exercise caution to be certain the devices to be upgraded contain sufficient memory and that current hardware and software configurations will continue to be supported properly by the new release. If the information is not clear, contact the Cisco Technical Assistance Center ("TAC") for assistance.
Each row of the Cisco CallManager software table (below) describes a release train which will address all of the vulnerabilities mentioned in this advisory. If a given release train is vulnerable, then the earliest possible releases that contain the fixes (the "First Fixed Release") and the anticipated date of availability for each are listed in the "Engineering Special," "Service Release," and "Maintenance Release" columns. A device running a Cisco CallManager release in the given train that is earlier than the release in a specific column (less than the First Fixed Release listed in the Engineering Special or Special Release columns) is known to be vulnerable to one or more issues. The Cisco CallManager should be upgraded at least to the indicated release or a later version (greater than or equal to the First Fixed Release label).
Train |
Engineering Special |
Service Release |
Maintenance Release |
---|---|---|---|
3.2 and earlier |
migrate to 3.3 or later |
||
3.3 |
3.3(3)ES61 3.3 (4)ES25 |
3.3(5) |
|
4.0 |
4.0(2a)ES40 |
4.0(2a)SR2b |
no release planned |
4.1 |
4.1(2)ES33 4.1 (3)ES07 |
4.1(3)SR1 |
no release planned |
The Cisco PSIRT is not aware of any public announcements or malicious use of the vulnerability described in this advisory.
The aupair service vulnerability (CSCsa75554) was reported to Cisco by Internet Security Systems who will also be making public announcements regarding this issue.
Jeff Fay from PatchAdvisor will issue a report on his findings of CSCee00116 on their vulnerability alert service.
To learn about Cisco security vulnerability disclosure policies and publications, see the Security Vulnerability Policy. This document also contains instructions for obtaining fixed software and receiving security vulnerability information from Cisco.
Revision 1.1 |
2005-July-18 |
Workaround section added example of restricting access to the Cisco Call Manager. |
Revision 1.0 |
2005-July-12 |
Initial public release. |
THIS DOCUMENT IS PROVIDED ON AN "AS IS" BASIS AND DOES NOT IMPLY ANY KIND OF GUARANTEE OR WARRANTY, INCLUDING THE WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR USE. YOUR USE OF THE INFORMATION ON THE DOCUMENT OR MATERIALS LINKED FROM THE DOCUMENT IS AT YOUR OWN RISK. CISCO RESERVES THE RIGHT TO CHANGE OR UPDATE THIS DOCUMENT AT ANY TIME.
A stand-alone copy or paraphrase of the text of this document that omits the distribution URL is an uncontrolled copy, and may lack important information or contain factual errors. The information in this document is intended for end-users of Cisco products.