dbcve.org
DolphinschedulerApplication · Apache

CVE-2022-45462

CRITICAL · 9.8 CVSS v3.1 Published 2022-11-23
Fix available
A fix is available. Upgrade to 2.0.6 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
Alarm instance management has command injection when there is a specific command configured. It is only for logged-in users. We recommend you upgrade to version 2.0.6 or higher

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

Authenticated command injection vulnerability in the alarm instance management functionality. When a specific alarm command is configured, user-supplied input is improperly handled allowing injection of arbitrary OS commands. The attack requires valid credentials (logged-in user), lowering the attack surface but still critical due to the high impact of command injection.

MitigationUpgrade to version 2.0.6 or higher to receive the patched code that properly sanitizes input in the alarm command configuration.

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:< 2.0.6

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. Identify Apache DolphinScheduler version
    Check the installed DolphinScheduler version via UI login (typically shown in About section) or inspect the release manifest file in the installation directory, then compare against the affected range (versions below 2.0.6)
    Affected if Installed version is Apache DolphinScheduler below 2.0.6
  2. Verify alarm instance management is accessible
    Log into DolphinScheduler with valid credentials and navigate to the Alarm instance management section (usually under the Alarms or System Settings menu) to confirm the feature is available and configured
    Affected if Alarm instance management interface is accessible to authenticated users
  3. Check for configured alarm command instances
    Inspect the alarm instance configuration panel - look for alarm instances that use command-based alert types (such as Script, HTTP, or custom command implementations) where user-defined parameters are accepted
    Affected if Any alarm instances are configured using command-based alert plugins that accept user input
  4. Identify if alarm command parameters accept user input
    Examine the configured alarm instance details - specifically check if any alarm command configuration fields allow direct parameter input that could be interpreted as shell commands (such as script parameters, command arguments, or callback URLs)
    Affected if Alarm command configurations accept direct user-supplied input in fields used for command execution

User is affected if running Apache DolphinScheduler version below 2.0.6 AND the alarm instance management feature is accessible with command-based alarm configurations that accept user input.

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 2.0.6 or later
Fixed in 2.0.6
Interim mitigation

Upgrade to version 2.0.6 or higher to receive the patched code that properly sanitizes input in the alarm command configuration.

Recommended fix High confidence

2.0.6 or higher

  1. Backup your current DolphinScheduler configuration and database
  2. Stop the DolphinScheduler services
  3. Download Apache DolphinScheduler version 2.0.6 or the latest stable release from the official Apache repository
  4. Upgrade the database schema using the provided migration scripts (if any) in the release package
  5. Replace the existing DolphinScheduler binaries with the new version
  6. Update configuration files as needed, ensuring alarm instance configurations are reviewed for safety
  7. Start the DolphinScheduler services
  8. Verify the upgrade by logging in and checking the alarm instance management functionality

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
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
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,968.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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