IBM Maximo Asset Management up to 7.5.0.1 privileges management
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.0 | $0-$5k | 0.00 |
Summary
A vulnerability was found in IBM Maximo Asset Management up to 7.5.0.1. It has been rated as critical. Affected by this issue is some unknown functionality. Performing a manipulation results in privileges management. This vulnerability is identified as CVE-2013-3047. There is not any exploit available. Upgrading the affected component is advised.
Details
A vulnerability was found in IBM Maximo Asset Management up to 7.5.0.1 (Asset Management Software). It has been classified as critical. This affects an unknown function. The manipulation with an unknown input leads to a privileges management vulnerability. CWE is classifying the issue as CWE-269. The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
IBM Maximo Asset Management 7.1 before 7.1.1.12 and 7.5 before 7.5.0.5 allows remote authenticated users to gain privileges via unspecified vectors.
The weakness was released 10/01/2013 (Website). The advisory is shared at www-01.ibm.com. This vulnerability is uniquely identified as CVE-2013-3047 since 04/12/2013. The exploitability is told to be easy. It is possible to initiate the attack remotely. The successful exploitation requires a authentication. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1068 for this issue.
It is declared as highly functional.
Upgrading to version 7.5.0.2 eliminates this vulnerability.
The vulnerability is also documented in the databases at X-Force (84844) and Secunia (SA55068†). Entries connected to this vulnerability are available at VDB-65139, VDB-65138, VDB-65137 and VDB-65136. 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: Privileges managementCWE: CWE-269 / CWE-266
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.5.0.2
Timeline
04/12/2013 🔍09/27/2013 🔍
10/01/2013 🔍
10/01/2013 🔍
03/24/2015 🔍
02/11/2018 🔍
Sources
Vendor: ibm.comAdvisory: www-01.ibm.com
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2013-3047 (🔍)
GCVE (CVE): GCVE-0-2013-3047
GCVE (VulDB): GCVE-100-65121
X-Force: 84844 - IBM Maximo Asset Management privilege escalation
Secunia: 55068 - IBM Multiple Asset and Service Management Products Multiple Vulnerabilities, Moderately Critical
See also: 🔍
Entry
Created: 03/24/2015 15:54Updated: 02/11/2018 12:03
Changes: 03/24/2015 15:54 (51), 02/11/2018 12:03 (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.