CVE-2025-30224
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 · uneditedMyDumper is a MySQL Logical Backup Tool. The MySQL C client library (libmysqlclient) allows authenticated remote actors to read arbitrary files from client systems via a crafted server response to LOAD LOCAL INFILE query, leading to sensitive information disclosure when clients connect to untrusted MySQL servers without explicitly disabling the local infile capability. Mydumper has the local infile option enabled by default and does not have an option to disable it. This can lead to an unexpected arbitrary file read if the Mydumper tool connects to an untrusted server. This vulnerability is fixed in 0.18.2-8.
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 confidenceMyDumper uses the MySQL C client library which allows authenticated remote MySQL servers to force clients to read arbitrary local files via the LOAD LOCAL INFILE protocol feature. MyDumper enables this capability by default and provides no option to disable it, enabling a malicious server to read sensitive files from the Mydumper client system.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- Privileges
- None
- Authentication
- X
- User interaction
- A
- Scope
- X
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
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 MyDumper versionRun 'mydumper --version' or check the installed package (e.g., dpkg -l mydumper, rpm -qa mydumper)Affected if Version is below 0.18.2-8 (the version that disables local infile by default)
-
Identify MySQL server connectionsReview MyDumper connection strings or configuration files to list all target MySQL serversAffected if Any connection targets an untrusted or potentially malicious MySQL server
-
Assess file access exposureDetermine if the MyDumper client runs with elevated privileges or has access to sensitive local files readable by its process userAffected if The mydumper process user can read sensitive files that a malicious server could request via LOAD LOCAL INFILE
You are affected if running MyDumper version below 0.18.2-8 and connecting to untrusted MySQL servers, as the client will blindly fulfill LOAD LOCAL INFILE requests from the server.
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.
dbcve · scopedUpgrade MyDumper to version 0.18.2-8 or later which disables local infile by default. Until upgraded, only connect to trusted MySQL servers.
0.18.2-8
- Check the currently installed MyDumper version using: mydumper --version
- Upgrade MyDumper to version 0.18.2-8 or later. On Debian-based systems, run: apt-get update && apt-get install mydumper
- Alternatively, if building from source, clone the repository and checkout version 0.18.2-8 or later: git clone https://github.com/mydumper/mydumper.git && cd mydumper && git checkout 0.18.2-8 && cmake . && make
- Verify the upgrade was successful by running: mydumper --version
- Confirm the local infile vulnerability is patched in the new version by reviewing the release notes for 0.18.2-8
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.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,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-30224 — 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-2025-30224 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