MySQLDatabase / datastore
CVE-2010-1850
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedBuffer 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceBuffer overflow in MySQL versions 5.0 through 5.0.91 and 5.1 before 5.1.47 in the COM_FIELD_LIST protocol command. When processing a table name field, the server fails to properly validate length boundaries, allowing an authenticated remote attacker to overflow a buffer and execute arbitrary code on the MySQL server.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
MySQLDatabase / datastore
= 5.0.0= 5.0.1= 5.0.2= 5.0.3= 5.0.4= 5.0.5= 5.0.5.0.21= 5.0.10= 5.0.15= 5.0.16= 5.0.17= 5.0.20
MySQLDatabase / datastore
= 5.0.0= 5.0.3= 5.0.6= 5.0.7= 5.0.8= 5.0.9= 5.0.11= 5.0.12= 5.0.13= 5.0.14= 5.0.18= 5.0.19CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- M
- Authentication
- Single
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:S/C:P/I:P/A:P
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed MySQL versionRun 'mysql --version' or 'mysqld --version' or query 'SELECT VERSION();'Affected if Version is 5.0.x (any version up to and including 5.0.91) OR version 5.1.x before 5.1.47
-
Check if MySQL service is listening on networkCheck if port 3306 is open and bound to a network interface using 'netstat -an | grep 3306' or 'ss -tlnp | grep 3306'Affected if MySQL is listening on a non-loopback interface (0.0.0.0 or specific IP rather than 127.0.0.1)
-
Verify remote authentication is permittedReview MySQL user table for any user entries with host allowing remote connections (non-localhost hosts, wildcards %, or specific IP addresses) using 'SELECT user, host FROM mysql.user;'Affected if There exist user accounts with remote access privileges (host not equal to 'localhost' or '127.0.0.1')
If the MySQL version falls within 5.0.0 through 5.0.91 or 5.1.0 through 5.1.46 AND the service is network-accessible with remote user accounts, the environment is affected by this vulnerability.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade MySQL to version 5.0.92+/5.1.47+ or later. If immediate patching is not feasible, restrict network access to the MySQL port (3306) to only trusted, authenticated users and consider implementing additional network-level filtering.
Fix this in MySQL
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-1850 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2010-1850 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data