IBM Tivoli Workload Scheduler 8.6.0/9.1.0/9.2.0 information disclosure
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.3 | $0-$5k | 0.00 |
Summary
A vulnerability was found in IBM Tivoli Workload Scheduler 8.6.0/9.1.0/9.2.0. It has been classified as problematic. Affected by this issue is some unknown functionality. Performing a manipulation results in information disclosure. This vulnerability is identified as CVE-2017-1716. The attack is only possible with local access. There is not any exploit available.
Details
A vulnerability was found in IBM Tivoli Workload Scheduler 8.6.0/9.1.0/9.2.0 (Directory Service Software). It has been classified as problematic. This affects an unknown code block. The manipulation with an unknown input leads to a information disclosure vulnerability. CWE is classifying the issue as CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. This is going to have an impact on confidentiality. The summary by CVE is:
IBM Tivoli Workload Scheduler 8.6.0, 9.1.0, and 9.2.0 could disclose sensitive information to a local attacker due to improper permission settings. IBM X-Force ID: 134638.
The bug was discovered 11/24/2017. The weakness was released 12/13/2017 (Website). The advisory is shared at www-01.ibm.com. This vulnerability is uniquely identified as CVE-2017-1716 since 11/30/2016. An attack has to be approached locally. The requirement for exploitation is a 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 19 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 101974†). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
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: 3.3VulDB Meta Temp Score: 3.3
VulDB Base Score: 3.3
VulDB Temp Score: 3.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 3.3
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
Class: Information disclosureCWE: 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
11/30/2016 🔍11/24/2017 🔍
11/24/2017 🔍
12/13/2017 🔍
12/13/2017 🔍
12/14/2017 🔍
01/27/2021 🔍
Sources
Vendor: ibm.comAdvisory: www-01.ibm.com
Researcher: David Lodge
Status: Not defined
Confirmation: 🔍
CVE: CVE-2017-1716 (🔍)
GCVE (CVE): GCVE-0-2017-1716
GCVE (VulDB): GCVE-100-110661
X-Force: 134638
SecurityFocus: 101974 - IBM Workload Scheduler CVE-2017-1716 Local Information Disclosure Vulnerability
Entry
Created: 12/14/2017 07:53Updated: 01/27/2021 11:27
Changes: 12/14/2017 07:53 (59), 12/15/2019 08:27 (4), 01/27/2021 11:22 (2), 01/27/2021 11:27 (1)
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.