| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.0 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, has been found in IBM Maximo Asset Management up to 7.0. This impacts an unknown function. The manipulation leads to sql injection. This vulnerability is traded as CVE-2013-4017. It is possible to initiate the attack remotely. There is no exploit available. It is advisable to upgrade the affected component.
Details
A vulnerability was found in IBM Maximo Asset Management up to 7.0 (Asset Management Software) and classified as critical. This issue affects an unknown functionality. The manipulation with an unknown input leads to a sql injection vulnerability. Using CWE to declare the problem leads to CWE-89. 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. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
SQL injection vulnerability in IBM Maximo Asset Management 7.1 before 7.1.1.12 allows remote attackers to execute arbitrary SQL commands via unspecified vectors.
The weakness was shared 10/01/2013 (Website). The advisory is shared at www-01.ibm.com. The identification of this vulnerability is CVE-2013-4017 since 06/07/2013. The exploitation is known to be easy. The attack may be initiated remotely. The successful exploitation needs a simple authentication. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1505 for this issue.
It is declared as highly functional.
Upgrading to version 7.1 eliminates this vulnerability.
The vulnerability is also documented in the databases at X-Force (85794) and Secunia (SA55068†). The entries VDB-65139, VDB-65138, VDB-65137 and VDB-65136 are related to this item. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://www.ibm.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.3VulDB Meta Temp Score: 6.0
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Sql injectionCWE: CWE-89 / CWE-74 / CWE-707
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Highly functional
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Maximo Asset Management 7.1
Timeline
06/07/2013 🔍09/27/2013 🔍
10/01/2013 🔍
10/01/2013 🔍
03/24/2015 🔍
02/25/2018 🔍
Sources
Vendor: ibm.comAdvisory: www-01.ibm.com
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2013-4017 (🔍)
GCVE (CVE): GCVE-0-2013-4017
GCVE (VulDB): GCVE-100-65129
X-Force: 85794 - IBM Maximo Asset Management SQL injection
Secunia: 55068 - IBM Multiple Asset and Service Management Products Multiple Vulnerabilities, Moderately Critical
See also: 🔍
Entry
Created: 03/24/2015 15:54Updated: 02/25/2018 10:07
Changes: 03/24/2015 15:54 (51), 02/25/2018 10:07 (7)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.