Skip to content
Fencer Intel
medium 4.7

CVE-2020-1960 json

Command injection in Apache Flink

published 6y ago modified 2mo ago also BIT-flink-2020-1960 , EUVD-2021-0970 , GHSA-6g88-99wj-8mgg

cvss
4.7
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.9%
EPSS 0.9% chance of exploitation in 30 days, percentile 58%
public exploits
0
none known

Summary

A vulnerability in Apache Flink (1.1.0 to 1.1.5, 1.2.0 to 1.2.1, 1.3.0 to 1.3.3, 1.4.0 to 1.4.2, 1.5.0 to 1.5.6, 1.6.0 to 1.6.4, 1.7.0 to 1.7.2, 1.8.0 to 1.8.3, 1.9.0 to 1.9.2, 1.10.0) where, when running a process with an enabled JMXReporter, with a port configured via metrics.reporter.reporter_name>.port, an attacker with local access to the machine and JMX port can execute a man-in-the-middle attack using a specially crafted request to rebind the JMXRMI registry to one under the attacker's control. This compromises any connection established to the process via JMX, allowing extraction of credentials and any other transferred data.

Patch / fix

  • maven org.apache.flink:flink-core 1.9.3, 1.10.1
  • bitnami flink 1.1.6, 1.2.2, 1.3.4, 1.4.3, 1.5.7, 1.6.5, 1.7.3, 1.8.4, 1.9.3, 1.10.1

Is CVE-2020-1960 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2020-1960 updated cvss 6.5

apache-flink: JMX information disclosure vulnerability

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.86% chance of exploitation in the next 30 days, higher than 58% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
GitHub 3.1 4.7 CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N
NVD 3.1 4.7 CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N
NVD 2.0 1.9 AV:L/AC:M/Au:N/C:P/I:N/A:N
OSV 3.1 4.7 CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
maven org.apache.flink:flink-core
<1.9.3
>=1.10.0, <1.10.1
1.9.3
1.10.1
bitnami flink
>=1.1.0, <1.1.6
>=1.2.0, <1.2.2
>=1.3.0, <1.3.4
>=1.4.0, <1.4.3
>=1.5.0, <1.5.7
>=1.6.0, <1.6.5
>=1.7.0, <1.7.3
>=1.8.0, <1.8.4
>=1.9.0, <1.9.3
>=1.10.0, <1.10.1
1.1.6
1.2.2
1.3.4
1.4.3
1.5.7
1.6.5
1.7.3
1.8.4
1.9.3
1.10.1

Affected products

  • n/a Apache Flink

Classification

Weakness
  • CWE-74 Improper Neutralization of Special Elements in Output Used by a Downstream Component

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.