MySQLDatabase / datastore
CVE-2010-1849
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 · uneditedThe my_net_skip_rest function in sql/net_serv.cc in MySQL 5.0 through 5.0.91 and 5.1 before 5.1.47 allows remote attackers to cause a denial of service (CPU and bandwidth consumption) by sending a large number of packets that exceed the maximum length.
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 confidenceThe my_net_skip_rest function in MySQL's sql/net_serv.cc fails to properly handle oversized network packets. Attackers can send a large volume of packets exceeding the maximum allowed length, causing excessive CPU consumption and bandwidth usage due to the function's inefficient processing of these malformed packets.
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
- Low
- Authentication
- None
- Confidentiality
- None
- Integrity
- None
- Availability
- Partial
AV:N/AC:L/Au:N/C:N/I:N/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 'SELECT VERSION();' query to get the exact version numberAffected if Version is 5.0.x and falls within the listed affected versions (5.0.0 through 5.0.20 for MySQL, 5.0.0 through 5.0.19 for Oracle MySQL)
-
Verify if network listening is enabledCheck MySQL configuration file (my.cnf/my.ini) for 'skip-networking' option or run 'SHOW VARIABLES LIKE 'skip_networking';'Affected if skip-networking is disabled or not set, meaning the server accepts TCP connections
-
Check MySQL bind address configurationRun 'SHOW VARIABLES LIKE 'bind_address';' or inspect my.cnf for 'bind-address' settingAffected if bind-address is set to '0.0.0.0' or the server is reachable on any IP address, exposing it to remote attacks
You are affected if running a vulnerable 5.0.x version AND the MySQL server has network listening enabled with exposed network access.
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 or later, or 5.1.47 or later. Alternatively, restrict network access to the MySQL server to prevent unauthenticated remote attacks.
Fix this in MySQL
Scoped from the published advisory
- Consultation3.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,896.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-1849 — 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-1849 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