IBM Daeja ViewONE 4.1.5.1/5.0.2 Logging information disclosure
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 2.9 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic has been found in IBM Daeja ViewONE 4.1.5.1/5.0.2. Impacted is an unknown function of the component Logging. Performing a manipulation results in information disclosure. This vulnerability is reported as CVE-2017-1211. The attack requires a local approach. No exploit exists.
Details
A vulnerability, which was classified as problematic, was found in IBM Daeja ViewONE 4.1.5.1/5.0.2. This affects some unknown processing of the component Logging. 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 Daeja ViewONE Professional, Standard & Virtual 4.1.5.1 and 5.0.2 could disclose sensitive information to a local user when logging is enabled. IBM X-Force ID: 123851.
The bug was discovered 09/18/2017. The weakness was disclosed 10/24/2017 (Website). The advisory is shared at ibm.com. This vulnerability is uniquely identified as CVE-2017-1211 since 11/30/2016. An attack has to be approached locally. No form of authentication is needed for exploitation. 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 36 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 101526†). The entries VDB-108598, VDB-108596 and VDB-108595 are pretty similar. 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: 2.9VulDB Meta Temp Score: 2.9
VulDB Base Score: 3.3
VulDB Temp Score: 3.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 2.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
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 🔍09/18/2017 🔍
10/18/2017 🔍
10/24/2017 🔍
10/24/2017 🔍
10/25/2017 🔍
01/20/2021 🔍
Sources
Vendor: ibm.comAdvisory: ibm.com
Researcher: IBM.
Status: Not defined
Confirmation: 🔍
CVE: CVE-2017-1211 (🔍)
GCVE (CVE): GCVE-0-2017-1211
GCVE (VulDB): GCVE-100-108597
X-Force: 123851
SecurityFocus: 101526 - Multiple IBM Products CVE-2017-1211 Local Information Disclosure Vulnerability
See also: 🔍
Entry
Created: 10/25/2017 09:16Updated: 01/20/2021 16:02
Changes: 10/25/2017 09:16 (60), 11/30/2019 15:26 (4), 01/20/2021 15:56 (2), 01/20/2021 16:02 (1)
Complete: 🔍
Cache ID: 216:EEF: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.