CWE
119
Advisory Published
Updated

CVE-2010-1850: Buffer Overflow

First published: Mon Jun 07 2010(Updated: )

Buffer overflow in MySQL 5.0 through 5.0.91 and 5.1 before 5.1.47 allows remote authenticated users to execute arbitrary code via a COM_FIELD_LIST command with a long table name.

Credit: cve@mitre.org

Affected SoftwareAffected VersionHow to fix
MySQL (MySQL-common)=5.0.5
MySQL (MySQL-common)=5.0.10
MySQL (MySQL-common)=5.0.0
MySQL (MySQL-common)=5.0.84
MySQL (MySQL-common)=5.0.15
MySQL (MySQL-common)=5.0.17
MySQL (MySQL-common)=5.0.5.0.21
MySQL (MySQL-common)=5.0.3
MySQL (MySQL-common)=5.0.24
MySQL (MySQL-common)=5.0.87
MySQL (MySQL-common)=5.0.2
MySQL (MySQL-common)=5.0.20
MySQL (MySQL-common)=5.0.1
MySQL (MySQL-common)=5.0.4
MySQL (MySQL-common)=5.0.82
MySQL (MySQL-common)=5.0.16
MySQL (MySQL-common)=5.0.45b
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.27
Oracle MySQL=5.0.33
Oracle MySQL=5.0.37
Oracle MySQL=5.0.41
Oracle MySQL=5.0.45
Oracle MySQL=5.0.7
Oracle MySQL=5.0.8
Oracle MySQL=5.0.67
Oracle MySQL=5.0.75
Oracle MySQL=5.0.77
Oracle MySQL=5.0.81
Oracle MySQL=5.0.9
Oracle MySQL=5.0.83
Oracle MySQL=5.0.85
Oracle MySQL=5.0.86
Oracle MySQL=5.0.88
Oracle MySQL=5.0.89
Oracle MySQL=5.0.90
Oracle MySQL=5.0.91
MySQL (MySQL-common)=5.1.23
MySQL (MySQL-common)=5.1.34
MySQL (MySQL-common)=5.1.37
MySQL (MySQL-common)=5.1.31
MySQL (MySQL-common)=5.1.32
MySQL (MySQL-common)=5.1.5
Oracle MySQL=5.1.39
Oracle MySQL=5.1.40
Oracle MySQL=5.1.41
Oracle MySQL=5.1.42
Oracle MySQL=5.1.43
Oracle MySQL=5.1.44
Oracle MySQL=5.1.45
Oracle MySQL=5.1.46
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.30
Oracle MySQL=5.1.33
Oracle MySQL=5.1.35
Oracle MySQL=5.1.36
Oracle MySQL=5.1.38

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-2010-1850?

    CVE-2010-1850 is considered critical due to its potential to allow remote authenticated users to execute arbitrary code.

  • How do I fix CVE-2010-1850?

    To fix CVE-2010-1850, upgrade MySQL to version 5.1.47 or later.

  • What versions of MySQL are affected by CVE-2010-1850?

    CVE-2010-1850 affects MySQL versions 5.0.0 through 5.0.91 and 5.1 before 5.1.47.

  • Can CVE-2010-1850 be exploited remotely?

    Yes, CVE-2010-1850 can be exploited remotely by authenticated users using a specially crafted COM_FIELD_LIST command.

  • What types of attacks can result from CVE-2010-1850?

    CVE-2010-1850 may lead to arbitrary code execution, allowing attackers to gain unauthorized access to the system.

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