CWE
20
Advisory Published
Updated

CVE-2009-4028: Input Validation

First published: Mon Nov 30 2009(Updated: )

The vio_verify_callback function in viosslfactories.c in MySQL 5.0.x before 5.0.88 and 5.1.x before 5.1.41, when OpenSSL is used, accepts a value of zero for the depth of X.509 certificates, which allows man-in-the-middle attackers to spoof arbitrary SSL-based MySQL servers via a crafted certificate, as demonstrated by a certificate presented by a server linked against the yaSSL library.

Credit: secalert@redhat.com

Affected SoftwareAffected VersionHow to fix
MySQL (MySQL-common)<=5.0.87
MySQL (MySQL-common)=5.0.0
MySQL (MySQL-common)=5.0.1
MySQL (MySQL-common)=5.0.2
MySQL (MySQL-common)=5.0.3
MySQL (MySQL-common)=5.0.4
MySQL (MySQL-common)=5.0.5
MySQL (MySQL-common)=5.0.5.0.21
MySQL (MySQL-common)=5.0.10
MySQL (MySQL-common)=5.0.15
MySQL (MySQL-common)=5.0.16
MySQL (MySQL-common)=5.0.17
MySQL (MySQL-common)=5.0.20
MySQL (MySQL-common)=5.0.22.1.0.1
MySQL (MySQL-common)=5.0.24
MySQL (MySQL-common)=5.0.30
MySQL (MySQL-common)=5.0.36
MySQL (MySQL-common)=5.0.44
MySQL (MySQL-common)=5.0.54
MySQL (MySQL-common)=5.0.56
MySQL (MySQL-common)=5.0.60
MySQL (MySQL-common)=5.0.66
MySQL (MySQL-common)=5.0.82
MySQL (MySQL-common)=5.0.84
MySQL (MySQL-common)=5.1.5
MySQL (MySQL-common)=5.1.23
MySQL (MySQL-common)=5.1.31
MySQL (MySQL-common)=5.1.32
MySQL (MySQL-common)=5.1.34
MySQL (MySQL-common)=5.1.37
Oracle MySQL=5.0.0-alpha
Oracle MySQL=5.0.3-beta
Oracle MySQL=5.0.6
Oracle MySQL=5.0.7
Oracle MySQL=5.0.8
Oracle MySQL=5.0.11
Oracle MySQL=5.0.12
Oracle MySQL=5.0.13
Oracle MySQL=5.0.14
Oracle MySQL=5.0.18
Oracle MySQL=5.0.19
Oracle MySQL=5.0.21
Oracle MySQL=5.0.22
Oracle MySQL=5.0.23
Oracle MySQL=5.0.25
Oracle MySQL=5.0.26
Oracle MySQL=5.0.27
Oracle MySQL=5.0.30-sp1
Oracle MySQL=5.0.32
Oracle MySQL=5.0.33
Oracle MySQL=5.0.37
Oracle MySQL=5.0.38
Oracle MySQL=5.0.41
Oracle MySQL=5.0.42
Oracle MySQL=5.0.45
Oracle MySQL=5.0.50
Oracle MySQL=5.0.51
Oracle MySQL=5.0.52
Oracle MySQL=5.0.75
Oracle MySQL=5.0.77
Oracle MySQL=5.0.81
Oracle MySQL=5.0.83
Oracle MySQL=5.0.85
Oracle MySQL=5.0.86
Oracle MySQL=5.1
Oracle MySQL=5.1.1
Oracle MySQL=5.1.2
Oracle MySQL=5.1.3
Oracle MySQL=5.1.4
Oracle MySQL=5.1.6
Oracle MySQL=5.1.7
Oracle MySQL=5.1.8
Oracle MySQL=5.1.9
Oracle MySQL=5.1.10
Oracle MySQL=5.1.11
Oracle MySQL=5.1.12
Oracle MySQL=5.1.13
Oracle MySQL=5.1.14
Oracle MySQL=5.1.15
Oracle MySQL=5.1.16
Oracle MySQL=5.1.17
Oracle MySQL=5.1.18
Oracle MySQL=5.1.19
Oracle MySQL=5.1.20
Oracle MySQL=5.1.21
Oracle MySQL=5.1.22
Oracle MySQL=5.1.23-a
Oracle MySQL=5.1.24
Oracle MySQL=5.1.25
Oracle MySQL=5.1.26
Oracle MySQL=5.1.27
Oracle MySQL=5.1.28
Oracle MySQL=5.1.29
Oracle MySQL=5.1.30
Oracle MySQL=5.1.31-sp1
Oracle MySQL=5.1.33
Oracle MySQL=5.1.34-sp1
Oracle MySQL=5.1.35
Oracle MySQL=5.1.36
Oracle MySQL=5.1.37-sp1
Oracle MySQL=5.1.38
Oracle MySQL=5.1.39
Oracle MySQL=5.1.40
Oracle MySQL=5.1.40-sp1

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-2009-4028?

    CVE-2009-4028 is classified as a high-severity vulnerability due to the potential for man-in-the-middle attacks.

  • How do I fix CVE-2009-4028?

    To fix CVE-2009-4028, upgrade to MySQL version 5.0.88 or later, or 5.1.41 or later.

  • What impact does CVE-2009-4028 have on MySQL servers?

    CVE-2009-4028 allows attackers to spoof arbitrary SSL-based MySQL servers.

  • Which versions of MySQL are affected by CVE-2009-4028?

    CVE-2009-4028 affects MySQL versions prior to 5.0.88 and 5.1.41.

  • Is there a workaround for CVE-2009-4028?

    A recommended workaround is to avoid using OpenSSL in affected MySQL versions until an upgrade can be performed.

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