dbcve.org
DolphinschedulerApplication · Apache

CVE-2022-45875

CRITICAL · 9.8 CVSS v3.1 Published 2023-01-04
Fix available
A fix is available. Upgrade to 3.0.2 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 validation of script alert plugin parameters in Apache DolphinScheduler to avoid remote command execution vulnerability. This issue affects Apache DolphinScheduler version 3.0.1 and prior versions; version 3.1.0 and prior versions. This attack can be performed only by authenticated users which can login to DS.

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

Apache DolphinScheduler's script alert plugin fails to properly validate input parameters, allowing authenticated users to inject and execute arbitrary commands on the host system. The vulnerability exists in how the alert plugin processes script-related configuration values.

MitigationUpgrade to Apache DolphinScheduler version 3.1.1 or later which contains proper parameter validation. Until patched, minimize the number of users with login access and monitor for suspicious alert configurations.

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.0.2= 3.1.0

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

CVSS:3.1/AV:N/AC:L/PR:N/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. Check DolphinScheduler version
    Access the DolphinScheduler UI and navigate to 'About' or use the API endpoint '/dolphinscheduler/version' to retrieve the installed version. Alternatively, check the 'application.properties' or 'install.conf' file in the installation directory.
    Affected if The installed version is less than 3.0.2, or exactly 3.1.0.
  2. Verify script alert plugin is in use
    Navigate to 'Alert Management' in the DolphinScheduler UI, or query the 't_ds_alert_plugin_instance' table in the DolphinScheduler database. Look for instances of the script alert plugin type.
    Affected if The script alert plugin is configured and active in the environment.
  3. Inspect script alert plugin configuration
    In Alert Management, examine the script alert instance configuration. Check the 'Alert Plugin Parameter' settings for script paths, script content, or command parameters that could be manipulated.
    Affected if The script alert plugin configuration contains user-controlled script paths or parameters that could be modified by authenticated users.
  4. Review alert instance definitions
    Query the database table 't_ds_alert_instance' or inspect the alert instances via API at '/alert-instance' to list all alert instances and their types.
    Affected if An alert instance of type 'script' exists and is associated with a plugin instance.

A user is affected if their DolphinScheduler version is less than 3.0.2 or exactly 3.1.0 AND the script alert plugin is configured and active in their environment.

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.0.2 or later
Fixed in 3.0.2
Interim mitigation

Upgrade to Apache DolphinScheduler version 3.1.1 or later which contains proper parameter validation. Until patched, minimize the number of users with login access and monitor for suspicious alert configurations.

Recommended fix High confidence

Apache DolphinScheduler 3.0.2 (for 3.0.x branch) or 3.1.1 (for 3.1.x branch)

  1. 1. Identify the currently installed Apache DolphinScheduler version by checking the UI or running 'dsctl --version' or inspecting the installation directory
  2. 2. If running version 3.0.1 or earlier, plan upgrade to version 3.0.2 or later
  3. 3. If running version 3.1.0, plan upgrade to version 3.1.1 or later
  4. 4. Before upgrading, back up the DolphinScheduler database and configuration files
  5. 5. Follow the official upgrade guide for your deployment method (kubernetes, docker, or standalone)
  6. 6. Stop all DolphinScheduler services before performing the upgrade
  7. 7. Run database migration scripts if required by the target version
  8. 8. Start the upgraded DolphinScheduler services and verify they are running
Caveat Review release notes for any configuration or API changes between your current version and the target version; some alert plugin configurations may need adjustment

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

Fix this in Dolphinscheduler Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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