Advisory Published
CVE Published
Updated

CVE-2019-2507

First published: Wed Jan 16 2019(Updated: )

Last updated 24 July 2024

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

Affected SoftwareAffected VersionHow to fix
debian/mysql-5.7
redhat/mysql<5.6.43
5.6.43
redhat/mysql<5.7.25
5.7.25
redhat/mysql<8.0.14
8.0.14
MySQL>=5.6.0<=5.6.42
MySQL>=5.7.0<=5.7.24
MySQL>=8.0.0<=8.0.13

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-2019-2507?

    The severity of CVE-2019-2507 is medium with a severity value of 4.9.

  • Which versions of MySQL are affected by CVE-2019-2507?

    MySQL versions 5.6.42 and prior, 5.7.24 and prior, and 8.0.13 and prior are affected by CVE-2019-2507.

  • How can an attacker exploit CVE-2019-2507?

    An attacker can exploit CVE-2019-2507 by leveraging high privileges and network access via multiple protocols.

  • Is there a fix available for CVE-2019-2507?

    Yes, the fix for CVE-2019-2507 is available in MySQL versions 5.6.43, 5.7.25, and 8.0.14.

  • Where can I find more information about CVE-2019-2507?

    More information about CVE-2019-2507 can be found on the Oracle website and Red Hat Bugzilla.

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