# CVE-2023-25601: Apache DolphinScheduler 3.0.0 to 3.1.1 python gateway has improper authentication > Attackers can bypass authentication in the Python gateway to execute arbitrary code or escalate privileges in Apache DolphinScheduler. - **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 20 Apr 2023 - **Updated:** 13 Feb 2025 - **Also known as:** GHSA-3jxw-cv35-2mmv ## What is CVE-2023-25601? CVE-2023-25601 is a medium-severity authentication bypass vulnerability in Apache DolphinScheduler, published on 20 Apr 2023. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description On version 3.0.0 through 3.1.1, Apache DolphinScheduler's python gateway suffered from improper authentication: an attacker could use a socket bytes attack without authentication. This issue has been fixed from version 3.1.2 onwards. For users who use version 3.0.0 to 3.1.1, you can turn off the python-gateway function by changing the value `python-gateway.enabled=false` in configuration file `application.yaml`. If you are using the python gateway, please upgrade to version 3.1.2 or above. Weakness: CWE-287 (Improper Authentication) ## Which versions are affected by CVE-2023-25601? 2 open source packages ship an affected version, including org.apache.dolphinscheduler:dolphinscheduler-api. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.apache.dolphinscheduler:dolphinscheduler-api` | Maven | From 3.0.0 | 3.1.2 | | `org.apache.dolphinscheduler:dolphinscheduler-api` | Maven | From 3.0.0 | 3.1.2 | Products: Apache Dolphinscheduler. ## How do I fix CVE-2023-25601? Upgrade org.apache.dolphinscheduler:dolphinscheduler-api to 3.1.2 or later. ## Is CVE-2023-25601 being exploited? There is no known exploitation of CVE-2023-25601 in the wild and no public exploit code. ## 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-25601 and fix it if it is affected. What it is: CVE-2023-25601 is a medium-severity authentication bypass vulnerability in Apache DolphinScheduler, published on 20 Apr 2023. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2023-25601 in the wild and no public exploit code. Affected packages and fixed versions: - org.apache.dolphinscheduler:dolphinscheduler-api (Maven): affected from 3.0.0; fixed in 3.1.2 - org.apache.dolphinscheduler:dolphinscheduler-api (Maven): affected from 3.0.0; fixed in 3.1.2 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-25601/ (Markdown: https://insights.sbomify.com/CVE-2023-25601/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2023-25601 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-25601 - OSV: https://osv.dev/vulnerability/CVE-2023-25601 --- From sbomify Insights: https://insights.sbomify.com/CVE-2023-25601/ Summaries are generated and may contain mistakes; the official description above is the record.