IBM Security Privileged Identity Manager 2.0.2/2.1.0 Credentials information disclosure
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.4 | $0-$5k | 0.00 |
Summary
A vulnerability was found in IBM Security Privileged Identity Manager 2.0.2/2.1.0. It has been rated as problematic. The affected element is an unknown function. The manipulation leads to information disclosure (Credentials). This vulnerability is listed as CVE-2016-5960. The attack must be carried out locally. There is no available exploit.
Details
A vulnerability, which was classified as problematic, has been found in IBM Security Privileged Identity Manager 2.0.2/2.1.0. This issue affects an unknown function. The manipulation with an unknown input leads to a information disclosure vulnerability (Credentials). Using CWE to declare the problem leads to CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. Impacted is confidentiality. The summary by CVE is:
IBM Security Privileged Identity Manager 2.0.2 and 2.1.0 stores user credentials in plain in clear text which can be read by a local user. IBM X-Force ID: 116171.
The bug was discovered 06/02/2017. The weakness was presented 06/07/2017 (Website). The advisory is shared at ibm.com. The identification of this vulnerability is CVE-2016-5960 since 06/29/2016. An attack has to be approached locally. The successful exploitation requires a simple authentication. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1592 for this issue.
The vulnerability was handled as a non-public zero-day exploit for at least 5 days. During that time the estimated underground price was around $0-$5k.
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 vulnerability database at SecurityFocus (BID 98825†). See VDB-102052 for similar entry. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
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: 4.4VulDB Meta Temp Score: 4.4
VulDB Base Score: 3.3
VulDB Temp Score: 3.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.5
NVD Vector: 🔍
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
Name: CredentialsClass: Information disclosure / Credentials
CWE: CWE-200 / CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
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
06/29/2016 🔍06/02/2017 🔍
06/02/2017 🔍
06/07/2017 🔍
06/07/2017 🔍
06/07/2017 🔍
12/26/2020 🔍
Sources
Vendor: ibm.comAdvisory: ibm.com
Status: Not defined
Confirmation: 🔍
CVE: CVE-2016-5960 (🔍)
GCVE (CVE): GCVE-0-2016-5960
GCVE (VulDB): GCVE-100-102053
X-Force: 116171
SecurityFocus: 98825 - IBM Security Privileged Identity Manager CVE-2016-5960 Local Information Disclosure Vulnerability
See also: 🔍
Entry
Created: 06/07/2017 23:20Updated: 12/26/2020 11:20
Changes: 06/07/2017 23:20 (60), 10/14/2019 11:55 (4), 12/26/2020 11:20 (2)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.