Menu

Star on GitHub · 3.2k

CVE-2010-1850

6.0 · MEDIUM

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.

Published Jun 8, 2010mysqlCWE-119EPSS 21.79%

Overview

CVE-2010-1850 is a medium-severity vulnerability affecting mysql mysql. It was published on June 8, 2010 and has a CVSS 2.0 base score of 6.0 (MEDIUM).

This vulnerability has a CVSS 2.0 base score of 6.0, rated MEDIUM. It can be exploited remotely over the network. Some level of privileges is required for exploitation.

Technical description

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.

Remediation

Check the references section for vendor advisories and patches from mysql. Update mysql to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Affected products

VendorProductVersionsStatus

Frequently asked questions

What is CVE-2010-1850?

CVE-2010-1850 is a medium-severity vulnerability affecting mysql mysql. It was published on June 8, 2010 and has a CVSS 2.0 base score of 6.0 (MEDIUM).

How severe is CVE-2010-1850?

This vulnerability has a CVSS 2.0 base score of 6.0, rated MEDIUM. It can be exploited remotely over the network. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2010-1850?

Check the references section for vendor advisories and patches from mysql. Update mysql to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2010-1850?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2010-1850 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related MEDIUM CVEs from 2010

View all