dbcve.org
DolphinschedulerApplication · Apache

CVE-2024-30188

HIGH · 8.1 CVSS v3.1 Published 2024-08-12
Fix available
A fix is available. Upgrade to 3.2.2 or later.
See remediation →
87/100
Remediation priority · High
Remotely reachable Zero-click

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 · unedited
File read and write vulnerability in Apache DolphinScheduler ,  authenticated users can illegally access additional resource files. This issue affects Apache DolphinScheduler: from 3.1.0 before 3.2.2. Users are recommended to upgrade to version 3.2.2, which fixes the issue.

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 · moderate confidence

Apache DolphinScheduler before 3.2.2 contains a file read/write vulnerability where authenticated users can access resource files outside their authorized scope, likely due to insufficient path validation or access controls in the resource file handling functionality.

MitigationUpgrade Apache DolphinScheduler to version 3.2.2 or later.

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
DolphinschedulerApplication
Affected:>= 3.1.0, < 3.2.2

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed DolphinScheduler version
    Check the version by accessing the DolphinScheduler web UI (typically at /dolphinscheduler/about or /system/about), or inspect the configuration files (application.yml, pom.xml, or startup logs) in the installation directory
    Affected if The version is 3.1.0 through 3.2.1 (anything >= 3.1.0 but < 3.2.2)
  2. Determine if resource file handling is in use
    Check if the Resources feature is enabled or being used. This includes checking for any uploaded files, file templates, or resource management features accessed through the UI or API
    Affected if The Resources functionality is accessible or being used by authenticated users in the deployment
  3. Verify access control configuration for resources
    Inspect the DolphinScheduler configuration files (especially application.yml or security-related config) for any custom path validation or access control settings related to file resources
    Affected if No custom path validation or restrictive access controls are configured for resource file operations
  4. Check API endpoints for resource file operations
    Review API logs or documentation for resource-related endpoints (such as /resources/* or /file/*) to confirm they accept user-supplied file paths
    Affected if The API accepts user-provided paths without additional validation beyond authentication

You are affected if your installed version is 3.1.0 through 3.2.1 and the resource file handling functionality is enabled or accessible to authenticated users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 3.2.2 or later
Fixed in 3.2.2
Interim mitigation

Upgrade Apache DolphinScheduler to version 3.2.2 or later.

Recommended fix High confidence

Apache DolphinScheduler 3.2.2

  1. 1. Back up your existing DolphinScheduler database and configuration files (especially the conf directory and any custom settings).
  2. 2. Stop all DolphinScheduler services (api-server, master-server, worker-server, alert-server).
  3. 3. Download Apache DolphinScheduler 3.2.2 from the official Apache repository (https://dolphinscheduler.apache.org/download/).
  4. 4. Extract the new installation package to your target directory.
  5. 5. Copy your backed-up configuration files to the new installation, updating any deprecated settings as needed for version 3.2.2.
  6. 6. Run the database upgrade scripts if upgrading from a previous version (check the sql/upgrade directory).
  7. 7. Start the DolphinScheduler services in the correct order: Zookeeper (if external), then master-server, then worker-server, then api-server, then alert-server.
  8. 8. Verify all services are running correctly and the UI is accessible.
Caveat Review release notes for any configuration or API changes between your current version and 3.2.2; test thoroughly in a staging environment before production deployment.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Dolphinscheduler Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-30188 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-30188 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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