cve.bz

CVE-2020-17518 apache flink: Path traversal

7.5 highEPSS 49%Fix available

High (7.5) in apache flink. EPSS 49% estimated probability of exploitation activity in the next 30 days. Fixed in org.apache.flink:flink-runtime 1.11.3.

On this page
Apache Flink 1.5.1 introduced a REST handler that allows you to write an uploaded file to an arbitrary location on the local file system, through a maliciously modified HTTP HEADER. The files can be written to any location accessible by Flink 1.5.1. 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 a5264a6f41524afe8ceadf1d8ddc8c80f323ebc4 from apache/flink:master.

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
EPSS
49% (unchanged from 49% a week ago; 49% 30 days ago) estimated probability of exploitation activity in the next 30 days; 99th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CWEs
CWE-22 Improper Limitation of a Pathname to a Restricted Directory (Path traversal)
CWE-23 Relative Path Traversal
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2020-17518 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2020-17518?via=ask-ai-copy and https://cve.bz/cve/CVE-2020-17518?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2020-17518 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
apache:flinkfrom 1.5.1 before 1.11.3

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-7q5g-gph2-4rc6Mavenorg.apache.flink:flink-runtime>=1.5.1 <1.11.31.11.3

Red Hat

Red Hat rates this Moderate.

ProductPackageStateAdvisory
Red Hat Fuse 7.9flinkFixed 2021-08-11RHSA-2021:3140
Red Hat IntegrationFixed 2021-08-18RHSA-2021:3205
Red Hat Integration Camel Quarkus 2Fixed 2021-08-18RHSA-2021:3207
Red Hat Integration Camel K 1flinkNot affected
Red Hat Integration Camel Quarkus 1flinkNot affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2020-17518.

Detection rules

Ways to detect this CVE, not exploit code: the nuclei template that checks a system for it, and the Suricata and Snort rules that name it. A rule set may ship a rule turned off, so check yours by its sid.

Attack patterns (CAPEC)

  • CAPEC-76 Manipulating Web Input to File System Calls Likelihood: High · Severity: Very High
  • CAPEC-139 Relative Path Traversal Likelihood: High · Severity: High
  • CAPEC-64 Using Slashes and URL Encoding Combined to Bypass Validation Logic Likelihood: High · Severity: High
  • CAPEC-78 Using Escaped Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-79 Using Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-126 Path Traversal Likelihood: High · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON