An issue was discovered in these Pivotal RabbitMQ versions: all 3.4.x
versions, all 3.5.x versions, and 3.6.x versions prior to 3.6.9; and these
RabbitMQ for PCF versions: all 1.5.x versions, 1.6.x versions prior to
1.6.18, and 1.7.x versions prior to 1.7.15. RabbitMQ management UI stores
signed-in user credentials in a browser's local storage without expiration,
making it possible to retrieve them using a chained attack.
CVE-2017-4966 is classified as a medium-severity vulnerability due to its potential to allow unauthorized access to sensitive information within RabbitMQ.
2
How do I fix CVE-2017-4966?
To fix CVE-2017-4966, upgrade your RabbitMQ installation to version 3.6.9 or later for 3.6.x series, or to version 1.6.18 or later for RabbitMQ for PCF.
3
What versions of RabbitMQ are affected by CVE-2017-4966?
CVE-2017-4966 affects all versions of RabbitMQ in the 3.4.x, 3.5.x, and 3.6.x series prior to 3.6.9, as well as RabbitMQ for PCF versions before 1.6.18.
4
What impact does CVE-2017-4966 have on RabbitMQ users?
CVE-2017-4966 may allow attackers to gain unauthorized access to the RabbitMQ management UI, potentially exposing sensitive configuration and user data.
5
Is there a workaround for CVE-2017-4966?
A potential workaround for CVE-2017-4966 includes disabling the management plugin until an upgrade can be applied.
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.