What is CVE-2020-17519?

CVE-2020-17519 is a high-severity path traversal vulnerability in org.apache.flink:flink-runtime_2.11 (maven), affecting versions >= 1.11.0, < 1.11.3. It is fixed in 1.11.3. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.

How severe is CVE-2020-17519?

CVE-2020-17519 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which packages are affected by CVE-2020-17519?

org.apache.flink:flink-runtime_2.11 (maven) versions >= 1.11.0, = 1.11.0, < 1.11.3.

Is there a fix for CVE-2020-17519?

Yes. CVE-2020-17519 is fixed in 1.11.3. Upgrade to this version or later.

Is CVE-2020-17519 exploitable, and should I be worried?

Whether CVE-2020-17519 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2020-17519 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2020-17519

Q: How severe is CVE-2020-17519?

CVE-2020-17519 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which packages are affected by CVE-2020-17519?

org.apache.flink:flink-runtime_2.11 (maven) versions >= 1.11.0, = 1.11.0, < 1.11.3.

Q: Is there a fix for CVE-2020-17519?

Yes. CVE-2020-17519 is fixed in 1.11.3. Upgrade to this version or later.

Q: Is CVE-2020-17519 exploitable, and should I be worried?

Whether CVE-2020-17519 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2020-17519 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2020-17519?

Upgrade: org.apache.flink:flink-runtime_2.11 to 1.11.3 or later, org.apache.flink:flink-runtime_2.12 to 1.11.3 or later.

Summary

Path Traversal in Apache Flink

A change introduced in Apache Flink 1.11.0 (and released in 1.11.1 and 1.11.2 as well) allows attackers to read any file on the local filesystem of the JobManager through the REST interface of the JobManager process. Access is restricted to files accessible by the JobManager process. All users should upgrade to Flink 1.11.3 or 1.12.0 if their Flink instance(s) are exposed. The issue was fixed in commit b561010b0ee741543c3953306037f00d7a9f0801 from apache/flink:master.

Impact

Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files. Typical impact: unauthorized file read or write outside the intended directory.

CVE-2020-17519 has a CVSS score of 7.5 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.11.3); upgrading removes the vulnerable code path.

Affected versions

org.apache.flink:flink-runtime_2.11 (>= 1.11.0, < 1.11.3) org.apache.flink:flink-runtime_2.12 (>= 1.11.0, < 1.11.3)

Security releases

org.apache.flink:flink-runtime_2.11 → 1.11.3 (maven) org.apache.flink:flink-runtime_2.12 → 1.11.3 (maven)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade the following packages to resolve this vulnerability:

org.apache.flink:flink-runtime_2.11 to 1.11.3 or later; org.apache.flink:flink-runtime_2.12 to 1.11.3 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2020-17519? CVE-2020-17519 is a high-severity path traversal vulnerability in org.apache.flink:flink-runtime_2.11 (maven), affecting versions >= 1.11.0, < 1.11.3. It is fixed in 1.11.3. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.
How severe is CVE-2020-17519? CVE-2020-17519 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which packages are affected by CVE-2020-17519?
- org.apache.flink:flink-runtime_2.11 (maven) (versions >= 1.11.0, < 1.11.3)
- org.apache.flink:flink-runtime_2.12 (maven) (versions >= 1.11.0, < 1.11.3)
Is there a fix for CVE-2020-17519? Yes. CVE-2020-17519 is fixed in 1.11.3. Upgrade to this version or later.
Is CVE-2020-17519 exploitable, and should I be worried? Whether CVE-2020-17519 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2020-17519 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2020-17519?
- Upgrade org.apache.flink:flink-runtime_2.11 to 1.11.3 or later
- Upgrade org.apache.flink:flink-runtime_2.12 to 1.11.3 or later