First published: Tue Jul 03 2018(Updated: )
IBM Rational Quality Manager and IBM Rational Collaborative Lifecycle Management 5.0 through 5.0.2 and 6.0 through 6.0.5 are vulnerable to cross-site scripting. This vulnerability allows users to embed arbitrary JavaScript code in the Web UI thus altering the intended functionality potentially leading to credentials disclosure within a trusted session. IBM X-Force ID: 131760.
Credit: psirt@us.ibm.com
Affected Software | Affected Version | How to fix |
---|---|---|
IBM Collaborative Lifecycle Management | =5.0 | |
IBM Collaborative Lifecycle Management | =5.0.1 | |
IBM Collaborative Lifecycle Management | =5.0.2 | |
IBM Collaborative Lifecycle Management | =6.0 | |
IBM Collaborative Lifecycle Management | =6.0.1 | |
IBM Collaborative Lifecycle Management | =6.0.2 | |
IBM Collaborative Lifecycle Management | =6.0.3 | |
IBM Collaborative Lifecycle Management | =6.0.4 | |
IBM Collaborative Lifecycle Management | =6.0.5 | |
IBM Rational Quality Manager | =5.0 | |
IBM Rational Quality Manager | =5.0.1 | |
IBM Rational Quality Manager | =5.0.2 | |
IBM Rational Quality Manager | =6.0 | |
IBM Rational Quality Manager | =6.0.1 | |
IBM Rational Quality Manager | =6.0.2 | |
IBM Rational Quality Manager | =6.0.3 | |
IBM Rational Quality Manager | =6.0.4 | |
IBM Rational Quality Manager | =6.0.5 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2017-1561 is rated as high severity due to its potential impact on user data through cross-site scripting.
To fix CVE-2017-1561, upgrade to the latest versions of IBM Rational Quality Manager or IBM Rational Collaborative Lifecycle Management that address this vulnerability.
CVE-2017-1561 affects IBM Rational Quality Manager versions 5.0 to 5.0.2 and 6.0 to 6.0.5, as well as IBM Rational Collaborative Lifecycle Management versions 5.0 to 5.0.2 and 6.0 to 6.0.5.
Exploiting CVE-2017-1561 allows attackers to inject arbitrary JavaScript code into the web UI, potentially compromising user sessions and leading to unauthorized actions.
Currently, there are no documented workarounds for CVE-2017-1561; applying the patch or upgrade is the recommended course of action.