dbcve.org
DolphinschedulerApplication · Apache

CVE-2024-43115

HIGH · 8.8 CVSS v3.1 Published 2025-09-03
Fix available
A fix is available. Upgrade to 3.2.2 or later.
See remediation →
94/100
Remediation priority · Urgent
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
Improper Input Validation vulnerability in Apache DolphinScheduler. An authenticated user can execute any shell script server by alert script. This issue affects Apache DolphinScheduler: before 3.2.2. Users are recommended to upgrade to version 3.3.1, 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 · high confidence

This is an improper input validation vulnerability in Apache DolphinScheduler's alert script functionality. An authenticated user can execute arbitrary shell scripts on the server due to insufficient input validation when processing alert scripts, leading to command injection and potential complete system compromise.

MitigationUpgrade Apache DolphinScheduler to version 3.3.1 or later, which includes proper input validation fixes for the alert script execution path.

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

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

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 DolphinScheduler installation and version
    Check the version file or startup scripts. Common locations: look for version info in the installation directory, or run: grep -r 'version' <install_dir>/conf/application.properties 2>/dev/null || cat <install_dir>/ pom.xml | grep '<version>'
    Affected if The installed version is lower than 3.2.2 (e.g., 3.2.1, 3.2.0, 3.1.x, 3.0.x, etc.)
  2. Verify alert plugin is enabled
    Check the alert plugin configuration directory (typically <install_dir>/alert-plugin/ or similar) and the alert configuration file (alert.properties or similar). List contents: ls -la <install_dir>/alert-plugin/ && cat <install_dir>/conf/alert.properties 2>/dev/null
    Affected if The alert plugin directory exists and contains alert plugin jars, meaning the alert functionality is active
  3. Check alert script configuration
    Examine the alert configuration for script-based alerts. Look for entries like 'script' or 'shell' in the alert configuration files: grep -rE 'script|shell|command' <install_dir>/conf/ 2>/dev/null | grep -v '*.class'
    Affected if Script-based alert configurations exist, particularly custom shell scripts defined in the alert settings
  4. Review alert script file permissions and ownership
    List alert script files and their permissions: find <install_dir> -name '*alert*' -type f 2>/dev/null | head -20
    Affected if Custom or external alert scripts are present in the DolphinScheduler installation directory

A user is affected if Apache DolphinScheduler version is below 3.2.2 AND the alert plugin functionality is enabled with script-based alerts configured.

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.3.1 or later, which includes proper input validation fixes for the alert script execution path.

Recommended fix High confidence

3.3.1

  1. Download Apache DolphinScheduler version 3.3.1 from the official Apache release repository
  2. Review the upgrade documentation specific to your deployment method (standalone, cluster, or Docker)
  3. Backup your current DolphinScheduler database and configuration files
  4. Stop the running DolphinScheduler services
  5. Install or extract the new version 3.3.1
  6. Update configuration files to match your existing setup if needed
  7. Run any provided database migration scripts for version 3.3.1
  8. Start the DolphinScheduler services and verify they run correctly

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

Fix this in Dolphinscheduler Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,780
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-43115 — 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-43115 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