MySQLDatabase / datastore
CVE-2010-1848
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 · uneditedDirectory traversal vulnerability in MySQL 5.0 through 5.0.91 and 5.1 before 5.1.47 allows remote authenticated users to bypass intended table grants to read field definitions of arbitrary tables, and on 5.1 to read or delete content of arbitrary tables, via a .. (dot dot) in a 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 confidenceDirectory traversal vulnerability in MySQL 5.0 through 5.0.91 and 5.1 before 5.1.47 allows authenticated users to bypass table-level grants by using '..' (dot dot) sequences in table names, enabling unauthorized access to read field definitions of arbitrary tables, and on 5.1 versions to read or delete content from tables outside their granted permissions.
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
- Single
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/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.
-
Determine installed MySQL versionRun 'mysql --version' or log into MySQL and execute 'SELECT VERSION();'Affected if Version is 5.0.x at or below 5.0.91, or 5.1.x below 5.1.47
-
Identify users with table-level privilegesLog into MySQL and run 'SELECT User, Host, Table_name, Priv FROM mysql.tables_priv;' to list users who have table-level grantsAffected if Any non-root users have SELECT, INSERT, UPDATE, DELETE, or other table-level privileges (vulnerability allows bypassing these)
-
Review query logs for traversal patternsExamine MySQL general query log, slow query log, or binary log for queries containing '..' in table or database names (e.g., 'SELECT * FROM ..tablename' or 'SELECT * FROM database1..table2')Affected if Any queries contain '..' sequences in table or database identifiers, indicating exploitation attempts
-
Check for unauthorized table accessQuery the MySQL information_schema to compare granted privileges against actual table access: compare 'SELECT DISTINCT TABLE_SCHEMA FROM information_schema.TABLES' against granted databases in 'mysql.db' or 'mysql.tables_priv'Affected if Users can access tables in databases where they have no explicit grants, suggesting the vulnerability may be exploited
You are affected if your MySQL version is 5.0.x at or below 5.0.91 or 5.1.x below 5.1.47 AND you have users with table-level privileges that could be bypassed using '..' traversal.
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. If immediate patching is not feasible, restrict database user privileges and monitor for anomalous queries containing '..' in table identifiers.
Fix this in MySQL
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing3.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,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-1848 — 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-1848 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