Cisco Call Manager up to 3.0/3.1 Call Telephony Integration Framework Password memory leak

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $0-$5k | 0.00 |
Summary
A vulnerability marked as problematic has been reported in Cisco Call Manager up to 3.0/3.1. This issue affects some unknown processing of the component Call Telephony Integration Framework. Performing a manipulation of the argument Password results in memory leak. This vulnerability is identified as CVE-2002-0505. There is not any exploit available. It is suggested to upgrade the affected component.
Details
A vulnerability, which was classified as problematic, was found in Cisco Call Manager up to 3.0/3.1. This affects an unknown code of the component Call Telephony Integration Framework. The manipulation of the argument Password with an unknown input leads to a memory leak vulnerability. CWE is classifying the issue as CWE-401. The product does not sufficiently track and release allocated memory after it has been used, which slowly consumes remaining memory. This is going to have an impact on availability. The summary by CVE is:
Memory leak in the Call Telephony Integration (CTI) Framework authentication for Cisco CallManager 3.0 and 3.1 before 3.1(3) allows remote attackers to cause a denial of service (crash and reload) via a series of authentication failures, e.g. via incorrect passwords.
The bug was discovered 03/28/2002. The weakness was released 08/12/2002 with Cisco (Website). The advisory is shared at cisco.com. This vulnerability is uniquely identified as CVE-2002-0505. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details are known, but no exploit is available.
The vulnerability was handled as a non-public zero-day exploit for at least 137 days. During that time the estimated underground price was around $5k-$25k.
Upgrading to version 3.0 eliminates this vulnerability.
The vulnerability is also documented in the databases at X-Force (8655), SecurityFocus (BID 4370†), OSVDB (5277†) and Vulnerability Center (SBV-11243†). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
License
Website
- Vendor: https://www.cisco.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.1
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Memory leakCWE: CWE-401 / CWE-404
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Call Manager 3.0
Timeline
03/27/2002 🔍03/27/2002 🔍
03/28/2002 🔍
08/12/2002 🔍
08/12/2002 🔍
04/25/2006 🔍
07/22/2014 🔍
06/17/2019 🔍
Sources
Vendor: cisco.comAdvisory: cisco.com
Organization: Cisco
Status: Not defined
CVE: CVE-2002-0505 (🔍)
GCVE (CVE): GCVE-0-2002-0505
GCVE (VulDB): GCVE-100-18561
X-Force: 8655
SecurityFocus: 4370 - Cisco CallManager CTI Memory Leak Denial of Service Vulnerability
OSVDB: 5277 - Cisco - CallManager - Denial of Service Attack via CTI Memory Leak
Vulnerability Center: 11243 - [cisco-sa-20020327-cm-ctifw-leak] Cisco CallManager DoS via Memory Leak in CTI Framework, Medium
Entry
Created: 07/22/2014 22:14Updated: 06/17/2019 06:57
Changes: 07/22/2014 22:14 (61), 06/17/2019 06:57 (3)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.