medium
5.4
CWE
79
Advisory Published
Updated

CVE-2017-1101: XSS

First published: Tue Jun 13 2017(Updated: )

IBM Quality Manager (RQM) 4.0, 5.0, and 6.0 is 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: 120662.

Credit: psirt@us.ibm.com

Affected SoftwareAffected VersionHow to fix
IBM Rational Quality Manager=4.0
IBM Rational Quality Manager=4.0.0.1
IBM Rational Quality Manager=4.0.0.2
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

http://www.ibm.com/support/docview.wss?uid=swg22004428

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-2017-1101?

    CVE-2017-1101 has a medium severity rating due to its potential for cross-site scripting attacks.

  • How do I fix CVE-2017-1101?

    To fix CVE-2017-1101, update your IBM Rational Quality Manager to the latest patched version provided by IBM.

  • What types of attacks can CVE-2017-1101 enable?

    CVE-2017-1101 can enable attackers to execute arbitrary JavaScript code, which may lead to unauthorized access and credential disclosure.

  • Which versions of IBM Quality Manager are affected by CVE-2017-1101?

    CVE-2017-1101 affects IBM Quality Manager versions 4.0, 5.0, and 6.0, including their subsequent minor releases.

  • Is there a workaround for CVE-2017-1101?

    While the best approach is to apply the available patches, implementing input validation could serve as a temporary workaround for CVE-2017-1101.

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