9.8
CVE-2017-1670
- EPSS 0.68%
- Published 09.01.2018 20:29:00
- Last modified 21.11.2024 03:22:11
- Source psirt@us.ibm.com
- Teams watchlist Login
- Open Login
IBM Tivoli Key Lifecycle Manager 2.5, 2.6, and 2.7 is vulnerable to SQL injection. A remote attacker could send specially-crafted SQL statements, which could allow the attacker to view, add, modify or delete information in the back-end database. IBM X-Force ID: 133637.
Data is provided by the National Vulnerability Database (NVD)
Ibm ≫ Security Key Lifecycle Manager Version2.5.0
Ibm ≫ Security Key Lifecycle Manager Version2.5.0.1
Ibm ≫ Security Key Lifecycle Manager Version2.5.0.2
Ibm ≫ Security Key Lifecycle Manager Version2.5.0.3
Ibm ≫ Security Key Lifecycle Manager Version2.5.0.4
Ibm ≫ Security Key Lifecycle Manager Version2.5.0.5
Ibm ≫ Security Key Lifecycle Manager Version2.5.0.6
Ibm ≫ Security Key Lifecycle Manager Version2.5.0.7
Ibm ≫ Security Key Lifecycle Manager Version2.5.0.8
Ibm ≫ Security Key Lifecycle Manager Version2.6.0
Ibm ≫ Security Key Lifecycle Manager Version2.6.0.1
Ibm ≫ Security Key Lifecycle Manager Version2.6.0.2
Ibm ≫ Security Key Lifecycle Manager Version2.6.0.3
Ibm ≫ Security Key Lifecycle Manager Version2.7.0
Ibm ≫ Security Key Lifecycle Manager Version2.7.0.1
Ibm ≫ Security Key Lifecycle Manager Version2.7.0.2
Zu dieser CVE wurde keine CISA KEV oder CERT.AT-Warnung gefunden.
Type | Source | Score | Percentile |
---|---|---|---|
EPSS | FIRST.org | 0.68% | 0.705 |
Source | Base Score | Exploit Score | Impact Score | Vector string |
---|---|---|---|---|
nvd@nist.gov | 9.8 | 3.9 | 5.9 |
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
|
nvd@nist.gov | 7.5 | 10 | 6.4 |
AV:N/AC:L/Au:N/C:P/I:P/A:P
|
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.