# CVE-2023-51770: Apache DolphinScheduler: Arbitrary File Read Vulnerability

> Attackers can read arbitrary files from the server, exposing sensitive data in Apache DolphinScheduler deployments.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 20 Feb 2024
- **Updated:** 27 Mar 2025
- **Also known as:** GHSA-ff2w-wm48-jhqj

## What is CVE-2023-51770?

CVE-2023-51770 is a high-severity path traversal vulnerability in Apache DolphinScheduler, published on 20 Feb 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Arbitrary File Read Vulnerability in Apache Dolphinscheduler.

This issue affects Apache DolphinScheduler: before 3.2.1. 

We recommend users to upgrade Apache DolphinScheduler to version 3.2.1, which fixes the issue.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2023-51770?

2 open source packages ship an affected version, including org.apache.dolphinscheduler:dolphinscheduler. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.apache.dolphinscheduler:dolphinscheduler` | Maven | All versions | 3.2.1 |
| `org.apache.dolphinscheduler:dolphinscheduler` | Maven | All versions | 3.2.1 |

Products: Apache Dolphinscheduler.

## How do I fix CVE-2023-51770?

Upgrade org.apache.dolphinscheduler:dolphinscheduler to 3.2.1 or later.

## Is CVE-2023-51770 being exploited?

There is no known exploitation of CVE-2023-51770 in the wild and no public exploit code.

Public exploit code:

- https://github.com/shoucheng3/apache__dolphinscheduler_CVE-2023-51770_3-2-00 (github_poc): https://github.com/shoucheng3/apache__dolphinscheduler_CVE-2023-51770_3-2-00
- https://github.com/shoucheng3/apache__dolphinscheduler_CVE-2023-51770_3_2_1_fixed (github_poc): https://github.com/shoucheng3/apache__dolphinscheduler_CVE-2023-51770_3_2_1_fixed

## Other vulnerabilities in Apache DolphinScheduler

- [CVE-2024-43166](https://insights.sbomify.com/CVE-2024-43166/): Apache DolphinScheduler Incorrect Default Permissions Vulnerability (critical 9.8)
- [CVE-2024-43202](https://insights.sbomify.com/CVE-2024-43202/): Apache DolphinScheduler: Remote Code Execution Vulnerability (critical 9.8)
- [CVE-2023-49109](https://insights.sbomify.com/CVE-2023-49109/): Remote Code Execution in Apache Dolphinscheduler (critical 9.8)
- [CVE-2022-45875](https://insights.sbomify.com/CVE-2022-45875/): Apache DolphinScheduler: Remote command execution Vulnerability in script alert plugin (critical 9.8)
- [CVE-2022-45462](https://insights.sbomify.com/CVE-2022-45462/): Apache DolphinScheduler prior to 2.0.5 have command execution vulnerability (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-51770 and fix it if it is affected.

What it is: CVE-2023-51770 is a high-severity path traversal vulnerability in Apache DolphinScheduler, published on 20 Feb 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-51770 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.apache.dolphinscheduler:dolphinscheduler (Maven): affected all versions; fixed in 3.2.1
- org.apache.dolphinscheduler:dolphinscheduler (Maven): affected all versions; fixed in 3.2.1

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-2023-51770/ (Markdown: https://insights.sbomify.com/CVE-2023-51770/index.md)
```

## Sources

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

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