CVE-2010-0592 Vulnerability Analysis & Exploit Details

CVE-2010-0592
Vulnerability Scoring

7.8
/10
Very High Risk

Due to its potential exploitability, CVE-2010-0592 presents a serious risk to affected systems.

Attack Complexity Details

  • Attack Complexity: Low
    Exploits can be performed without significant complexity.
  • Attack Vector: Network
    Vulnerability is exploitable over a network without physical access.
  • Privileges Required: None
    No authentication is required for exploitation.
  • Scope:
    Impact is confined to the initially vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2010-0592 Details

Status: Modified

Last updated: 🕐 21 Nov 2024, 01:12 UTC
Originally published on: 🕟 05 Mar 2010, 16:30 UTC

Time between publication and last update: 5374 days

CVSS Release: version 2

CVE-2010-0592 Vulnerability Summary

CVE-2010-0592: The CTI Manager service in Cisco Unified Communications Manager (aka CUCM, formerly CallManager) 4.x before 4.3(2)sr1a, 6.x before 6.1(3), 7.0x before 7.0(2), 7.1x before 7.1(2), and 8.x before 8.0(1) allows remote attackers to cause a denial of service (service failure) via a malformed message, aka Bug ID CSCsu31800.

Assessing the Risk of CVE-2010-0592

Access Complexity Graph

The exploitability of CVE-2010-0592 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2010-0592

The vulnerability CVE-2010-0592 is highly exploitable since it requires low complexity and no authentication.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2010-0592, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2010-0592, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: None
    CVE-2010-0592 does not compromise confidentiality.
  • Integrity: None
    CVE-2010-0592 does not impact data integrity.
  • Availability: None
    CVE-2010-0592 does not affect system availability.

Exploit Prediction Scoring System (EPSS)

The EPSS score estimates the probability that this vulnerability will be exploited in the near future.

EPSS Score: 0.563% (probability of exploit)

EPSS Percentile: 78.01% (lower percentile = lower relative risk)
This vulnerability is less risky than approximately 21.989999999999995% of others.

CVE-2010-0592 References

External References

CWE Common Weakness Enumeration

NVD-CWE-Other

Vulnerable Configurations

  • cpe:2.3:a:cisco:unified_communications_manager:4.1:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:unified_communications_manager:4.1:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:unified_communications_manager:4.1:\(3\)sr.5:*:*:*:*:*:*
    cpe:2.3:a:cisco:unified_communications_manager:4.1:\(3\)sr.5:*:*:*:*:*:*
  • cpe:2.3:a:cisco:unified_communications_manager:4.1:\(3\)sr4:*:*:*:*:*:*
    cpe:2.3:a:cisco:unified_communications_manager:4.1:\(3\)sr4:*:*:*:*:*:*
  • cpe:2.3:a:cisco:unified_communications_manager:4.1:\(3\)sr5:*:*:*:*:*:*
    cpe:2.3:a:cisco:unified_communications_manager:4.1:\(3\)sr5:*:*:*:*:*:*
  • cpe:2.3:a:cisco:unified_communications_manager:4.1:\(3\)sr5b:*:*:*:*:*:*
    cpe:2.3:a:cisco:unified_communications_manager:4.1:\(3\)sr5b:*:*:*:*:*:*
  • cpe:2.3:a:cisco:unified_communications_manager:4.1:\(3\)sr5c:*:*:*:*:*:*
    cpe:2.3:a:cisco:unified_communications_manager:4.1:\(3\)sr5c:*:*:*:*:*:*
  • cpe:2.3:a:cisco:unified_communications_manager:4.1\(3\):*:*:*:*:*:*:*
    cpe:2.3:a:cisco:unified_communications_manager:4.1\(3\):*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:unified_communications_manager:4.1\(3\)sr1:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:unified_communications_manager:4.1\(3\)sr1:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:unified_communications_manager:4.1\(3\)sr2:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:unified_communications_manager:4.1\(3\)sr2:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:unified_communications_manager:4.1\(3\)sr3:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:unified_communications_manager:4.1\(3\)sr3:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:unified_communications_manager:4.1\(3\)sr4:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:unified_communications_manager:4.1\(3\)sr4:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:unified_communications_manager:4.1.1:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:unified_communications_manager:4.1.1:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:unified_communications_manager:4.1.2:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:unified_communications_manager:4.1.2:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:unified_communications_manager:4.1.3:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:unified_communications_manager:4.1.3:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:unified_communications_manager:4.2:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:unified_communications_manager:4.2:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:unified_communications_manager:4.2:4.2\(3\)sr.2:*:*:*:*:*:*
    cpe:2.3:a:cisco:unified_communications_manager:4.2:4.2\(3\)sr.2:*:*:*:*:*:*
  • cpe:2.3:a:cisco:unified_communications_manager:4.2:4.2_\(3\)sr2b:*:*:*:*:*:*
    cpe:2.3:a:cisco:unified_communications_manager:4.2:4.2_\(3\)sr2b:*:*:*:*:*:*
  • cpe:2.3:a:cisco:unified_communications_manager:4.2:4.2_\(3\)sr3:*:*:*:*:*:*
    cpe:2.3:a:cisco:unified_communications_manager:4.2:4.2_\(3\)sr3:*:*:*:*:*:*
  • cpe:2.3:a:cisco:unified_communications_manager:4.2\(3\)sr1:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:unified_communications_manager:4.2\(3\)sr1:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:unified_communications_manager:4.2\(3\)sr2b:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:unified_communications_manager:4.2\(3\)sr2b:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:unified_communications_manager:4.2\(3\)sr3:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:unified_communications_manager:4.2\(3\)sr3:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:unified_communications_manager:4.2\(3\)sr4:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:unified_communications_manager:4.2\(3\)sr4:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:unified_communications_manager:4.2.1:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:unified_communications_manager:4.2.1:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:unified_communications_manager:4.2.2:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:unified_communications_manager:4.2.2:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:unified_communications_manager:4.2.3:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:unified_communications_manager:4.2.3:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:unified_communications_manager:4.2.3_sr3:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:unified_communications_manager:4.2.3_sr3:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:unified_communications_manager:4.2.3sr1:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:unified_communications_manager:4.2.3sr1:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:unified_communications_manager:4.2.3sr2:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:unified_communications_manager:4.2.3sr2:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:unified_communications_manager:4.2.3sr2b:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:unified_communications_manager:4.2.3sr2b:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:unified_communications_manager:4.2_1:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:unified_communications_manager:4.2_1:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:unified_communications_manager:4.2_2:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:unified_communications_manager:4.2_2:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:unified_communications_manager:4.2_3:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:unified_communications_manager:4.2_3:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:unified_communications_manager:4.2_3sr1:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:unified_communications_manager:4.2_3sr1:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:unified_communications_manager:4.3:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:unified_communications_manager:4.3:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:unified_communications_manager:4.3:4.3\(1\)sr.1:*:*:*:*:*:*
    cpe:2.3:a:cisco:unified_communications_manager:4.3:4.3\(1\)sr.1:*:*:*:*:*:*
  • cpe:2.3:a:cisco:unified_communications_manager:4.3\(1\):*:*:*:*:*:*:*
    cpe:2.3:a:cisco:unified_communications_manager:4.3\(1\):*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:unified_communications_manager:4.3\(1\)sr.1:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:unified_communications_manager:4.3\(1\)sr.1:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:unified_communications_manager:4.3\(2\):*:*:*:*:*:*:*
    cpe:2.3:a:cisco:unified_communications_manager:4.3\(2\):*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:unified_communications_manager:4.3\(2\)sr1:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:unified_communications_manager:4.3\(2\)sr1:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:unified_communications_manager:4.3.1:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:unified_communications_manager:4.3.1:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:unified_communications_manager:4.3_1:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:unified_communications_manager:4.3_1:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:unified_communications_manager:6.0:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:unified_communications_manager:6.0:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:unified_communications_manager:6.0\(1\):*:*:*:*:*:*:*
    cpe:2.3:a:cisco:unified_communications_manager:6.0\(1\):*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:unified_communications_manager:6.0\(1a\):*:*:*:*:*:*:*
    cpe:2.3:a:cisco:unified_communications_manager:6.0\(1a\):*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:unified_communications_manager:6.1:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:unified_communications_manager:6.1:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:unified_communications_manager:6.1:\(1a\):*:*:*:*:*:*
    cpe:2.3:a:cisco:unified_communications_manager:6.1:\(1a\):*:*:*:*:*:*
  • cpe:2.3:a:cisco:unified_communications_manager:6.1\(1\):*:*:*:*:*:*:*
    cpe:2.3:a:cisco:unified_communications_manager:6.1\(1\):*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:unified_communications_manager:6.1\(1a\):*:*:*:*:*:*:*
    cpe:2.3:a:cisco:unified_communications_manager:6.1\(1a\):*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:unified_communications_manager:6.1\(1b\):*:*:*:*:*:*:*
    cpe:2.3:a:cisco:unified_communications_manager:6.1\(1b\):*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:unified_communications_manager:6.1\(2\):*:*:*:*:*:*:*
    cpe:2.3:a:cisco:unified_communications_manager:6.1\(2\):*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:unified_communications_manager:6.1\(2\)su1:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:unified_communications_manager:6.1\(2\)su1:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:unified_communications_manager:6.1\(2\)su1a:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:unified_communications_manager:6.1\(2\)su1a:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:unified_communications_manager:6.1.0:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:unified_communications_manager:6.1.0:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:unified_communications_manager:7.0:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:unified_communications_manager:7.0:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:unified_communications_manager:7.0\(1\):*:*:*:*:*:*:*
    cpe:2.3:a:cisco:unified_communications_manager:7.0\(1\):*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:unified_communications_manager:7.0\(2\):*:*:*:*:*:*:*
    cpe:2.3:a:cisco:unified_communications_manager:7.0\(2\):*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:unified_communications_manager:7.1:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:unified_communications_manager:7.1:*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:unified_communications_manager:8.0:*:*:*:*:*:*:*
    cpe:2.3:a:cisco:unified_communications_manager:8.0:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2010-0592: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2025-26205 – Lua 5.4.7, when the debug library is used, has a out-of-bounds read and segmentation violation in mainpositionTV in ltable.c. NOTE: this is dispute...
  • CVE-2025-26204 – Lua 5.4.7, when the debug library is used, has a out-of-bounds read and segmentation violation in equalkey in ltable.c. NOTE: this is disputed beca...
  • CVE-2025-2129 – A vulnerability was found in Mage AI 0.9.75. It has been classified as problematic. This affects an unknown part. The manipulation leads to insecur...
  • CVE-2025-2127 – A vulnerability was found in JoomlaUX JUX Real Estate 3.4.0 on Joomla. It has been classified as problematic. Affected is an unknown function of th...
  • CVE-2025-2126 – A vulnerability was found in JoomlaUX JUX Real Estate 3.4.0 on Joomla and classified as critical. This issue affects some unknown processing of the...