medium
5.4
CWE
79
Advisory Published
Updated

CVE-2016-6036: XSS

First published: Fri Mar 31 2017(Updated: )

IBM Rational Quality Manager (RQM) 4.0, 5.0, and 6.0 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 Reference #: 2000784.

Credit: psirt@us.ibm.com

Affected SoftwareAffected VersionHow to fix
IBM Rational Quality Manager=4.0
IBM Rational Quality Manager=4.0.1
IBM Rational Quality Manager=4.0.2
IBM Rational Quality Manager=4.0.3
IBM Rational Quality Manager=4.0.4
IBM Rational Quality Manager=4.0.5
IBM Rational Quality Manager=4.0.6
IBM Rational Quality Manager=4.0.7
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

Remedy

https://www.ibm.com/support/docview.wss?uid=swg22000784

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Read MoreStart Free Trial

Reference Links

Frequently Asked Questions

  • What is the severity of CVE-2016-6036?

    CVE-2016-6036 is classified as a medium-severity vulnerability due to the potential for cross-site scripting and credential disclosure.

  • How do I fix CVE-2016-6036?

    To address CVE-2016-6036, update IBM Rational Quality Manager to a patched version that resolves the cross-site scripting vulnerability.

  • Which versions of IBM Rational Quality Manager are affected by CVE-2016-6036?

    CVE-2016-6036 affects IBM Rational Quality Manager versions 4.0 through 6.0.3.

  • What impact does CVE-2016-6036 have on users?

    If exploited, CVE-2016-6036 can allow attackers to execute arbitrary JavaScript and potentially steal user credentials during a trusted session.

  • Is there a workaround for CVE-2016-6036 if an update cannot be applied?

    While the recommended fix is to update to a secure version, mitigating cross-site scripting by restricting user input can serve as a temporary workaround for CVE-2016-6036.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203