Spring Cloud Data FlowFramework / library · VMware
CVE-2020-5427
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 Spring Cloud Data Flow, versions 2.6.x prior to 2.6.5, versions 2.5.x prior 2.5.4, an application is vulnerable to SQL injection when requesting task execution.
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 confidenceSpring Cloud Data Flow versions 2.6.x prior to 2.6.5 and 2.5.x prior to 2.5.4 contain a SQL injection vulnerability in the task execution request handler. Attackers can craft malicious input in task execution requests to manipulate SQL queries, potentially exfiltrating or modifying database contents.
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
Spring Cloud Data FlowFramework / library
>= 2.5.0, < 2.5.4>= 2.6.0, < 2.6.5CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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 Spring Cloud Data Flow versionCheck the version of Spring Cloud Data Flow running in your environment. This is typically visible in the application startup logs, the about page in the UI, or via the /management/info endpoint if exposed.Affected if The installed version is 2.5.0 through 2.5.3, or 2.6.0 through 2.6.4 (anything >= 2.5.0 but < 2.5.4, or >= 2.6.0 but < 2.6.5).
-
Confirm task execution feature is in useDetermine if the task execution functionality is enabled and accessible. This includes any REST endpoints or UI options that allow submitting task execution requests, such as /tasks/executions or similar task launch endpoints.Affected if Task execution feature is enabled and users can submit task execution requests to the system.
-
Verify task execution endpoint is network accessibleCheck whether the task execution API endpoints are exposed to network traffic. Review your network configuration, firewall rules, and Spring Cloud Data Flow security settings to determine if these endpoints can be reached by potential attackers.Affected if The task execution request handler endpoint is reachable from the network without additional authentication or is accessible to untrusted users.
Your environment is affected if you are running Spring Cloud Data Flow version 2.5.0 to 2.5.3 or 2.6.0 to 2.6.4, and the task execution feature with its REST API is enabled and accessible to users who can submit malicious SQL payloads.
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.
From vendor data2.5.42.6.5
Upgrade Spring Cloud Data Flow to version 2.6.5, 2.5.4, or later. If immediate patching is not possible, implement strict input validation and web application firewall rules to mitigate SQL injection vectors in task execution endpoints.
Fix this in Spring Cloud Data Flow
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing12.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 $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-5427 — 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-5427 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