critical
9.8
CWE
502
Advisory Published
Updated

CVE-2017-8045

First published: Mon Nov 27 2017(Updated: )

In Pivotal Spring AMQP versions prior to 1.7.4, 1.6.11, and 1.5.7, an org.springframework.amqp.core.Message may be unsafely deserialized when being converted into a string. A malicious payload could be crafted to exploit this and enable a remote code execution attack.

Credit: security_alert@emc.com

Affected SoftwareAffected VersionHow to fix
Pivotal Software Spring Advanced Message Queuing Protocol=1.5.0
Pivotal Software Spring Advanced Message Queuing Protocol=1.5.0-m1
Pivotal Software Spring Advanced Message Queuing Protocol=1.5.0-rc1
Pivotal Software Spring Advanced Message Queuing Protocol=1.5.1
Pivotal Software Spring Advanced Message Queuing Protocol=1.5.2
Pivotal Software Spring Advanced Message Queuing Protocol=1.5.3
Pivotal Software Spring Advanced Message Queuing Protocol=1.5.4
Pivotal Software Spring Advanced Message Queuing Protocol=1.5.5
Pivotal Software Spring Advanced Message Queuing Protocol=1.5.6
Pivotal Software Spring Advanced Message Queuing Protocol=1.6.0
Pivotal Software Spring Advanced Message Queuing Protocol=1.6.0-m1
Pivotal Software Spring Advanced Message Queuing Protocol=1.6.0-m2
Pivotal Software Spring Advanced Message Queuing Protocol=1.6.0-rc1
Pivotal Software Spring Advanced Message Queuing Protocol=1.6.1
Pivotal Software Spring Advanced Message Queuing Protocol=1.6.2
Pivotal Software Spring Advanced Message Queuing Protocol=1.6.3
Pivotal Software Spring Advanced Message Queuing Protocol=1.6.4
Pivotal Software Spring Advanced Message Queuing Protocol=1.6.5
Pivotal Software Spring Advanced Message Queuing Protocol=1.6.6
Pivotal Software Spring Advanced Message Queuing Protocol=1.6.7
Pivotal Software Spring Advanced Message Queuing Protocol=1.6.8
Pivotal Software Spring Advanced Message Queuing Protocol=1.6.9
Pivotal Software Spring Advanced Message Queuing Protocol=1.6.10
Pivotal Software Spring Advanced Message Queuing Protocol=1.7.0
Pivotal Software Spring Advanced Message Queuing Protocol=1.7.1
Pivotal Software Spring Advanced Message Queuing Protocol=1.7.2
Pivotal Software Spring Advanced Message Queuing Protocol=1.7.3

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-8045?

    The severity of CVE-2017-8045 is critical with a severity value of 9.8.

  • How does CVE-2017-8045 affect Pivotal Spring AMQP?

    CVE-2017-8045 affects Pivotal Spring AMQP versions prior to 1.7.4, 1.6.11, and 1.5.7.

  • What is the vulnerability description for CVE-2017-8045?

    CVE-2017-8045 allows a malicious payload to be crafted which may enable remote code execution by exploiting unsafe deserialization of org.springframework.amqp.core.Message.

  • How can I fix CVE-2017-8045?

    To fix CVE-2017-8045, update Pivotal Spring AMQP to version 1.7.4, 1.6.11, or 1.5.7.

  • Are there any references for CVE-2017-8045?

    Yes, you can find more information about CVE-2017-8045 at the following references: http://www.securityfocus.com/bid/100936, https://pivotal.io/security/cve-2017-8045.

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