CVE-2020-5427: In Spring Cloud Data Flow, versions 2.6.x prior to 2.6.5, versions 2.5.x prior 2.5.4, an application is vulner

This month

HIGH 7.2UPGRADE

CVE-2020-5427 is a high-severity flaw (CVSS 7.2) affecting spring cloud data flow. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

In 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.

Why this priority

High severity

A fixed release or distro patch exists.

Risk facts

CVSS score	7.2 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	High
User interaction	None
EPSS exploit chance	1.1% (top 34%)
CISA exploited list	No
Weakness	CWE-89
Published	2021-01-27
Last modified	2026-06-17

Publisher (CNA): Pivotal Software, Inc. · Vendor: vmware

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2021-01-27 18:15 UTCPublished CVE record published
2026-06-17 03:21 UTCUpdated Record last modified

vmware spring cloud data flow UPGRADE

Affected: >= 2.5.0 and < 2.5.4 · >= 2.6.0 and < 2.6.5

Fixed in: 2.5.4, 2.6.5

Safe to downgrade to: a release before 2.5.0

1. Check installed version

apt-cache policy spring-cloud-data-flow || rpm -q spring-cloud-data-flow || spring-cloud-data-flow --version

2. UPGRADE to 2.5.4 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade spring-cloud-data-flow

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade spring-cloud-data-flow

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 2.5.0 (Debian / Ubuntu)

apt-cache madison spring-cloud-data-flow sudo apt install spring-cloud-data-flow=<VERSION_BEFORE_2.5.0> sudo apt-mark hold spring-cloud-data-flow

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list spring-cloud-data-flow sudo dnf downgrade spring-cloud-data-flow-<VERSION_BEFORE_2.5.0> sudo dnf versionlock add spring-cloud-data-flow

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2020-5427?

spring cloud data flow: upgrade to 2.5.4, 2.6.5. Exact commands for each OS are on this page.

Is CVE-2020-5427 being exploited?

CVE-2020-5427 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2020-5427 affect?

CVE-2020-5427 affects spring cloud data flow. Severity is high (CVSS 7.2). In 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.

How urgent is CVE-2020-5427?

Priority 42/100. High severity

Software pages

VMware vulnerabilities

Related CVEs

CVE-2024-37084 CRITICAL 9.8 UPGRADE In Spring Cloud Data Flow versions prior to 2.11.4, a malicious user who has access to the Skipper server api

References

← Back to latest CVEs