IBM Tivoli Monitoring up to 6.2.0.1 Access Restriction access control
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.8 | $5k-$25k | 0.00 |
Summary
A vulnerability identified as critical has been detected in IBM Tivoli Monitoring up to 6.2.0.1. The impacted element is an unknown function of the component Access Restriction. The manipulation leads to access control. This vulnerability is uniquely identified as CVE-2014-6141. No exploit exists.
Details
A vulnerability was found in IBM Tivoli Monitoring up to 6.2.0.1 (Directory Service Software). It has been rated as critical. This issue affects some unknown functionality of the component Access Restriction. The manipulation with an unknown input leads to a access control vulnerability. Using CWE to declare the problem leads to CWE-264. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
IBM Tivoli Monitoring (ITM) 6.2.0 through FP03, 6.2.1 through FP04, 6.2.2 through FP09, 6.2.3 through FP05, and 6.3.0 before FP04 allows remote authenticated users to bypass intended access restrictions and execute arbitrary commands by leveraging Take Action view authority to modify in-progress commands.
The weakness was disclosed 02/01/2015 (Website). The advisory is shared at xforce.iss.net. The identification of this vulnerability is CVE-2014-6141 since 09/02/2014. The attack may be initiated remotely. A simple authentication is required for exploitation. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 06/20/2017). MITRE ATT&CK project uses the attack technique T1068 for this issue.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the databases at X-Force (96911), SecurityFocus (BID 72315†) and Vulnerability Center (SBV-48633†). 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: 8.8VulDB Meta Temp Score: 8.8
VulDB Base Score: 8.8
VulDB Temp Score: 8.8
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: Access controlCWE: CWE-264
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
09/02/2014 🔍12/08/2014 🔍
12/08/2014 🔍
02/01/2015 🔍
02/01/2015 🔍
02/12/2015 🔍
03/27/2015 🔍
06/20/2017 🔍
Sources
Vendor: ibm.comAdvisory: xforce.iss.net
Status: Not defined
Confirmation: 🔍
CVE: CVE-2014-6141 (🔍)
GCVE (CVE): GCVE-0-2014-6141
GCVE (VulDB): GCVE-100-73817
X-Force: 96911
SecurityFocus: 72315 - IBM Tivoli Monitoring CVE-2014-6141 Remote Command Execution Vulnerability
Vulnerability Center: 48633 - IBM Tivoli Monitoring Remote Security Bypass and Code Execution Vulnerability, High
Entry
Created: 03/27/2015 14:56Updated: 06/20/2017 08:29
Changes: 03/27/2015 14:56 (54), 06/20/2017 08:29 (4)
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.