Arbitrary file write via multipart filename traversal
Published Jan 5, 2021 · Updated Feb 13, 2025
Path traversal in Apache Flink 1.5.1 through 1.11.2 allows remote attackers to write uploaded files through the REST API. FileUploadHandler resolves the multipart Content-Disposition filename against its upload directory without stripping path components. An exposed, unauthenticated REST interface is sufficient, and writes are limited to filesystem locations accessible to the Flink process.
Summary
What happened
Path traversal in Apache Flink 1.5.1 through 1.11.2 allows remote attackers to write uploaded files through the REST API. FileUploadHandler resolves the multipart Content-Disposition filename against its upload directory without stripping path components. An exposed, unauthenticated REST interface is sufficient, and writes are limited to filesystem locations accessible to the Flink process.
The record
- CVE
- CVE-2020-17518
- Published
- Jan 5, 2021
- Updated
- Feb 13, 2025
- Vendor
- The Apache Software Foundation
- Product
- Apache Flink
- Classifications
- CWE-22, CWE-23, T1105
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 5, 2021CVE publishedPublication date reported by the CVE source.
- Feb 13, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=Apache Flink 1.5.1 to 1.11.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo