Vulnerabilities > IBM > Rational Collaborative Lifecycle Management
| DATE | CVE | VULNERABILITY TITLE | RISK |
|---|---|---|---|
| 2017-10-25 | CVE-2017-1295 | Information Exposure vulnerability in IBM Rational Collaborative Lifecycle Management IBM RSA DM contains unspecified vulnerability in CLM Applications with potential for information leakage. | 4.3 |
| 2017-10-25 | CVE-2017-1241 | Information Exposure vulnerability in IBM Rational Collaborative Lifecycle Management An unspecified vulnerability in IBM Jazz Foundation based applications might allow the display of stack trace information to an attacker. | 4.3 |
| 2017-10-25 | CVE-2017-1169 | Cross-site Scripting vulnerability in IBM Rational Collaborative Lifecycle Management IBM DOORS next Generation (DNG/RRC) is vulnerable to cross-site scripting. | 5.4 |
| 2017-10-25 | CVE-2017-1164 | Cross-site Scripting vulnerability in IBM Rational Collaborative Lifecycle Management IBM Jazz Foundation is vulnerable to cross-site scripting. | 5.4 |
| 2017-07-05 | CVE-2016-9700 | Information Exposure vulnerability in IBM products IBM Jazz Foundation could allow an authenticated attacker to obtain sensitive information from error message stack traces. | 4.3 |
| 2017-07-05 | CVE-2016-9746 | Cross-site Scripting vulnerability in IBM products IBM Team Concert (RTC) 4.0, 5.0 and 6.0 is vulnerable to cross-site scripting. | 5.4 |
| 2017-07-05 | CVE-2016-9733 | Cross-site Scripting vulnerability in IBM products IBM Team Concert (RTC) 4.0, 5.0 and 6.0 is vulnerable to cross-site scripting. | 5.4 |
| 2017-07-05 | CVE-2016-9701 | Cross-site Scripting vulnerability in IBM products IBM Team Concert 4.0, 5.0 and 6.0 is vulnerable to cross-site scripting. | 5.4 |
| 2017-06-22 | CVE-2016-9747 | Cross-site Scripting vulnerability in IBM products IBM RELM 4.0, 5.0 and 6.0 is vulnerable to cross-site scripting. | 5.4 |
| 2017-06-13 | CVE-2017-1099 | Information Exposure vulnerability in IBM products IBM Jazz Foundation could expose potentially sensitive information to authenticated users through stack trace error conditions. | 4.3 |