| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.6 | $0-$5k | 0.00 |
Summary
A vulnerability was found in IBM Cognos Business Intelligence 10.1. It has been rated as problematic. The affected element is an unknown function. Performing a manipulation results in path traversal. This vulnerability is known as CVE-2013-2988. No exploit is available.
Details
A vulnerability, which was classified as problematic, was found in IBM Cognos Business Intelligence 10.1 (Business Process Management Software). This affects an unknown function. The manipulation with an unknown input leads to a path traversal vulnerability. CWE is classifying the issue as CWE-22. The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. This is going to have an impact on confidentiality. The summary by CVE is:
Absolute path traversal vulnerability in the server in IBM Cognos Business Intelligence (BI) 8.4.1, 10.1, 10.1.1, 10.2, and 10.2.1 allows remote authenticated users to read files by leveraging the Report Author privilege, a different vulnerability than CVE-2013-2978.
The weakness was published 08/26/2013 (Website). The advisory is shared at xforce.iss.net. This vulnerability is uniquely identified as CVE-2013-2988 since 04/12/2013. The exploitability is told to be difficult. It is possible to initiate the attack remotely. 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 T1006 for this issue.
It is declared as highly functional.
The vulnerability is also documented in the databases at X-Force (84010) and SecurityFocus (BID 62003†). Similar entries are available at VDB-64784 and VDB-64783. 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: 3.7VulDB Meta Temp Score: 3.6
VulDB Base Score: 3.7
VulDB Temp Score: 3.6
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: Path traversalCWE: CWE-22
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
04/12/2013 🔍08/21/2013 🔍
08/26/2013 🔍
08/26/2013 🔍
03/24/2015 🔍
02/27/2018 🔍
Sources
Vendor: ibm.comAdvisory: xforce.iss.net
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2013-2988 (🔍)
GCVE (CVE): GCVE-0-2013-2988
GCVE (VulDB): GCVE-100-64785
X-Force: 84010 - IBM Cognos Business Intelligence Report Author information disclosure 2
SecurityFocus: 62003 - IBM Cognos Business Intelligence CVE-2013-2988 Access Bypass Vulnerability
See also: 🔍
Entry
Created: 03/24/2015 15:54Updated: 02/27/2018 03:09
Changes: 03/24/2015 15:54 (48), 02/27/2018 03:09 (8)
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.