IBM Rational Collaborative Lifecycle Management up to 5.02/6.0 HSTS information disclosure
|CVSS Meta Temp Score|
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
|Current Exploit Price (≈)|
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
|CTI Interest Score|
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
A vulnerability was found in IBM Rational Collaborative Lifecycle Management, Rational DOORS Next Generation, Rational Engineering Lifecycle Manager, Rational Quality Manager, Rational Rhapsody Design Manager, Rational Software Architect Design Manager and Rational Team Concert up to 5.02/6.0 (Testing Software). It has been rated as problematic. This issue affects some unknown functionality of the component HSTS. The manipulation with an unknown input leads to a information disclosure vulnerability. Using CWE to declare the problem leads to CWE-200. Impacted is confidentiality. The summary by CVE is:
IBM Jazz applications (IBM Rational Collaborative Lifecycle Management 5.0 through 5.02 and 6.0 through 6.0.6, IBM Rational DOORS Next Generation 5.0 through 5.02 and 6.0 through 6.0.6, IBM Rational Engineering Lifecycle Manager 5.0 through 5.02 and 6.0 through 6.0.6, IBM Rational Quality Manager 5.0 through 5.02 and 6.0 through 6.0.6, IBM Rational Rhapsody Design Manager 5.0 through 5.02 and 6.0 through 6.0.6, IBM Rational Software Architect Design Manager 5.0 through 5.02 and 6.0 through 6.0.1, IBM Rational Team Concert 5.0 through 5.02 and 6.0 through 6.0.6) could allow a remote attacker to obtain sensitive information, caused by the failure to properly enable HTTP Strict Transport Security. An attacker could exploit this vulnerability to obtain sensitive information using man in the middle techniques. IBM X-Force ID: 145609.
The bug was discovered 11/02/2018. The weakness was published 11/06/2018 (Website). The advisory is shared at exchange.xforce.ibmcloud.com. The identification of this vulnerability is CVE-2018-1694 since 12/13/2017. The attack may be initiated remotely. No form of authentication is needed for a successful 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 04/10/2020). It is expected to see the exploit prices for this product increasing in the near future.
The vulnerability was handled as a non-public zero-day exploit for at least 4 days. During that time the estimated underground price was around $5k-$25k.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Similar entry is available at 126480.
- Rational Collaborative Lifecycle Management
- Rational DOORS Next Generation
- Rational Engineering Lifecycle Manager
- Rational Quality Manager
- Rational Rhapsody Design Manager
- Rational Software Architect Design Manager
- Rational Team Concert
CVSSv3VulDB Meta Base Score: 5.6
VulDB Meta Temp Score: 5.6
VulDB Base Score: 5.3
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.9
NVD Vector: 🔍
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
ExploitingClass: Information disclosure
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔍
Threat IntelligenceThreat: 🔍
CountermeasuresRecommended: no mitigation known
0-Day Time: 🔍
11/02/2018 +324 days 🔍
11/06/2018 +4 days 🔍
11/06/2018 +0 days 🔍
11/07/2018 +1 days 🔍
04/10/2020 +520 days 🔍
Status: Not defined
CVE: CVE-2018-1694 (🔍)
See also: 🔍
EntryCreated: 11/07/2018 07:53 AM
Updated: 04/10/2020 11:22 AM
Changes: (1) vulnerability_discoverydate
Want to stay up to date on a daily basis?
Enable the mail alert feature now!