CVE-2009-4028: Input Validation

Q: 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.

Q: 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.

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

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

Q: 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.

Q: 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.

Published Nov 30, 2009

Updated

The vioverifycallback 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.

Affected Software

104 affected components

MySQL mysql=5.0.5

MySQL mysql=5.0.10

MySQL mysql=5.0.54

MySQL mysql=5.0.0

MySQL mysql<=5.0.87

MySQL mysql=5.1.23

MySQL mysql=5.0.84

MySQL mysql=5.0.15

MySQL mysql=5.1.34

MySQL mysql=5.0.17

MySQL mysql=5.0.5.0.21

MySQL mysql=5.0.3

MySQL mysql=5.0.44

MySQL mysql=5.0.66

MySQL mysql=5.0.56

MySQL mysql=5.0.60

MySQL mysql=5.0.24

MySQL mysql=5.0.2

MySQL mysql=5.1.37

MySQL mysql=5.0.22.1.0.1

MySQL mysql=5.0.30

MySQL mysql=5.0.20

MySQL mysql=5.1.31

MySQL mysql=5.0.1

MySQL mysql=5.0.4

MySQL mysql=5.0.82

MySQL mysql=5.0.36

MySQL mysql=5.1.32

MySQL mysql=5.0.16

MySQL mysql=5.1.5

Oracle MySQL=5.1.39

Oracle MySQL=5.1.40-sp1

Oracle MySQL=5.1.40

Oracle MySQL=5.0.50

Oracle MySQL=5.0.51

Oracle MySQL=5.0.0-alpha

Oracle MySQL=5.0.3-beta

Oracle MySQL=5.0.6

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.52

Oracle MySQL=5.0.7

Oracle MySQL=5.0.8

Oracle MySQL=5.0.75

Oracle MySQL=5.0.77

Oracle MySQL=5.0.81

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.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.33

Oracle MySQL=5.1.35

Oracle MySQL=5.1.36

Oracle MySQL=5.1.38

Oracle MySQL=5.0.83

Oracle MySQL=5.0.85

Oracle MySQL=5.0.86

Oracle MySQL=5.1.23-a

Oracle MySQL=5.1.31-sp1

Oracle MySQL=5.1.34-sp1

Oracle MySQL=5.1.37-sp1

Event History

Nov 30, 2009

CVE Published

via MITRE·05:00 PM

Data Sourced

via MITRE·05:00 PM

Description

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?