VAR-200909-0382
Vulnerability from variot - Updated: 2025-04-10 20:45Buffer overflow in the login implementation in the Extension Mobility feature in the Unified Communications Manager Express (CME) component in Cisco IOS 12.4XW, 12.4XY, 12.4XZ, and 12.4YA allows remote attackers to execute arbitrary code or cause a denial of service via crafted HTTP requests, aka Bug ID CSCsq58779. Attackers can exploit this issue to execute arbitrary code or to cause denial-of-service conditions. This issue is documented by Cisco Bug ID CSCsq58779. ----------------------------------------------------------------------
Do you have VARM strategy implemented?
(Vulnerability Assessment Remediation Management)
If not, then implement it through the most reliable vulnerability intelligence source on the market.
Implement it through Secunia.
For more information visit: http://secunia.com/advisories/business_solutions/
Alternatively request a call from a Secunia representative today to discuss how we can help you with our capabilities contact us at: sales@secunia.com
TITLE: Cisco IOS Multiple Vulnerabilities
SECUNIA ADVISORY ID: SA36835
VERIFY ADVISORY: http://secunia.com/advisories/36835/
DESCRIPTION: Some vulnerabilities have been reported in Cisco IOS, which can be exploited by malicious people to cause a DoS (Denial of Service), bypass certain security restrictions, disclose sensitive information, or compromise a vulnerable device. This can be exploited to cause a buffer overflow via specially crafted HTTP requests.
2) An error in the IKE implementation can be exploited to allocate all available Phase 1 SAs and prevent new IPSec sessions from being established.
Successful exploitation requires that the IKE certificate based authentication method is used.
3) Multiple errors exist in the IP tunnelling implementation when switching network packets. These can be exploited to trigger a device reload via specially crafted packets.
Successful exploitation requires that the device is configured for PPTP, GRE, IPinIP, Generic Packet Tunneling in IPv6, or IPv6 over IP tunnels, and Cisco Express Forwarding.
4) An error in the implementation of the Object Groups for ACLs feature can be exploited to bypass access control policies.
5) An error in the H.323 implementation can be exploited to trigger a device reload via specially crafted TCP packets.
6) An error in the SIP implementation related to the Cisco Unified Border Element feature can be exploited to trigger a device reload.
For more information: SA36836
7) An error in the SSLVPN, SSH, and IKE Encrypted Nonces features can be exploited to reload a device via specially crafted packets sent to TCP ports 22 (for SSH) or 443 (for SSLVPN), or UDP ports 500 and 4500 (for IKE Encrypted Nonces).
8) A race condition error exists in the Authentication Proxy for HTTP(S), Web Authentication, and consent features. This can be exploited to bypass the authentication proxy services and the consent accept web page if a successfully authenticated session or accepted consent session exists.
9) An error exists in the Cisco IOS Zone-Based Policy Firewall SIP inspection feature. This can be exploited to reload a device via a specially crafted SIP transit packet.
10) An error exists in the NTPv4 implementation while creating NTP reply packets. This can be exploited to trigger a device reload via a specially crafted NTP packet.
SOLUTION: Update to a fixed version (please see the vendor's advisories for details).
PROVIDED AND/OR DISCOVERED BY: 1, 3-10) Reported by the vendor. 2) Reported to the vendor by a customer.
ORIGINAL ADVISORY: http://www.cisco.com/warp/public/707/cisco-sa-20090923-cme.shtml http://www.cisco.com/warp/public/707/cisco-sa-20090923-ipsec.shtml http://www.cisco.com/warp/public/707/cisco-sa-20090923-tunnels.shtml http://www.cisco.com/warp/public/707/cisco-sa-20090923-acl.shtml http://www.cisco.com/warp/public/707/cisco-sa-20090923-h323.shtml http://www.cisco.com/warp/public/707/cisco-sa-20090923-sip.shtml http://www.cisco.com/warp/public/707/cisco-sa-20090923-tls.shtml http://www.cisco.com/warp/public/707/cisco-sa-20090923-auth-proxy.shtml http://www.cisco.com/warp/public/707/cisco-sa-20090923-ios-fw.shtml http://www.cisco.com/warp/public/707/cisco-sa-20090923-ntp.shtml
OTHER REFERENCES: SA36836: http://secunia.com/advisories/36836/
About: This Advisory was delivered by Secunia as a free service to help everybody keeping their systems up to date against the latest vulnerabilities.
Subscribe: http://secunia.com/advisories/secunia_security_advisories/
Definitions: (Criticality, Where etc.) http://secunia.com/advisories/about_secunia_advisories/
Please Note: Secunia recommends that you verify all advisories you receive by clicking the link. Secunia NEVER sends attached files with advisories. Secunia does not advise people to install third party patches, only use those supplied by the vendor.
Unsubscribe: Secunia Security Advisories http://secunia.com/sec_adv_unsubscribe/?email=packet%40packetstormsecurity.org
.
Cisco has released free software updates that address this vulnerability.
This advisory is posted at:
http://www.cisco.com/warp/public/707/cisco-sa-20090923-cme.shtml
Note: The September 23, 2009, Cisco IOS Security Advisory bundled publication includes eleven Security Advisories. Each advisory lists the releases that correct the vulnerability or vulnerabilities detailed in the advisory. The following table lists releases that correct all Cisco IOS Software vulnerabilities that have been published on September 23, 2009, or earlier. logout-profile [logout-profile tag]
To determine the Cisco IOS Software release that is running on a Cisco product, administrators can log in to the device and issue the "show version" command to display the system banner. The system banner confirms that the device is running Cisco IOS Software by displaying text similar to "Cisco Internetwork Operating System Software" or "Cisco IOS Software." The image name is displayed in parentheses, followed by "Version" and the Cisco IOS Software release name. Other Cisco devices do not have the "show version" command or may provide different output.
The following example identifies a Cisco product that is running Cisco IOS Software Release 12.3(26) with an installed image name of C2500-IS-L:
Router#show version
Cisco Internetwork Operating System Software
IOS (tm) 2500 Software (C2500-IS-L), Version 12.3(26), RELEASE SOFTWARE (fc2)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2008 by cisco Systems, Inc.
Compiled Mon 17-Mar-08 14:39 by dchih
<output truncated>
The following example identifies a Cisco product that is running Cisco IOS Software Release 12.4(20)T with an installed image name of C1841-ADVENTERPRISEK9-M:
Router#show version
Cisco IOS Software, 1841 Software (C1841-ADVENTERPRISEK9-M), Version 12.4(20)T, RELEASE SOFTWARE (fc3)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2008 by Cisco Systems, Inc.
Compiled Thu 10-Jul-08 20:25 by prod_rel_team
<output truncated>
Additional information about Cisco IOS Software release naming conventions is available in "White Paper: Cisco IOS Reference Guide" at the following link: http://www.cisco.com/warp/public/620/1.html .
Cisco IOS XR is not affected.
Cisco IOS XE is not affected.
Cisco Unified Communications Manager is not affected.
No other Cisco products are currently known to be affected by these vulnerabilities.
Details
Cisco Unified CME is the call processing component of an enhanced IP telephony solution that is integrated into Cisco IOS. A user login service allows phone users to temporarily access a physical phone other than their own phone and utilize their personal settings, such as directory number, speed-dial lists, and services, that is assigned to their own desk phone. The phone user can make and receive calls on that phone using the same personal directory number as is on their own desk phone. Such packets can only come from registered phone IP addresses in the form of HTTP requests. If the auto-registration feature is enabled, an attacker can register its IP address and subsequently send a crafted payload to exploit this vulnerability. The auto-registration feature is enabled by default. More information on auto-registration can be found at the following link:
http://www.cisco.com/en/US/docs/voice_ip_comm/cucme/command/reference/cme_a1ht.html#wp1031242.
Vulnerability Scoring Details
Cisco has provided scores for the vulnerabilities in this advisory based on the Common Vulnerability Scoring System (CVSS). The CVSS scoring in this Security Advisory is done in accordance with CVSS version 2.0.
CVSS is a standards-based scoring method that conveys vulnerability severity and helps determine urgency and priority of response.
Cisco has provided a base and temporal score. Customers can then compute environmental scores to assist in determining the impact of the vulnerability in individual networks.
Cisco has provided an FAQ to answer additional questions regarding CVSS at:
http://www.cisco.com/web/about/security/intelligence/cvss-qandas.html
Cisco has also provided a CVSS calculator to help compute the environmental impact for individual networks at:
http://intellishield.cisco.com/security/alertmanager/cvss
CSCsq58779 - Vulnerability in Extension Mobility Feature
CVSS Base Score - 7.6
Access Vector - Network Access Complexity - High Authentication - None Confidentiality Impact - Complete Integrity Impact - Complete Availability Impact - Complete
CVSS Temporal Score - 6.3
Exploitability - Functional Remediation Level - Official-Fix Report Confidence - Confirmed
Impact
Successful exploitation of this vulnerability may result in the execution of arbitrary code or a Denial of Service (DoS) condition on an affected device.
Software Versions and Fixes
When considering software upgrades, also consult:
http://www.cisco.com/go/psirt
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) or your contracted maintenance provider for assistance.
Each row of the Cisco IOS software table (below) names a Cisco IOS release train. If a given release train is vulnerable, then the earliest possible releases that contain the fix (along with the anticipated date of availability for each, if applicable) are listed in the "First Fixed Release" column of the table. The "Recommended Release" column indicates the releases which have fixes for all the published vulnerabilities at the time of this Advisory. A device running a release in the given train that is earlier than the release in a specific column (less than the First Fixed Release) is known to be vulnerable. Cisco recommends upgrading to a release equal to or later than the release in the "Recommended Releases" column of the table.
+-------------------------------------------------------------------+ | Major Release | Availability of Repaired Releases | |----------------------+--------------------------------------------| | Affected 12.0-Based | First Fixed | Recommended Release | | Releases | Release | | |-------------------------------------------------------------------| | There are no affected 12.0 based releases. | |-------------------------------------------------------------------| | Affected 12.1-Based | First Fixed | Recommended Release | | Releases | Release | | |-------------------------------------------------------------------| | There are no affected 12.1 based releases. | |-------------------------------------------------------------------| | Affected 12.2-Based | First Fixed | Recommended Release | | Releases | Release | | |-------------------------------------------------------------------| | There are no affected 12.2 based releases. | |-------------------------------------------------------------------| | Affected 12.3-Based | First Fixed | Recommended Release | | Releases | Release | | |-------------------------------------------------------------------| | There are no affected 12.3 based releases. | |-------------------------------------------------------------------| | Affected 12.4-Based | First Fixed | Recommended Release | | Releases | Release | | |----------------------+---------------+----------------------------| | 12.4 | Not | | | | Vulnerable | | |----------------------+---------------+----------------------------| | 12.4GC | Not | | | | Vulnerable | | |----------------------+---------------+----------------------------| | 12.4JA | Not | | | | Vulnerable | | |----------------------+---------------+----------------------------| | 12.4JDA | Not | | | | Vulnerable | | |----------------------+---------------+----------------------------| | 12.4JDC | Not | | | | Vulnerable | | |----------------------+---------------+----------------------------| | 12.4JDD | Not | | | | Vulnerable | | |----------------------+---------------+----------------------------| | 12.4JK | Not | | | | Vulnerable | | |----------------------+---------------+----------------------------| | 12.4JL | Not | | | | Vulnerable | | |----------------------+---------------+----------------------------| | 12.4JMA | Not | | | | Vulnerable | | |----------------------+---------------+----------------------------| | 12.4JMB | Not | | | | Vulnerable | | |----------------------+---------------+----------------------------| | 12.4JX | Not | | | | Vulnerable | | |----------------------+---------------+----------------------------| | 12.4MD | Not | | | | Vulnerable | | |----------------------+---------------+----------------------------| | 12.4MDA | Not | | | | Vulnerable | | |----------------------+---------------+----------------------------| | 12.4MR | Not | | | | Vulnerable | | |----------------------+---------------+----------------------------| | 12.4SW | Not | | | | Vulnerable | | |----------------------+---------------+----------------------------| | 12.4T | Not | | | | Vulnerable | | |----------------------+---------------+----------------------------| | 12.4XA | Not | | | | Vulnerable | | |----------------------+---------------+----------------------------| | 12.4XB | Not | | | | Vulnerable | | |----------------------+---------------+----------------------------| | 12.4XC | Not | | | | Vulnerable | | |----------------------+---------------+----------------------------| | 12.4XD | Not | | | | Vulnerable | | |----------------------+---------------+----------------------------| | 12.4XE | Not | | | | Vulnerable | | |----------------------+---------------+----------------------------| | 12.4XF | Not | | | | Vulnerable | | |----------------------+---------------+----------------------------| | 12.4XG | Not | | | | Vulnerable | | |----------------------+---------------+----------------------------| | 12.4XJ | Not | | | | Vulnerable | | |----------------------+---------------+----------------------------| | 12.4XK | Not | | | | Vulnerable | | |----------------------+---------------+----------------------------| | 12.4XL | Not | | | | Vulnerable | | |----------------------+---------------+----------------------------| | 12.4XM | Not | | | | Vulnerable | | |----------------------+---------------+----------------------------| | 12.4XN | Not | | | | Vulnerable | | |----------------------+---------------+----------------------------| | 12.4XP | Not | | | | Vulnerable | | |----------------------+---------------+----------------------------| | 12.4XQ | Not | | | | Vulnerable | | |----------------------+---------------+----------------------------| | 12.4XR | Not | | | | Vulnerable | | |----------------------+---------------+----------------------------| | 12.4XT | Not | | | | Vulnerable | | |----------------------+---------------+----------------------------| | 12.4XV | Not | | | | Vulnerable | | |----------------------+---------------+----------------------------| | | | 12.4(20)T4 | | | | | | 12.4XW | 12.4(11)XW8 | 12.4(22)T3 | | | | | | | | 12.4(24)T2; Available on | | | | 23-OCT-2009 | |----------------------+---------------+----------------------------| | | | 12.4(20)T4 | | | | | | 12.4XY | 12.4(15)XY4 | 12.4(22)T3 | | | | | | | | 12.4(24)T2; Available on | | | | 23-OCT-2009 | |----------------------+---------------+----------------------------| | | | 12.4(20)T4 | | | | | | 12.4XZ | 12.4(15)XZ1 | 12.4(22)T3 | | | | | | | | 12.4(24)T2; Available on | | | | 23-OCT-2009 | |----------------------+---------------+----------------------------| | | | 12.4(20)T4 | | | | | | 12.4YA | 12.4(20)YA1 | 12.4(22)T3 | | | | | | | | 12.4(24)T2; Available on | | | | 23-OCT-2009 | |----------------------+---------------+----------------------------| | 12.4YB | Not | | | | Vulnerable | | |----------------------+---------------+----------------------------| | 12.4YD | Not | | | | Vulnerable | | |----------------------+---------------+----------------------------| | 12.4YE | Not | | | | Vulnerable | | +-------------------------------------------------------------------+
Workarounds
There are no workarounds to mitigate this vulnerability, other than disabling Extension Mobility. However, auto-registration can be disabled to make exploitation more difficult. Auto-registration can be disabled by the following command:
telephony-service
no auto-reg-ephone
Before disabling auto-registration, all phone MAC addresses need to be explicitly defined on the Cisco Unified CME. Otherwise phones will not be able to register. More information on auto-registration can be found at the following link:
http://www.cisco.com/en/US/docs/voice_ip_comm/cucme/command/reference/cme_a1ht.html#wp1031242
Additional mitigations that can be deployed on Cisco devices in the network are available in the Cisco Applied Mitigation Bulletin companion document for this advisory, which is available at the following link:
http://www.cisco.com/warp/public/707/cisco-amb-20090923-cme.shtml
Obtaining Fixed Software
Cisco has released free software updates that address these vulnerabilities. Prior to deploying software, customers should consult their maintenance provider or check the software for feature set compatibility and known issues specific to their environment.
Customers may only install and expect support for the feature sets they have purchased. By installing, downloading, accessing or otherwise using such software upgrades, customers agree to be bound by the terms of Cisco's software license terms found at:
http://www.cisco.com/en/US/docs/general/warranty/English/EU1KEN_.html
or as otherwise set forth at Cisco.com Downloads at:
http://www.cisco.com/public/sw-center/sw-usingswc.shtml
Do not contact psirt@cisco.com or security-alert@cisco.com for software upgrades.
Customers with Service Contracts +-------------------------------
Customers with contracts should obtain upgraded software through their regular update channels. For most customers, this means that upgrades should be obtained through the Software Center on Cisco's worldwide website at http://www.cisco.com.
Customers using Third Party Support Organizations +------------------------------------------------
Customers whose Cisco products are provided or maintained through prior or existing agreements with third-party support organizations, such as Cisco Partners, authorized resellers, or service providers should contact that support organization for guidance and assistance with the appropriate course of action in regards to this advisory.
The effectiveness of any workaround or fix 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 or fix is the most appropriate for use in the intended network before it is deployed.
Customers without Service Contracts +----------------------------------
Customers who purchase direct from Cisco but do not hold a Cisco service contract, and customers who purchase through third-party vendors but are unsuccessful in obtaining fixed software through their point of sale should acquire upgrades by contacting the Cisco Technical Assistance Center (TAC). TAC contacts are as follows.
- +1 800 553 2447 (toll free from within North America)
- +1 408 526 7209 (toll call from anywhere in the world)
- e-mail: tac@cisco.com
Customers should have their product serial number available and be prepared to give the URL of this notice as evidence of entitlement to a free upgrade. Free upgrades for non-contract customers must be requested through the TAC.
Refer to:
http://www.cisco.com/en/US/support/tsd_cisco_worldwide_contacts.html
for additional TAC contact information, including localized telephone numbers, and instructions and e-mail addresses for use in various languages.
Exploitation and Public Announcements
The Cisco PSIRT is not aware of any public announcements or malicious use of the vulnerability described in this advisory.
This vulnerability was found internally.
Status of this Notice: FINAL
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 in the following section is an uncontrolled copy, and may lack important information or contain factual errors.
Distribution
This advisory is posted on Cisco's worldwide website at:
http://www.cisco.com/warp/public/707/cisco-sa-20090923-cme.shtml
In addition to worldwide web posting, a text version of this notice is clear-signed with the Cisco PSIRT PGP key and is posted to the following e-mail and Usenet news recipients.
- cust-security-announce@cisco.com
- first-bulletins@lists.first.org
- bugtraq@securityfocus.com
- vulnwatch@vulnwatch.org
- cisco@spot.colorado.edu
- cisco-nsp@puck.nether.net
- full-disclosure@lists.grok.org.uk
- comp.dcom.sys.cisco@newsgate.cisco.com
Future updates of this advisory, if any, will be placed on Cisco's worldwide website, but may or may not be actively announced on mailing lists or newsgroups. Users concerned about this problem are encouraged to check the above URL for any updates.
Revision History
+----------------------------------------+ | Revision | | Initial | | 1.0 | 2009-September-23 | public | | | | release | +----------------------------------------+
Cisco Security Procedures
Complete information on reporting security vulnerabilities in Cisco products, obtaining assistance with security incidents, and registering to receive security information from Cisco, is available on Cisco's worldwide website at:
http://www.cisco.com/en/US/products/products_security_vulnerability_policy.html
This includes instructions for press inquiries regarding Cisco security notices. All Cisco security advisories are available at:
http://www.cisco.com/go/psirt -----BEGIN PGP SIGNATURE-----
iD8DBQFKukGH86n/Gc8U/uARAgunAJ90YNHlxpf2v1OEz8qFEo7oqmNAqACfbq6X iHSiDV5CevynZQRrKe+sRiU= =Fp40 -----END PGP SIGNATURE-----
Show details on source website{
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/VARIoTentry#",
"affected_products": {
"@id": "https://www.variotdbs.pl/ref/affected_products"
},
"configurations": {
"@id": "https://www.variotdbs.pl/ref/configurations"
},
"credits": {
"@id": "https://www.variotdbs.pl/ref/credits"
},
"cvss": {
"@id": "https://www.variotdbs.pl/ref/cvss/"
},
"description": {
"@id": "https://www.variotdbs.pl/ref/description/"
},
"exploit_availability": {
"@id": "https://www.variotdbs.pl/ref/exploit_availability/"
},
"external_ids": {
"@id": "https://www.variotdbs.pl/ref/external_ids/"
},
"iot": {
"@id": "https://www.variotdbs.pl/ref/iot/"
},
"iot_taxonomy": {
"@id": "https://www.variotdbs.pl/ref/iot_taxonomy/"
},
"patch": {
"@id": "https://www.variotdbs.pl/ref/patch/"
},
"problemtype_data": {
"@id": "https://www.variotdbs.pl/ref/problemtype_data/"
},
"references": {
"@id": "https://www.variotdbs.pl/ref/references/"
},
"sources": {
"@id": "https://www.variotdbs.pl/ref/sources/"
},
"sources_release_date": {
"@id": "https://www.variotdbs.pl/ref/sources_release_date/"
},
"sources_update_date": {
"@id": "https://www.variotdbs.pl/ref/sources_update_date/"
},
"threat_type": {
"@id": "https://www.variotdbs.pl/ref/threat_type/"
},
"title": {
"@id": "https://www.variotdbs.pl/ref/title/"
},
"type": {
"@id": "https://www.variotdbs.pl/ref/type/"
}
},
"@id": "https://www.variotdbs.pl/vuln/VAR-200909-0382",
"affected_products": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/affected_products#",
"data": {
"@container": "@list"
},
"sources": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources#"
},
"@id": "https://www.variotdbs.pl/ref/sources"
}
},
"data": [
{
"model": "unified communications manager express",
"scope": "eq",
"trust": 1.0,
"vendor": "cisco",
"version": "*"
},
{
"model": "ios",
"scope": "eq",
"trust": 1.0,
"vendor": "cisco",
"version": "12.4xz"
},
{
"model": "ios",
"scope": "eq",
"trust": 1.0,
"vendor": "cisco",
"version": "12.4ya"
},
{
"model": "ios",
"scope": "eq",
"trust": 1.0,
"vendor": "cisco",
"version": "12.4xy"
},
{
"model": "ios",
"scope": "eq",
"trust": 1.0,
"vendor": "cisco",
"version": "12.4xw"
},
{
"model": "ios",
"scope": "eq",
"trust": 0.8,
"vendor": "cisco",
"version": "12.4"
},
{
"model": "unified communications manager express",
"scope": null,
"trust": 0.6,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.4ya",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.4xz",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.4xy",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.4xw",
"scope": null,
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.4 t2",
"scope": "ne",
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.4 t3",
"scope": "ne",
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.4 ya1",
"scope": "ne",
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.4 t4",
"scope": "ne",
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.4 xz1",
"scope": "ne",
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.4 xy4",
"scope": "ne",
"trust": 0.3,
"vendor": "cisco",
"version": null
},
{
"model": "ios 12.4 xw8",
"scope": "ne",
"trust": 0.3,
"vendor": "cisco",
"version": null
}
],
"sources": [
{
"db": "BID",
"id": "36498"
},
{
"db": "JVNDB",
"id": "JVNDB-2009-002166"
},
{
"db": "CNNVD",
"id": "CNNVD-200910-019"
},
{
"db": "NVD",
"id": "CVE-2009-2865"
}
]
},
"configurations": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/configurations#",
"children": {
"@container": "@list"
},
"cpe_match": {
"@container": "@list"
},
"data": {
"@container": "@list"
},
"nodes": {
"@container": "@list"
}
},
"data": [
{
"CVE_data_version": "4.0",
"nodes": [
{
"cpe_match": [
{
"cpe22Uri": "cpe:/o:cisco:ios",
"vulnerable": true
}
],
"operator": "OR"
}
]
}
],
"sources": [
{
"db": "JVNDB",
"id": "JVNDB-2009-002166"
}
]
},
"credits": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/credits#",
"sources": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources#"
}
}
},
"data": "Cisco Security bulletin",
"sources": [
{
"db": "CNNVD",
"id": "CNNVD-200910-019"
}
],
"trust": 0.6
},
"cve": "CVE-2009-2865",
"cvss": {
"@context": {
"cvssV2": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/cvss/cvssV2#"
},
"@id": "https://www.variotdbs.pl/ref/cvss/cvssV2"
},
"cvssV3": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/cvss/cvssV3#"
},
"@id": "https://www.variotdbs.pl/ref/cvss/cvssV3/"
},
"severity": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/cvss/severity#"
},
"@id": "https://www.variotdbs.pl/ref/cvss/severity"
},
"sources": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources#"
},
"@id": "https://www.variotdbs.pl/ref/sources"
}
},
"data": [
{
"cvssV2": [
{
"accessComplexity": "HIGH",
"accessVector": "NETWORK",
"authentication": "NONE",
"author": "nvd@nist.gov",
"availabilityImpact": "COMPLETE",
"baseScore": 7.6,
"confidentialityImpact": "COMPLETE",
"exploitabilityScore": 4.9,
"id": "CVE-2009-2865",
"impactScore": 10.0,
"integrityImpact": "COMPLETE",
"severity": "HIGH",
"trust": 1.8,
"vectorString": "AV:N/AC:H/Au:N/C:C/I:C/A:C",
"version": "2.0"
},
{
"accessComplexity": "HIGH",
"accessVector": "NETWORK",
"authentication": "NONE",
"author": "VULHUB",
"availabilityImpact": "COMPLETE",
"baseScore": 7.6,
"confidentialityImpact": "COMPLETE",
"exploitabilityScore": 4.9,
"id": "VHN-40311",
"impactScore": 10.0,
"integrityImpact": "COMPLETE",
"severity": "HIGH",
"trust": 0.1,
"vectorString": "AV:N/AC:H/AU:N/C:C/I:C/A:C",
"version": "2.0"
}
],
"cvssV3": [],
"severity": [
{
"author": "nvd@nist.gov",
"id": "CVE-2009-2865",
"trust": 1.0,
"value": "HIGH"
},
{
"author": "NVD",
"id": "CVE-2009-2865",
"trust": 0.8,
"value": "High"
},
{
"author": "CNNVD",
"id": "CNNVD-200910-019",
"trust": 0.6,
"value": "HIGH"
},
{
"author": "VULHUB",
"id": "VHN-40311",
"trust": 0.1,
"value": "HIGH"
}
]
}
],
"sources": [
{
"db": "VULHUB",
"id": "VHN-40311"
},
{
"db": "JVNDB",
"id": "JVNDB-2009-002166"
},
{
"db": "CNNVD",
"id": "CNNVD-200910-019"
},
{
"db": "NVD",
"id": "CVE-2009-2865"
}
]
},
"description": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/description#",
"sources": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources#"
}
}
},
"data": "Buffer overflow in the login implementation in the Extension Mobility feature in the Unified Communications Manager Express (CME) component in Cisco IOS 12.4XW, 12.4XY, 12.4XZ, and 12.4YA allows remote attackers to execute arbitrary code or cause a denial of service via crafted HTTP requests, aka Bug ID CSCsq58779. \nAttackers can exploit this issue to execute arbitrary code or to cause denial-of-service conditions. \nThis issue is documented by Cisco Bug ID CSCsq58779. ----------------------------------------------------------------------\n\nDo you have VARM strategy implemented?\n\n(Vulnerability Assessment Remediation Management) \n\nIf not, then implement it through the most reliable vulnerability\nintelligence source on the market. \n\nImplement it through Secunia. \n\nFor more information visit:\nhttp://secunia.com/advisories/business_solutions/\n\nAlternatively request a call from a Secunia representative today to\ndiscuss how we can help you with our capabilities contact us at:\nsales@secunia.com\n\n----------------------------------------------------------------------\n\nTITLE:\nCisco IOS Multiple Vulnerabilities\n\nSECUNIA ADVISORY ID:\nSA36835\n\nVERIFY ADVISORY:\nhttp://secunia.com/advisories/36835/\n\nDESCRIPTION:\nSome vulnerabilities have been reported in Cisco IOS, which can be\nexploited by malicious people to cause a DoS (Denial of Service),\nbypass certain security restrictions, disclose sensitive information,\nor compromise a vulnerable device. This can be exploited to cause a buffer overflow via\nspecially crafted HTTP requests. \n\n2) An error in the IKE implementation can be exploited to allocate\nall available Phase 1 SAs and prevent new IPSec sessions from being\nestablished. \n\nSuccessful exploitation requires that the IKE certificate based\nauthentication method is used. \n\n3) Multiple errors exist in the IP tunnelling implementation when\nswitching network packets. These can be exploited to trigger a device\nreload via specially crafted packets. \n\nSuccessful exploitation requires that the device is configured for\nPPTP, GRE, IPinIP, Generic Packet Tunneling in IPv6, or IPv6 over IP\ntunnels, and Cisco Express Forwarding. \n\n4) An error in the implementation of the Object Groups for ACLs\nfeature can be exploited to bypass access control policies. \n\n5) An error in the H.323 implementation can be exploited to trigger a\ndevice reload via specially crafted TCP packets. \n\n6) An error in the SIP implementation related to the Cisco Unified\nBorder Element feature can be exploited to trigger a device reload. \n\nFor more information:\nSA36836\n\n7) An error in the SSLVPN, SSH, and IKE Encrypted Nonces features can\nbe exploited to reload a device via specially crafted packets sent to\nTCP ports 22 (for SSH) or 443 (for SSLVPN), or UDP ports 500 and 4500\n(for IKE Encrypted Nonces). \n\n8) A race condition error exists in the Authentication Proxy for\nHTTP(S), Web Authentication, and consent features. This can be\nexploited to bypass the authentication proxy services and the consent\naccept web page if a successfully authenticated session or accepted\nconsent session exists. \n\n9) An error exists in the Cisco IOS Zone-Based Policy Firewall SIP\ninspection feature. This can be exploited to reload a device via a\nspecially crafted SIP transit packet. \n\n10) An error exists in the NTPv4 implementation while creating NTP\nreply packets. This can be exploited to trigger a device reload via a\nspecially crafted NTP packet. \n\nSOLUTION:\nUpdate to a fixed version (please see the vendor\u0027s advisories for\ndetails). \n\nPROVIDED AND/OR DISCOVERED BY:\n1, 3-10) Reported by the vendor. \n2) Reported to the vendor by a customer. \n\nORIGINAL ADVISORY:\nhttp://www.cisco.com/warp/public/707/cisco-sa-20090923-cme.shtml\nhttp://www.cisco.com/warp/public/707/cisco-sa-20090923-ipsec.shtml\nhttp://www.cisco.com/warp/public/707/cisco-sa-20090923-tunnels.shtml\nhttp://www.cisco.com/warp/public/707/cisco-sa-20090923-acl.shtml\nhttp://www.cisco.com/warp/public/707/cisco-sa-20090923-h323.shtml\nhttp://www.cisco.com/warp/public/707/cisco-sa-20090923-sip.shtml\nhttp://www.cisco.com/warp/public/707/cisco-sa-20090923-tls.shtml\nhttp://www.cisco.com/warp/public/707/cisco-sa-20090923-auth-proxy.shtml\nhttp://www.cisco.com/warp/public/707/cisco-sa-20090923-ios-fw.shtml\nhttp://www.cisco.com/warp/public/707/cisco-sa-20090923-ntp.shtml\n\nOTHER REFERENCES:\nSA36836:\nhttp://secunia.com/advisories/36836/\n\n----------------------------------------------------------------------\n\nAbout:\nThis Advisory was delivered by Secunia as a free service to help\neverybody keeping their systems up to date against the latest\nvulnerabilities. \n\nSubscribe:\nhttp://secunia.com/advisories/secunia_security_advisories/\n\nDefinitions: (Criticality, Where etc.)\nhttp://secunia.com/advisories/about_secunia_advisories/\n\n\nPlease Note:\nSecunia recommends that you verify all advisories you receive by\nclicking the link. \nSecunia NEVER sends attached files with advisories. \nSecunia does not advise people to install third party patches, only\nuse those supplied by the vendor. \n\n----------------------------------------------------------------------\n\nUnsubscribe: Secunia Security Advisories\nhttp://secunia.com/sec_adv_unsubscribe/?email=packet%40packetstormsecurity.org\n\n----------------------------------------------------------------------\n\n\n. \n\nCisco has released free software updates that address this\nvulnerability. \n\nThis advisory is posted at:\n\nhttp://www.cisco.com/warp/public/707/cisco-sa-20090923-cme.shtml\n\nNote: The September 23, 2009, Cisco IOS Security Advisory bundled\npublication includes eleven Security Advisories. Each advisory lists the releases that correct the\nvulnerability or vulnerabilities detailed in the advisory. The\nfollowing table lists releases that correct all Cisco IOS Software\nvulnerabilities that have been published on September 23, 2009, or\nearlier. \n logout-profile [logout-profile tag]\n\nTo determine the Cisco IOS Software release that is running on a\nCisco product, administrators can log in to the device and issue the \n\"show version\" command to display the system banner. The system banner\nconfirms that the device is running Cisco IOS Software by displaying\ntext similar to \"Cisco Internetwork Operating System Software\" or\n\"Cisco IOS Software.\" The image name is displayed in parentheses,\nfollowed by \"Version\" and the Cisco IOS Software release name. Other\nCisco devices do not have the \"show version\" command or may provide\ndifferent output. \n\nThe following example identifies a Cisco product that is running\nCisco IOS Software Release 12.3(26) with an installed image name of\nC2500-IS-L:\n\n Router#show version\n Cisco Internetwork Operating System Software\n IOS (tm) 2500 Software (C2500-IS-L), Version 12.3(26), RELEASE SOFTWARE (fc2)\n Technical Support: http://www.cisco.com/techsupport\n Copyright (c) 1986-2008 by cisco Systems, Inc. \n Compiled Mon 17-Mar-08 14:39 by dchih\n \n \u003coutput truncated\u003e\n\nThe following example identifies a Cisco product that is running\nCisco IOS Software Release 12.4(20)T with an installed image name of\nC1841-ADVENTERPRISEK9-M:\n\n Router#show version\n Cisco IOS Software, 1841 Software (C1841-ADVENTERPRISEK9-M), Version 12.4(20)T, RELEASE SOFTWARE (fc3)\n Technical Support: http://www.cisco.com/techsupport\n Copyright (c) 1986-2008 by Cisco Systems, Inc. \n Compiled Thu 10-Jul-08 20:25 by prod_rel_team\n \n \u003coutput truncated\u003e\n\nAdditional information about Cisco IOS Software release naming\nconventions is available in \"White Paper: Cisco IOS Reference Guide\"\nat the following link: http://www.cisco.com/warp/public/620/1.html . \n\nCisco IOS XR is not affected. \n\nCisco IOS XE is not affected. \n\nCisco Unified Communications Manager is not affected. \n\nNo other Cisco products are currently known to be affected by these\nvulnerabilities. \n\nDetails\n=======\n\nCisco Unified CME is the call processing component of an enhanced IP\ntelephony solution that is integrated into Cisco IOS. A user login service allows\nphone users to temporarily access a physical phone other than their\nown phone and utilize their personal settings, such as directory\nnumber, speed-dial lists, and services, that is assigned to their own\ndesk phone. The phone user can make and receive calls on that phone\nusing the same personal directory number as is on their own desk\nphone. Such packets can\nonly come from registered phone IP addresses in the form of HTTP\nrequests. If the auto-registration feature is enabled, an attacker\ncan register its IP address and subsequently send a crafted payload\nto exploit this vulnerability. The auto-registration feature is\nenabled by default. More information on auto-registration can be\nfound at the following link:\n\nhttp://www.cisco.com/en/US/docs/voice_ip_comm/cucme/command/reference/cme_a1ht.html#wp1031242. \n\nVulnerability Scoring Details\n=============================\n\nCisco has provided scores for the vulnerabilities in this advisory\nbased on the Common Vulnerability Scoring System (CVSS). The CVSS\nscoring in this Security Advisory is done in accordance with CVSS\nversion 2.0. \n\nCVSS is a standards-based scoring method that conveys vulnerability\nseverity and helps determine urgency and priority of response. \n\nCisco has provided a base and temporal score. Customers can then\ncompute environmental scores to assist in determining the impact of\nthe vulnerability in individual networks. \n\nCisco has provided an FAQ to answer additional questions regarding\nCVSS at:\n\nhttp://www.cisco.com/web/about/security/intelligence/cvss-qandas.html\n\nCisco has also provided a CVSS calculator to help compute the\nenvironmental impact for individual networks at:\n\nhttp://intellishield.cisco.com/security/alertmanager/cvss\n\nCSCsq58779 - Vulnerability in Extension Mobility Feature\n\nCVSS Base Score - 7.6\n\nAccess Vector - Network\nAccess Complexity - High\nAuthentication - None\nConfidentiality Impact - Complete\nIntegrity Impact - Complete\nAvailability Impact - Complete\n\nCVSS Temporal Score - 6.3\n\nExploitability - Functional\nRemediation Level - Official-Fix\nReport Confidence - Confirmed\n\nImpact\n======\n\nSuccessful exploitation of this vulnerability may result in the\nexecution of arbitrary code or a Denial of Service (DoS) condition on\nan affected device. \n\nSoftware Versions and Fixes\n===========================\n\nWhen considering software upgrades, also consult:\n\nhttp://www.cisco.com/go/psirt\n\nand any subsequent advisories to determine exposure and a complete\nupgrade solution. \n\nIn all cases, customers should exercise caution to be certain the\ndevices to be upgraded contain sufficient memory and that current\nhardware and software configurations will continue to be supported\nproperly by the new release. If the information is not clear, contact\nthe Cisco Technical Assistance Center (TAC) or your contracted\nmaintenance provider for assistance. \n\nEach row of the Cisco IOS software table (below) names a Cisco IOS\nrelease train. If a given release train is vulnerable, then the\nearliest possible releases that contain the fix (along with the\nanticipated date of availability for each, if applicable) are listed\nin the \"First Fixed Release\" column of the table. The \"Recommended\nRelease\" column indicates the releases which have fixes for all the\npublished vulnerabilities at the time of this Advisory. A device\nrunning a release in the given train that is earlier than the release\nin a specific column (less than the First Fixed Release) is known to\nbe vulnerable. Cisco recommends upgrading to a release equal to or\nlater than the release in the \"Recommended Releases\" column of the\ntable. \n\n+-------------------------------------------------------------------+\n| Major Release | Availability of Repaired Releases |\n|----------------------+--------------------------------------------|\n| Affected 12.0-Based | First Fixed | Recommended Release |\n| Releases | Release | |\n|-------------------------------------------------------------------|\n| There are no affected 12.0 based releases. |\n|-------------------------------------------------------------------|\n| Affected 12.1-Based | First Fixed | Recommended Release |\n| Releases | Release | |\n|-------------------------------------------------------------------|\n| There are no affected 12.1 based releases. |\n|-------------------------------------------------------------------|\n| Affected 12.2-Based | First Fixed | Recommended Release |\n| Releases | Release | |\n|-------------------------------------------------------------------|\n| There are no affected 12.2 based releases. |\n|-------------------------------------------------------------------|\n| Affected 12.3-Based | First Fixed | Recommended Release |\n| Releases | Release | |\n|-------------------------------------------------------------------|\n| There are no affected 12.3 based releases. |\n|-------------------------------------------------------------------|\n| Affected 12.4-Based | First Fixed | Recommended Release |\n| Releases | Release | |\n|----------------------+---------------+----------------------------|\n| 12.4 | Not | |\n| | Vulnerable | |\n|----------------------+---------------+----------------------------|\n| 12.4GC | Not | |\n| | Vulnerable | |\n|----------------------+---------------+----------------------------|\n| 12.4JA | Not | |\n| | Vulnerable | |\n|----------------------+---------------+----------------------------|\n| 12.4JDA | Not | |\n| | Vulnerable | |\n|----------------------+---------------+----------------------------|\n| 12.4JDC | Not | |\n| | Vulnerable | |\n|----------------------+---------------+----------------------------|\n| 12.4JDD | Not | |\n| | Vulnerable | |\n|----------------------+---------------+----------------------------|\n| 12.4JK | Not | |\n| | Vulnerable | |\n|----------------------+---------------+----------------------------|\n| 12.4JL | Not | |\n| | Vulnerable | |\n|----------------------+---------------+----------------------------|\n| 12.4JMA | Not | |\n| | Vulnerable | |\n|----------------------+---------------+----------------------------|\n| 12.4JMB | Not | |\n| | Vulnerable | |\n|----------------------+---------------+----------------------------|\n| 12.4JX | Not | |\n| | Vulnerable | |\n|----------------------+---------------+----------------------------|\n| 12.4MD | Not | |\n| | Vulnerable | |\n|----------------------+---------------+----------------------------|\n| 12.4MDA | Not | |\n| | Vulnerable | |\n|----------------------+---------------+----------------------------|\n| 12.4MR | Not | |\n| | Vulnerable | |\n|----------------------+---------------+----------------------------|\n| 12.4SW | Not | |\n| | Vulnerable | |\n|----------------------+---------------+----------------------------|\n| 12.4T | Not | |\n| | Vulnerable | |\n|----------------------+---------------+----------------------------|\n| 12.4XA | Not | |\n| | Vulnerable | |\n|----------------------+---------------+----------------------------|\n| 12.4XB | Not | |\n| | Vulnerable | |\n|----------------------+---------------+----------------------------|\n| 12.4XC | Not | |\n| | Vulnerable | |\n|----------------------+---------------+----------------------------|\n| 12.4XD | Not | |\n| | Vulnerable | |\n|----------------------+---------------+----------------------------|\n| 12.4XE | Not | |\n| | Vulnerable | |\n|----------------------+---------------+----------------------------|\n| 12.4XF | Not | |\n| | Vulnerable | |\n|----------------------+---------------+----------------------------|\n| 12.4XG | Not | |\n| | Vulnerable | |\n|----------------------+---------------+----------------------------|\n| 12.4XJ | Not | |\n| | Vulnerable | |\n|----------------------+---------------+----------------------------|\n| 12.4XK | Not | |\n| | Vulnerable | |\n|----------------------+---------------+----------------------------|\n| 12.4XL | Not | |\n| | Vulnerable | |\n|----------------------+---------------+----------------------------|\n| 12.4XM | Not | |\n| | Vulnerable | |\n|----------------------+---------------+----------------------------|\n| 12.4XN | Not | |\n| | Vulnerable | |\n|----------------------+---------------+----------------------------|\n| 12.4XP | Not | |\n| | Vulnerable | |\n|----------------------+---------------+----------------------------|\n| 12.4XQ | Not | |\n| | Vulnerable | |\n|----------------------+---------------+----------------------------|\n| 12.4XR | Not | |\n| | Vulnerable | |\n|----------------------+---------------+----------------------------|\n| 12.4XT | Not | |\n| | Vulnerable | |\n|----------------------+---------------+----------------------------|\n| 12.4XV | Not | |\n| | Vulnerable | |\n|----------------------+---------------+----------------------------|\n| | | 12.4(20)T4 |\n| | | |\n| 12.4XW | 12.4(11)XW8 | 12.4(22)T3 |\n| | | |\n| | | 12.4(24)T2; Available on |\n| | | 23-OCT-2009 |\n|----------------------+---------------+----------------------------|\n| | | 12.4(20)T4 |\n| | | |\n| 12.4XY | 12.4(15)XY4 | 12.4(22)T3 |\n| | | |\n| | | 12.4(24)T2; Available on |\n| | | 23-OCT-2009 |\n|----------------------+---------------+----------------------------|\n| | | 12.4(20)T4 |\n| | | |\n| 12.4XZ | 12.4(15)XZ1 | 12.4(22)T3 |\n| | | |\n| | | 12.4(24)T2; Available on |\n| | | 23-OCT-2009 |\n|----------------------+---------------+----------------------------|\n| | | 12.4(20)T4 |\n| | | |\n| 12.4YA | 12.4(20)YA1 | 12.4(22)T3 |\n| | | |\n| | | 12.4(24)T2; Available on |\n| | | 23-OCT-2009 |\n|----------------------+---------------+----------------------------|\n| 12.4YB | Not | |\n| | Vulnerable | |\n|----------------------+---------------+----------------------------|\n| 12.4YD | Not | |\n| | Vulnerable | |\n|----------------------+---------------+----------------------------|\n| 12.4YE | Not | |\n| | Vulnerable | |\n+-------------------------------------------------------------------+\n\nWorkarounds\n===========\n\nThere are no workarounds to mitigate this vulnerability, other than\ndisabling Extension Mobility. However, auto-registration can be\ndisabled to make exploitation more difficult. Auto-registration can\nbe disabled by the following command:\n\n telephony-service \n no auto-reg-ephone \n\nBefore disabling auto-registration, all phone MAC addresses need to\nbe explicitly defined on the Cisco Unified CME. Otherwise phones will\nnot be able to register. More information on auto-registration can be\nfound at the following link:\n\nhttp://www.cisco.com/en/US/docs/voice_ip_comm/cucme/command/reference/cme_a1ht.html#wp1031242\n\nAdditional mitigations that can be deployed on Cisco devices in the\nnetwork are available in the Cisco Applied Mitigation Bulletin\ncompanion document for this advisory, which is available at the\nfollowing link:\n\nhttp://www.cisco.com/warp/public/707/cisco-amb-20090923-cme.shtml\n\nObtaining Fixed Software\n========================\n\nCisco has released free software updates that address these\nvulnerabilities. Prior to deploying software, customers should\nconsult their maintenance provider or check the software for feature\nset compatibility and known issues specific to their environment. \n\nCustomers may only install and expect support for the feature sets\nthey have purchased. By installing, downloading, accessing or\notherwise using such software upgrades, customers agree to be bound\nby the terms of Cisco\u0027s software license terms found at:\n\nhttp://www.cisco.com/en/US/docs/general/warranty/English/EU1KEN_.html\n\nor as otherwise set forth at Cisco.com Downloads at:\n\nhttp://www.cisco.com/public/sw-center/sw-usingswc.shtml\n\nDo not contact psirt@cisco.com or security-alert@cisco.com for\nsoftware upgrades. \n\nCustomers with Service Contracts\n+-------------------------------\n\nCustomers with contracts should obtain upgraded software through\ntheir regular update channels. For most customers, this means that\nupgrades should be obtained through the Software Center on Cisco\u0027s\nworldwide website at http://www.cisco.com. \n\nCustomers using Third Party Support Organizations\n+------------------------------------------------\n\nCustomers whose Cisco products are provided or maintained through\nprior or existing agreements with third-party support organizations,\nsuch as Cisco Partners, authorized resellers, or service providers\nshould contact that support organization for guidance and assistance\nwith the appropriate course of action in regards to this advisory. \n\nThe effectiveness of any workaround or fix is dependent on specific\ncustomer situations, such as product mix, network topology, traffic\nbehavior, and organizational mission. Due to the variety of affected\nproducts and releases, customers should consult with their service\nprovider or support organization to ensure any applied workaround or\nfix is the most appropriate for use in the intended network before it\nis deployed. \n\nCustomers without Service Contracts\n+----------------------------------\n\nCustomers who purchase direct from Cisco but do not hold a Cisco\nservice contract, and customers who purchase through third-party\nvendors but are unsuccessful in obtaining fixed software through\ntheir point of sale should acquire upgrades by contacting the Cisco\nTechnical Assistance Center (TAC). TAC contacts are as follows. \n\n * +1 800 553 2447 (toll free from within North America)\n * +1 408 526 7209 (toll call from anywhere in the world)\n * e-mail: tac@cisco.com\n\nCustomers should have their product serial number available and be\nprepared to give the URL of this notice as evidence of entitlement to\na free upgrade. Free upgrades for non-contract customers must be\nrequested through the TAC. \n\nRefer to:\n\nhttp://www.cisco.com/en/US/support/tsd_cisco_worldwide_contacts.html\n\nfor additional TAC contact information, including localized telephone\nnumbers, and instructions and e-mail addresses for use in various\nlanguages. \n\nExploitation and Public Announcements\n=====================================\n\nThe Cisco PSIRT is not aware of any public announcements or malicious\nuse of the vulnerability described in this advisory. \n\nThis vulnerability was found internally. \n\nStatus of this Notice: FINAL\n============================\n\nTHIS DOCUMENT IS PROVIDED ON AN \"AS IS\" BASIS AND DOES NOT IMPLY ANY\nKIND OF GUARANTEE OR WARRANTY, INCLUDING THE WARRANTIES OF\nMERCHANTABILITY OR FITNESS FOR A PARTICULAR USE. YOUR USE OF THE\nINFORMATION ON THE DOCUMENT OR MATERIALS LINKED FROM THE DOCUMENT IS\nAT YOUR OWN RISK. CISCO RESERVES THE RIGHT TO CHANGE OR UPDATE THIS\nDOCUMENT AT ANY TIME. \n\nA stand-alone copy or Paraphrase of the text of this document that\nomits the distribution URL in the following section is an\nuncontrolled copy, and may lack important information or contain\nfactual errors. \n\nDistribution\n============\n\nThis advisory is posted on Cisco\u0027s worldwide website at:\n\nhttp://www.cisco.com/warp/public/707/cisco-sa-20090923-cme.shtml\n\nIn addition to worldwide web posting, a text version of this notice\nis clear-signed with the Cisco PSIRT PGP key and is posted to the\nfollowing e-mail and Usenet news recipients. \n\n * cust-security-announce@cisco.com\n * first-bulletins@lists.first.org\n * bugtraq@securityfocus.com\n * vulnwatch@vulnwatch.org\n * cisco@spot.colorado.edu\n * cisco-nsp@puck.nether.net\n * full-disclosure@lists.grok.org.uk\n * comp.dcom.sys.cisco@newsgate.cisco.com\n\nFuture updates of this advisory, if any, will be placed on Cisco\u0027s\nworldwide website, but may or may not be actively announced on\nmailing lists or newsgroups. Users concerned about this problem are\nencouraged to check the above URL for any updates. \n\nRevision History\n================\n\n+----------------------------------------+\n| Revision | | Initial |\n| 1.0 | 2009-September-23 | public |\n| | | release |\n+----------------------------------------+\n\nCisco Security Procedures\n=========================\n\nComplete information on reporting security vulnerabilities in Cisco\nproducts, obtaining assistance with security incidents, and\nregistering to receive security information from Cisco, is available\non Cisco\u0027s worldwide website at:\n\nhttp://www.cisco.com/en/US/products/products_security_vulnerability_policy.html\n\nThis includes instructions for press inquiries regarding Cisco security\nnotices. All Cisco security advisories are available at:\n\nhttp://www.cisco.com/go/psirt\n-----BEGIN PGP SIGNATURE-----\n\niD8DBQFKukGH86n/Gc8U/uARAgunAJ90YNHlxpf2v1OEz8qFEo7oqmNAqACfbq6X\niHSiDV5CevynZQRrKe+sRiU=\n=Fp40\n-----END PGP SIGNATURE-----\n\n",
"sources": [
{
"db": "NVD",
"id": "CVE-2009-2865"
},
{
"db": "JVNDB",
"id": "JVNDB-2009-002166"
},
{
"db": "BID",
"id": "36498"
},
{
"db": "VULHUB",
"id": "VHN-40311"
},
{
"db": "PACKETSTORM",
"id": "81635"
},
{
"db": "PACKETSTORM",
"id": "81594"
}
],
"trust": 2.16
},
"exploit_availability": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/exploit_availability#",
"data": {
"@container": "@list"
},
"sources": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources#"
}
}
},
"data": [
{
"reference": "https://www.scap.org.cn/vuln/vhn-40311",
"trust": 0.1,
"type": "unknown"
}
],
"sources": [
{
"db": "VULHUB",
"id": "VHN-40311"
}
]
},
"external_ids": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/external_ids#",
"data": {
"@container": "@list"
},
"sources": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources#"
}
}
},
"data": [
{
"db": "NVD",
"id": "CVE-2009-2865",
"trust": 2.9
},
{
"db": "BID",
"id": "36498",
"trust": 2.8
},
{
"db": "SECTRACK",
"id": "1022932",
"trust": 2.5
},
{
"db": "OSVDB",
"id": "58335",
"trust": 2.5
},
{
"db": "VUPEN",
"id": "ADV-2009-2758",
"trust": 2.5
},
{
"db": "XF",
"id": "53448",
"trust": 1.4
},
{
"db": "SECUNIA",
"id": "36835",
"trust": 0.9
},
{
"db": "JVNDB",
"id": "JVNDB-2009-002166",
"trust": 0.8
},
{
"db": "CNNVD",
"id": "CNNVD-200910-019",
"trust": 0.7
},
{
"db": "CISCO",
"id": "20090923 CISCO UNIFIED COMMUNICATIONS MANAGER EXPRESS VULNERABILITY",
"trust": 0.6
},
{
"db": "PACKETSTORM",
"id": "81594",
"trust": 0.2
},
{
"db": "VULHUB",
"id": "VHN-40311",
"trust": 0.1
},
{
"db": "PACKETSTORM",
"id": "81635",
"trust": 0.1
}
],
"sources": [
{
"db": "VULHUB",
"id": "VHN-40311"
},
{
"db": "BID",
"id": "36498"
},
{
"db": "JVNDB",
"id": "JVNDB-2009-002166"
},
{
"db": "PACKETSTORM",
"id": "81635"
},
{
"db": "PACKETSTORM",
"id": "81594"
},
{
"db": "CNNVD",
"id": "CNNVD-200910-019"
},
{
"db": "NVD",
"id": "CVE-2009-2865"
}
]
},
"id": "VAR-200909-0382",
"iot": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/iot#",
"sources": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources#"
}
}
},
"data": true,
"sources": [
{
"db": "VULHUB",
"id": "VHN-40311"
}
],
"trust": 0.01
},
"last_update_date": "2025-04-10T20:45:39.919000Z",
"patch": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/patch#",
"data": {
"@container": "@list"
},
"sources": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources#"
}
}
},
"data": [
{
"title": "cisco-amb-20090923-cme",
"trust": 0.8,
"url": "http://www.cisco.com/warp/public/707/cisco-amb-20090923-cme.shtml"
},
{
"title": "cisco-sa-20090923-cme",
"trust": 0.8,
"url": "http://www.cisco.com/warp/public/707/cisco-sa-20090923-cme.shtml"
}
],
"sources": [
{
"db": "JVNDB",
"id": "JVNDB-2009-002166"
}
]
},
"problemtype_data": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/problemtype_data#",
"sources": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources#"
}
}
},
"data": [
{
"problemtype": "CWE-119",
"trust": 1.9
}
],
"sources": [
{
"db": "VULHUB",
"id": "VHN-40311"
},
{
"db": "JVNDB",
"id": "JVNDB-2009-002166"
},
{
"db": "NVD",
"id": "CVE-2009-2865"
}
]
},
"references": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/references#",
"data": {
"@container": "@list"
},
"sources": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources#"
}
}
},
"data": [
{
"trust": 2.5,
"url": "http://www.securityfocus.com/bid/36498"
},
{
"trust": 2.5,
"url": "http://osvdb.org/58335"
},
{
"trust": 2.5,
"url": "http://www.securitytracker.com/id?1022932"
},
{
"trust": 2.5,
"url": "http://www.vupen.com/english/advisories/2009/2758"
},
{
"trust": 1.7,
"url": "http://www.cisco.com/en/us/products/products_security_advisory09186a0080af8116.shtml"
},
{
"trust": 1.7,
"url": "http://tools.cisco.com/security/center/viewalert.x?alertid=18884"
},
{
"trust": 1.4,
"url": "http://xforce.iss.net/xforce/xfdb/53448"
},
{
"trust": 1.1,
"url": "https://exchange.xforce.ibmcloud.com/vulnerabilities/53448"
},
{
"trust": 0.8,
"url": "http://cve.mitre.org/cgi-bin/cvename.cgi?name=cve-2009-2865"
},
{
"trust": 0.8,
"url": "http://web.nvd.nist.gov/view/vuln/detail?vulnid=cve-2009-2865"
},
{
"trust": 0.8,
"url": "http://secunia.com/advisories/36835"
},
{
"trust": 0.5,
"url": "http://www.cisco.com/warp/public/707/cisco-sa-20090923-cme.shtml"
},
{
"trust": 0.3,
"url": "http://www.cisco.com"
},
{
"trust": 0.3,
"url": "/archive/1/506683"
},
{
"trust": 0.1,
"url": "http://www.cisco.com/warp/public/707/cisco-sa-20090923-ipsec.shtml"
},
{
"trust": 0.1,
"url": "http://www.cisco.com/warp/public/707/cisco-sa-20090923-h323.shtml"
},
{
"trust": 0.1,
"url": "http://secunia.com/advisories/36836/"
},
{
"trust": 0.1,
"url": "http://www.cisco.com/warp/public/707/cisco-sa-20090923-ios-fw.shtml"
},
{
"trust": 0.1,
"url": "http://secunia.com/advisories/secunia_security_advisories/"
},
{
"trust": 0.1,
"url": "http://www.cisco.com/warp/public/707/cisco-sa-20090923-auth-proxy.shtml"
},
{
"trust": 0.1,
"url": "http://www.cisco.com/warp/public/707/cisco-sa-20090923-sip.shtml"
},
{
"trust": 0.1,
"url": "http://secunia.com/advisories/business_solutions/"
},
{
"trust": 0.1,
"url": "http://www.cisco.com/warp/public/707/cisco-sa-20090923-tunnels.shtml"
},
{
"trust": 0.1,
"url": "http://secunia.com/sec_adv_unsubscribe/?email=packet%40packetstormsecurity.org"
},
{
"trust": 0.1,
"url": "http://www.cisco.com/warp/public/707/cisco-sa-20090923-acl.shtml"
},
{
"trust": 0.1,
"url": "http://www.cisco.com/warp/public/707/cisco-sa-20090923-tls.shtml"
},
{
"trust": 0.1,
"url": "http://www.cisco.com/warp/public/707/cisco-sa-20090923-ntp.shtml"
},
{
"trust": 0.1,
"url": "http://secunia.com/advisories/36835/"
},
{
"trust": 0.1,
"url": "http://secunia.com/advisories/about_secunia_advisories/"
},
{
"trust": 0.1,
"url": "http://www.cisco.com/warp/public/620/1.html"
},
{
"trust": 0.1,
"url": "http://www.cisco.com/go/psirt"
},
{
"trust": 0.1,
"url": "http://www.cisco.com/en/us/support/tsd_cisco_worldwide_contacts.html"
},
{
"trust": 0.1,
"url": "http://www.cisco.com/en/us/products/products_security_vulnerability_policy.html"
},
{
"trust": 0.1,
"url": "http://www.cisco.com/warp/public/707/cisco-sa-20090923-bundle.shtml"
},
{
"trust": 0.1,
"url": "http://www.cisco.com/en/us/docs/voice_ip_comm/cucme/admin/configuration/guide/cmemobl.html"
},
{
"trust": 0.1,
"url": "http://www.cisco.com/en/us/docs/general/warranty/english/eu1ken_.html"
},
{
"trust": 0.1,
"url": "http://www.cisco.com/web/about/security/intelligence/cvss-qandas.html"
},
{
"trust": 0.1,
"url": "http://www.cisco.com/web/about/security/intelligence/cisco_erp_sep09.html"
},
{
"trust": 0.1,
"url": "https://nvd.nist.gov/vuln/detail/cve-2009-2865"
},
{
"trust": 0.1,
"url": "http://www.cisco.com/en/us/docs/voice_ip_comm/cucme/command/reference/cme_a1ht.html#wp1031242."
},
{
"trust": 0.1,
"url": "http://www.cisco.com."
},
{
"trust": 0.1,
"url": "http://www.cisco.com/techsupport"
},
{
"trust": 0.1,
"url": "http://www.cisco.com/warp/public/707/cisco-amb-20090923-cme.shtml"
},
{
"trust": 0.1,
"url": "http://www.cisco.com/public/sw-center/sw-usingswc.shtml"
},
{
"trust": 0.1,
"url": "http://www.cisco.com/en/us/docs/voice_ip_comm/cucme/command/reference/cme_a1ht.html#wp1031242"
},
{
"trust": 0.1,
"url": "http://intellishield.cisco.com/security/alertmanager/cvss"
}
],
"sources": [
{
"db": "VULHUB",
"id": "VHN-40311"
},
{
"db": "BID",
"id": "36498"
},
{
"db": "JVNDB",
"id": "JVNDB-2009-002166"
},
{
"db": "PACKETSTORM",
"id": "81635"
},
{
"db": "PACKETSTORM",
"id": "81594"
},
{
"db": "CNNVD",
"id": "CNNVD-200910-019"
},
{
"db": "NVD",
"id": "CVE-2009-2865"
}
]
},
"sources": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources#",
"data": {
"@container": "@list"
}
},
"data": [
{
"db": "VULHUB",
"id": "VHN-40311"
},
{
"db": "BID",
"id": "36498"
},
{
"db": "JVNDB",
"id": "JVNDB-2009-002166"
},
{
"db": "PACKETSTORM",
"id": "81635"
},
{
"db": "PACKETSTORM",
"id": "81594"
},
{
"db": "CNNVD",
"id": "CNNVD-200910-019"
},
{
"db": "NVD",
"id": "CVE-2009-2865"
}
]
},
"sources_release_date": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources_release_date#",
"data": {
"@container": "@list"
}
},
"data": [
{
"date": "2009-09-28T00:00:00",
"db": "VULHUB",
"id": "VHN-40311"
},
{
"date": "2009-09-23T00:00:00",
"db": "BID",
"id": "36498"
},
{
"date": "2009-10-30T00:00:00",
"db": "JVNDB",
"id": "JVNDB-2009-002166"
},
{
"date": "2009-09-25T06:09:32",
"db": "PACKETSTORM",
"id": "81635"
},
{
"date": "2009-09-24T02:39:07",
"db": "PACKETSTORM",
"id": "81594"
},
{
"date": "2009-09-28T00:00:00",
"db": "CNNVD",
"id": "CNNVD-200910-019"
},
{
"date": "2009-09-28T19:30:01.377000",
"db": "NVD",
"id": "CVE-2009-2865"
}
]
},
"sources_update_date": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources_update_date#",
"data": {
"@container": "@list"
}
},
"data": [
{
"date": "2017-08-17T00:00:00",
"db": "VULHUB",
"id": "VHN-40311"
},
{
"date": "2009-09-23T18:50:00",
"db": "BID",
"id": "36498"
},
{
"date": "2009-10-30T00:00:00",
"db": "JVNDB",
"id": "JVNDB-2009-002166"
},
{
"date": "2009-10-01T00:00:00",
"db": "CNNVD",
"id": "CNNVD-200910-019"
},
{
"date": "2025-04-09T00:30:58.490000",
"db": "NVD",
"id": "CVE-2009-2865"
}
]
},
"threat_type": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/threat_type#",
"sources": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources#"
}
}
},
"data": "remote",
"sources": [
{
"db": "CNNVD",
"id": "CNNVD-200910-019"
}
],
"trust": 0.6
},
"title": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/title#",
"sources": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources#"
}
}
},
"data": "Cisco IOS of Unified CME Component buffer overflow vulnerability",
"sources": [
{
"db": "JVNDB",
"id": "JVNDB-2009-002166"
}
],
"trust": 0.8
},
"type": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/type#",
"sources": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources#"
}
}
},
"data": "buffer overflow",
"sources": [
{
"db": "CNNVD",
"id": "CNNVD-200910-019"
}
],
"trust": 0.6
}
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.