# CVE-2025-30224: MyDumper arbitrary file read issue

> An attacker controlling a MySQL server can read arbitrary files from the client system when MyDumper connects, due to enabled local infile capability.

- **Severity:** Medium 5.1 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 1 Apr 2025
- **Updated:** 29 May 2025
- **Also known as:** DEBIAN-CVE-2025-30224, DLA-4190-1, GHSA-r8qc-xp3g-c458, UBUNTU-CVE-2025-30224

## What is CVE-2025-30224?

CVE-2025-30224 is a medium-severity vulnerability in mydumper, published on 1 Apr 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

MyDumper 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.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2025-30224?


## How do I fix CVE-2025-30224?

Upgrade to a fixed version.

## Is CVE-2025-30224 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-30224 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-30224 and fix it if it is affected.

What it is: CVE-2025-30224 is a medium-severity vulnerability in mydumper, published on 1 Apr 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-30224 exists.

Affected product: mydumper. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-30224/ (Markdown: https://insights.sbomify.com/CVE-2025-30224/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-30224
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-30224
- OSV: https://osv.dev/vulnerability/CVE-2025-30224

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-30224/
Summaries are generated and may contain mistakes; the official description above is the record.