Skip to content

Path Traversal in Apache Flink

High severity GitHub Reviewed Published Jan 6, 2021 to the GitHub Advisory Database • Updated May 24, 2024

Package

maven org.apache.flink:flink-runtime_2.11 (Maven)

Affected versions

>= 1.11.0, < 1.11.3

Patched versions

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

Description

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.

References

Published by the National Vulnerability Database Jan 5, 2021
Reviewed Jan 6, 2021
Published to the GitHub Advisory Database Jan 6, 2021
Last updated May 24, 2024

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

EPSS score

97.323%
(100th percentile)

Weaknesses

CVE ID

CVE-2020-17519

GHSA ID

GHSA-395w-qhqr-9fr6

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.