CWE
287
Advisory Published
Updated

CVE-2012-5952

First published: Wed Feb 20 2013(Updated: )

IBM WebSphere Message Broker 6.1 before 6.1.0.12, 7.0 before 7.0.0.6, and 8.0 before 8.0.0.2 does not validate Basic Authentication credentials before proceeding to WS-Addressing and WS-Security operations, which allows remote attackers to trigger transmission of unauthenticated messages via unspecified vectors.

Credit: psirt@us.ibm.com

Affected SoftwareAffected VersionHow to fix
IBM WebSphere Message Broker=6.1
IBM WebSphere Message Broker=6.1.0.1
IBM WebSphere Message Broker=6.1.0.2
IBM WebSphere Message Broker=6.1.0.3
IBM WebSphere Message Broker=6.1.0.4
IBM WebSphere Message Broker=6.1.0.5
IBM WebSphere Message Broker=6.1.0.6
IBM WebSphere Message Broker=6.1.0.7
IBM WebSphere Message Broker=6.1.0.8
IBM WebSphere Message Broker=6.1.0.9
IBM WebSphere Message Broker=6.1.0.10
IBM WebSphere Message Broker=6.1.0.11
IBM WebSphere Message Broker=7.0.
IBM WebSphere Message Broker=7.0.0.1
IBM WebSphere Message Broker=7.0.0.2
IBM WebSphere Message Broker=7.0.0.3
IBM WebSphere Message Broker=7.0.0.4
IBM WebSphere Message Broker=7.0.0.5
IBM WebSphere Message Broker=8.0
IBM WebSphere Message Broker=8.0.0.1

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.

Frequently Asked Questions

  • What is the severity of CVE-2012-5952?

    CVE-2012-5952 has a medium severity rating, which indicates potential impact on confidentiality and integrity.

  • How do I fix CVE-2012-5952?

    To fix CVE-2012-5952, upgrade IBM WebSphere Message Broker to version 6.1.0.12, 7.0.0.6, or 8.0.0.2 or later.

  • What versions of IBM WebSphere Message Broker are affected by CVE-2012-5952?

    CVE-2012-5952 affects IBM WebSphere Message Broker versions 6.1 before 6.1.0.12, 7.0 before 7.0.0.6, and 8.0 before 8.0.0.2.

  • What type of attack does CVE-2012-5952 allow?

    CVE-2012-5952 allows remote attackers to send unauthenticated messages by bypassing basic authentication.

  • Is there a workaround for CVE-2012-5952?

    Currently, there are no official workarounds for CVE-2012-5952, and the best mitigation is upgrading to the patched versions.

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