Advisory Published
CVE Published
Updated

CVE-2018-2583

First published: Wed Jan 17 2018(Updated: )

Last updated 24 July 2024

Credit: secalert_us@oracle.com secalert_us@oracle.com

Affected SoftwareAffected VersionHow to fix
redhat/mysql<5.6.39
5.6.39
redhat/mysql<5.7.21
5.7.21
debian/mysql-5.5
debian/mysql-5.7
MySQL>=5.6.0<=5.6.38
MySQL>5.7.0<=5.7.20

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-2018-2583?

    CVE-2018-2583 has been classified as a high severity vulnerability due to the ease with which it can be exploited by privileged attackers.

  • How do I fix CVE-2018-2583?

    To remediate CVE-2018-2583, upgrade your MySQL Server to version 5.6.39 or 5.7.21 or higher.

  • Which MySQL versions are affected by CVE-2018-2583?

    CVE-2018-2583 affects MySQL versions 5.6.38 and earlier, as well as 5.7.20 and earlier.

  • Can CVE-2018-2583 be exploited remotely?

    Yes, CVE-2018-2583 can be easily exploited by attackers with network access, making it a critical security concern.

  • What components of MySQL does CVE-2018-2583 impact?

    CVE-2018-2583 specifically impacts the MySQL Server component, particularly the Stored Procedure subcomponent.

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