6.5
CVE-2013-0451
- EPSS 0.35%
- Published 01.10.2013 11:14:43
- Last modified 11.04.2025 00:51:21
- Source psirt@us.ibm.com
- Teams watchlist Login
- Open Login
SQL injection vulnerability in IBM Maximo Asset Management 6.2 through 6.2.8 and 7.1 through 7.1.1.12 allows remote authenticated users to execute arbitrary SQL commands via unspecified vectors.
Data is provided by the National Vulnerability Database (NVD)
Ibm ≫ Maximo Asset Management Version6.2
Ibm ≫ Maximo Asset Management Version6.2.1
Ibm ≫ Maximo Asset Management Version6.2.2
Ibm ≫ Maximo Asset Management Version6.2.3
Ibm ≫ Maximo Asset Management Version6.2.4
Ibm ≫ Maximo Asset Management Version6.2.5
Ibm ≫ Maximo Asset Management Version6.2.6
Ibm ≫ Maximo Asset Management Version6.2.6.1
Ibm ≫ Maximo Asset Management Version6.2.7
Ibm ≫ Maximo Asset Management Version6.2.8
Ibm ≫ Maximo Asset Management Version7.1
Ibm ≫ Maximo Asset Management Version7.1.1
Ibm ≫ Maximo Asset Management Version7.1.1.1
Ibm ≫ Maximo Asset Management Version7.1.1.2
Ibm ≫ Maximo Asset Management Version7.1.1.5
Ibm ≫ Maximo Asset Management Version7.1.1.6
Ibm ≫ Maximo Asset Management Version7.1.1.7
Ibm ≫ Maximo Asset Management Version7.1.1.8
Ibm ≫ Maximo Asset Management Version7.1.1.9
Ibm ≫ Maximo Asset Management Version7.1.1.10
Ibm ≫ Maximo Asset Management Version7.1.1.11
Ibm ≫ Maximo Asset Management Version7.1.1.12
Zu dieser CVE wurde keine CISA KEV oder CERT.AT-Warnung gefunden.
Type | Source | Score | Percentile |
---|---|---|---|
EPSS | FIRST.org | 0.35% | 0.543 |
Source | Base Score | Exploit Score | Impact Score | Vector string |
---|---|---|---|---|
nvd@nist.gov | 6.5 | 8 | 6.4 |
AV:N/AC:L/Au:S/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.