Cisco Security Advisory-
Hard-coded Simple Network Management Protocol (SNMP) community strings are present in Cisco IP/VC Videoconferencing System models 3510, 3520, 3525 and 3530. Any user who has access to the vulnerable devices and knows the community strings, can obtain total control of the device.
Cisco strongly recommends that all users deploy the mitigation measures outlined in the Workaround section.
This advisory is posted at https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20050202-ipvc.
-
Vulnerable Products
The following products are known to be vulnerable:
- Cisco IPVC-3510-MCU
- Cisco IPVC-3520-GW-2B
- Cisco IPVC-3520-GW-4B
- Cisco IPVC-3520-GW-2V
- Cisco IPVC-3520-GW-4V
- Cisco IPVC-3520-GW-2B2V
- Cisco IPVC-3525-GW-1P
- Cisco IPVC-3530-VTA
Products Confirmed Not Vulnerable
The following products are known not to be vulnerable:
- Cisco IPVC-3511-MCU
- Cisco IPVC-3511-MCU-E
- Cisco IPVC-3521-GW-4B
- Cisco IPVC-3526-GW-1P
- Cisco IPVC-3540-EMP
- Cisco IPVC-3540-EMP3
- Cisco IPVC-3540-MCU03A
- Cisco IPVC-3540-MCU06A
- Cisco IPVC-3540-MCU10A
- Cisco IPVC-3540-GW2P
- Cisco IPVC-3540-GW4S
No other Cisco products are currently known to be affected by this vulnerability. In particular, video-enabled Cisco IP video telephones are not affected.
-
Affected products contain hard-coded SNMP community strings. SNMP is used for managing and monitoring an IP/VC device and community strings are the equivalent to a password. All models listed as affected are vulnerable regardless of the software release they are running.
There is no Cisco bug ID associated with this issue.
-
The only mitigation for this vulnerability is to disable SNMP traffic at the switch port that is connected to the affected device. If that cannot be done, the SNMP traffic to the IP/VC device should be blocked at the nearest possible point. In order for the mitigation to be successful all possible paths to the device must be protected. This can be done by blocking traffic on UDP (User Datagram Protocol) ports 161 and 162. Port 161 is used for inbound/outbound read/write SNMP access and port 162 is used for outbound traffic for SNMP traps. Blocking these ports disables all configuration and traps to/from the device. Access to ports 161 and 162 from the trusted hosts should be temporarily enabled and the IPVC Configuration Utility used when configuration changes are required on the affected IP/VC device.
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.
-
Cisco will not provide fixed software for this vulnerability. Customers are strongly advised to deploy the mitigation measures described in the Workaround section.
-
The Cisco PSIRT is not aware of any public announcements or malicious use of the vulnerability described in this advisory.
-
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.
-
Show LessRevision 1.0
2005-February-02
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.