CVE-2017-1126: Infoleak

Published Oct 3, 2017
·
Updated

IBM WebSphere Message Broker (IBM Integration Bus 9.0 and 10.0) could allow an unauthorized user to obtain sensitive information about software versions that could lead to further attacks. IBM X-Force ID: 121341.

Affected Software

27 affected components
IBM Integration Bus=9.0.0.0
IBM Integration Bus=9.0.0.1
IBM Integration Bus=9.0.0.2
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=9.0.0.8
IBM Integration Bus=10.0.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
IBM Integration Bus=10.0.0.8
IBM Integration Bus=10.0.0.9
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 WebSphere Message Broker=8.0.0.8

Event History

Oct 3, 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-1126?

CVE-2017-1126 has a medium severity rating, indicating a potential compromise of sensitive information.

2

How do I fix CVE-2017-1126?

To fix CVE-2017-1126, update your IBM Integration Bus or WebSphere Message Broker to the latest version that addresses this vulnerability.

3

Which versions are affected by CVE-2017-1126?

CVE-2017-1126 affects IBM Integration Bus versions 9.0.0.0 to 9.0.0.8 and 10.0.0.0 to 10.0.0.9, as well as IBM WebSphere Message Broker versions 8.0.0.0 to 8.0.0.8.

4

What kind of information can be exposed due to CVE-2017-1126?

CVE-2017-1126 could allow unauthorized users to obtain sensitive information about the software versions, which may lead to further attacks.

5

Is there a workaround for CVE-2017-1126 if I cannot apply a patch immediately?

A recommended workaround for CVE-2017-1126 is to restrict access to the affected software components until a patch can be applied.

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