CVE-2017-1207: Medium severity ibm websphere message broker vulnerability

Published Jul 5, 2017
·
Updated

IBM WebSphere Message Broker stores user credentials in plain in clear text which can be read by a local user. IBM X-Force ID: 123777.

Affected Software

24 affected components
IBM WebSphere Message Broker=8.0.0.0
IBM WebSphere Message Broker=8.0.0.1
IBM WebSphere Message Broker=8.0.0.2
IBM WebSphere Message Broker=8.0.0.3
IBM WebSphere Message Broker=8.0.0.4
IBM WebSphere Message Broker=8.0.0.5
IBM WebSphere Message Broker=8.0.0.6
IBM WebSphere Message Broker=8.0.0.7
IBM Integration Bus=9.0.0
IBM Integration Bus=9.0.0.1
IBM Integration Bus=9.0.0.2
IBM Integration Bus=9.0.0.3
IBM Integration Bus=9.0.0.4
IBM Integration Bus=9.0.0.5
IBM Integration Bus=9.0.0.6
IBM Integration Bus=9.0.0.7
IBM Integration Bus=10.0.0
IBM Integration Bus=10.0.0.1
IBM Integration Bus=10.0.0.2
IBM Integration Bus=10.0.0.3
IBM Integration Bus=10.0.0.4
IBM Integration Bus=10.0.0.5
IBM Integration Bus=10.0.0.6
IBM Integration Bus=10.0.0.7

Event History

Jul 5, 2017
CVE Published
via MITRE·05:00 PM
Data Sourced
via MITRE·05:00 PM
DescriptionWeakness
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2017-1207?

CVE-2017-1207 has a medium severity rating due to the exposure of user credentials in plain text.

2

How do I fix CVE-2017-1207?

To fix CVE-2017-1207, secure user credentials by storing them in an encrypted format and apply any available patches from IBM.

3

Which versions are affected by CVE-2017-1207?

CVE-2017-1207 affects IBM WebSphere Message Broker versions 8.0.0.0 through 8.0.0.7 and IBM Integration Bus versions 9.0.0 through 10.0.7.

4

What are the risks associated with CVE-2017-1207?

The risks associated with CVE-2017-1207 include unauthorized access to user credentials by local users, potentially leading to data breaches.

5

Is there a workaround for CVE-2017-1207?

While the recommended solution is to patch the software, an immediate workaround includes implementing strict access controls to limit local user access.

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.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203