DolphinschedulerApplication · Apache
CVE-2020-11974
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 · uneditedIn DolphinScheduler 1.2.0 and 1.2.1, with mysql connectorj a remote code execution vulnerability exists when choosing mysql as database.
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 confidenceDolphinScheduler versions 1.2.0 and 1.2.1 contain a critical remote code execution vulnerability when MySQL is used as the database backend with mysql-connector-j. The vulnerability is exploitable through the database connection configuration, likely due to insecure handling of database parameters in the mysql connector library.
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
= 1.2.0= 1.2.1CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed DolphinScheduler versionCheck the application version file, startup logs, or admin UI about page. Common locations include version files in the installation directory or the banner displayed at startup.Affected if Version is 1.2.0 or 1.2.1 exactly
-
Confirm MySQL is the database backendReview the database configuration file (typically database.properties or similar) in the conf directory. Look for jdbc:mysql:// or mariadb connection strings in the datasource configuration.Affected if Database connection URL uses MySQL (jdbc:mysql://) or MariaDB
-
Verify mysql-connector-j library is presentLocate the mysql-connector-java.jar or mysql-connector-j.jar file in the lib or libs directory of the DolphinScheduler installation. Check the filename and examine jar manifest if accessible.Affected if mysql-connector-java or mysql-connector-j library files exist in the application lib directory
If DolphinScheduler version is 1.2.0 or 1.2.1 AND MySQL is configured as the database backend with the mysql-connector-j library present, the environment is affected by this CVE.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpgrade DolphinScheduler to version 1.3.0 or later which contains the patched mysql-connector-j library, or apply vendor-supplied patches for the affected versions.
1.3.0 or later
- 1. Back up your current DolphinScheduler configuration and database
- 2. Stop the DolphinScheduler services
- 3. Upgrade DolphinScheduler from version 1.2.0 or 1.2.1 to version 1.3.0 or later
- 4. Verify the mysql-connector-java library is updated to a version that addresses the deserialization vulnerability
- 5. Test the upgrade in a non-production environment before deploying to production
- 6. Start the upgraded DolphinScheduler services
- 7. Verify MySQL database connectivity and all workflows function 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
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
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 locallyCheck whether your project pulls in CVE-2020-11974 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-11974 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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