Is CVE-2020-17519 exploited in the wild?

Yes. CVE-2020-17519 is known to be exploited in the wild, first recorded on 23 May 2024. Treat it as urgent.

How severe is CVE-2020-17519?

Critical severity, with a CVSS score of 3.1, published 6 January 2021.

Which products and versions are affected?

org.apache.flink:flink-runtime_2.11 (Maven) ECOSYSTEM:introduced=1.11.0,fixed=1.11.3; org.apache.flink:flink-runtime_2.12 (Maven) ECOSYSTEM:introduced=1.11.0,fixed=1.11.3.

Is there a fix for CVE-2020-17519?

Yes. org.apache.flink:flink-runtime_2.11 (Maven): upgrade to 1.11.3 or later; org.apache.flink:flink-runtime_2.12 (Maven): upgrade to 1.11.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2020-17519 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2020-17519?

Check whether you run Apache Flink, org.apache.flink:flink-runtime_2.11 (Maven) or org.apache.flink:flink-runtime_2.12 (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2020-17519: Path Traversal in Apache Flink

CVE-2020-17519 · Severity: critical · CVSS 3.1 · Exploited in the wild · Published 2021-01-06

Apache Flink contains an improper access control vulnerability in the JobManager's REST interface. An unauthenticated remote attacker can exploit this to read any file on the local filesystem that is accessible to the JobManager process.

Vendors: Apache, Maven.

Quick answers

Is CVE-2020-17519 exploited in the wild?: Yes. CVE-2020-17519 is known to be exploited in the wild, first recorded on 23 May 2024. Treat it as urgent.
How severe is CVE-2020-17519?: Critical severity, with a CVSS score of 3.1, published 6 January 2021.
Which products and versions are affected?: org.apache.flink:flink-runtime_2.11 (Maven) ECOSYSTEM:introduced=1.11.0,fixed=1.11.3; org.apache.flink:flink-runtime_2.12 (Maven) ECOSYSTEM:introduced=1.11.0,fixed=1.11.3.
Is there a fix for CVE-2020-17519?: Yes. org.apache.flink:flink-runtime_2.11 (Maven): upgrade to 1.11.3 or later; org.apache.flink:flink-runtime_2.12 (Maven): upgrade to 1.11.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2020-17519 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2020-17519?: Check whether you run Apache Flink, org.apache.flink:flink-runtime_2.11 (Maven) or org.apache.flink:flink-runtime_2.12 (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

org.apache.flink:flink-runtime_2.11 (Maven): upgrade to 1.11.3 or later

# set org.apache.flink:flink-runtime_2.11 to 1.11.3 in your pom.xml or build.gradle

org.apache.flink:flink-runtime_2.12 (Maven): upgrade to 1.11.3 or later

# set org.apache.flink:flink-runtime_2.12 to 1.11.3 in your pom.xml or build.gradle

Affected products

Apache Flink 1.11.0, 1.11.1, 1.11.2

Identifiers

CVE-2020-17519
GHSA-395w-qhqr-9fr6

Timeline

2021-01-05: disclosed: Public disclosure via mailing list
2024-05-23: kev added: Added to CISA Known Exploited Vulnerabilities Catalog
2024-05-23: advisory: NVD publication date

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.