CVE-2010-3840: Medium severity mysql vulnerability

Published Oct 7, 2010
·
Updated

A flaw in MySQL versions prior to 5.1.51 [1] was reported [2] that could allow an authenticated user to cause the MySQL server to crash when improper WKB data was passed to the PolyFromWKB() function.

There is an upstream patch [3] to correct the issue.

[1] http://dev.mysql.com/doc/refman/5.1/en/news-5-1-51.html [2] http://bugs.mysql.com/bug.php?id=51875 [3] http://lists.mysql.com/commits/117094

Other sources

The Gislinestring::initfromwkb function in sql/spatial.cc in MySQL 5.1 before 5.1.51 allows remote authenticated users to cause a denial of service (server crash) by calling the PolyFromWKB function with Well-Known Binary (WKB) data containing a crafted number of (1) line strings or (2) line points.

MITRE

Affected Software

59 affected components
MySQL mysql=5.1.23
MySQL mysql=5.1.34
MySQL mysql=5.1.37
MySQL mysql=5.1.31
MySQL mysql=5.1.32
MySQL mysql=5.1.5
Oracle MySQL=5.1.39
Oracle MySQL=5.1.40-sp1
Oracle MySQL=5.1.40
Oracle MySQL=5.1.41
Oracle MySQL=5.1.42
Oracle MySQL=5.1.43
Oracle MySQL=5.1.43-sp1
Oracle MySQL=5.1.44
Oracle MySQL=5.1.45
Oracle MySQL=5.1.46-sp1
Oracle MySQL=5.1.46
Oracle MySQL=5.1.47
Oracle MySQL=5.1.48
Oracle MySQL=5.1.49-sp1
Oracle MySQL=5.1.49
Oracle MySQL=5.1.50
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.1.23-a
Oracle MySQL=5.1.31-sp1
Oracle MySQL=5.1.34-sp1
Oracle MySQL=5.1.37-sp1

Event History

Oct 7, 2010
Data Sourced
12:01 AM
DescriptionSeverityAffected Software
Jan 14, 2011
CVE Published
via MITRE·06:00 PM
Data Sourced
via MITRE·06:00 PM
Description

Frequently Asked Questions

1

What is the severity of CVE-2010-3840?

CVE-2010-3840 is rated as a moderate severity vulnerability that can crash the MySQL server.

2

How do I fix CVE-2010-3840?

To fix CVE-2010-3840, upgrade MySQL to version 5.1.51 or later.

3

Which versions of MySQL are affected by CVE-2010-3840?

CVE-2010-3840 affects MySQL versions prior to 5.1.51.

4

What is the impact of CVE-2010-3840?

The impact of CVE-2010-3840 is that an authenticated user can cause the MySQL server to crash.

5

Is there an upstream patch available for CVE-2010-3840?

Yes, there is an upstream patch available to correct the CVE-2010-3840 vulnerability.

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