dbcve.org
DolphinschedulerApplication · Apache

CVE-2021-27644

HIGH · 8.8 CVSS v3.1 Published 2021-11-01
Fix available
A fix is available. Upgrade to 1.3.6 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
In Apache DolphinScheduler before 1.3.6 versions, authorized users can use SQL injection in the data source center. (Only applicable to MySQL data source with internal login account password)

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

SQL injection vulnerability in Apache DolphinScheduler's data source center component affects versions before 1.3.6. Authenticated users with internal login credentials can exploit this vulnerability specifically when using MySQL data sources. The vulnerability allows attackers to inject malicious SQL queries through the data source configuration interface.

MitigationUpgrade Apache DolphinScheduler to version 1.3.6 or later to remediate this SQL injection vulnerability. Until then, limit access to the data source center to only trusted personnel and monitor for suspicious SQL patterns in MySQL datasource 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:< 1.3.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
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. Determine Apache DolphinScheduler version
    Check the installed DolphinScheduler version by reviewing the release documentation, pom.xml file, or the About/Version page in the DolphinScheduler web UI. Look for a version identifier in the application startup logs or configuration files.
    Affected if The installed version is anything less than 1.3.6 (e.g., 1.3.5, 1.3.4, 1.3.0, or any 1.x version before 1.3.6).
  2. Verify data source center access
    Log into the DolphinScheduler web interface and navigate to the Data Source Center (usually found under the Resources or Datasources menu). Confirm whether you have permission to create, edit, or view data source configurations.
    Affected if The data source center is accessible to your user account and you can configure MySQL data sources.
  3. Identify configured MySQL data sources
    In the Data Source Center, list all configured data sources. Filter or search for data sources where the type is set to MySQL. Note the connection parameters such as host, port, database name, and username.
    Affected if Any MySQL data source is configured in DolphinScheduler, as the SQL injection occurs through the MySQL datasource configuration interface.
  4. Inspect data source configuration parameters
    Review the MySQL data source configuration fields (particularly connection strings, database names, or custom JDBC parameters) for any unusual or unexpected SQL syntax, encoded characters, or injection payloads that were not explicitly configured by your team.
    Affected if Any MySQL data source configuration contains unexpected SQL fragments, OR statements, or suspicious characters that were not intentionally added by an administrator.

You are affected if your DolphinScheduler version is below 1.3.6 and you have MySQL data sources configured in the data source center 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 1.3.6 or later
Fixed in 1.3.6
Interim mitigation

Upgrade Apache DolphinScheduler to version 1.3.6 or later to remediate this SQL injection vulnerability. Until then, limit access to the data source center to only trusted personnel and monitor for suspicious SQL patterns in MySQL datasource configurations.

Recommended fix High confidence

1.3.6

  1. Back up your current DolphinScheduler installation and database
  2. Stop all DolphinScheduler services
  3. Upgrade to version 1.3.6 or the latest stable release
  4. Start the DolphinScheduler services
  5. Verify the upgrade by logging in and testing the data source center functionality with MySQL connections
  6. Confirm that the SQL injection vulnerability is no longer present
Caveat Review the 1.3.6 release notes for any configuration or API changes that may affect your 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-2021-27644 — 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-2021-27644 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