First published: Tue Jan 05 2021(Updated: )
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.
Credit: security@apache.org security@apache.org
Affected Software | Affected Version | How to fix |
---|---|---|
redhat/flink | <1.11.3 | 1.11.3 |
redhat/flink | <1.12.0 | 1.12.0 |
Apache Flink | >=1.5.1<1.11.3 | |
maven/org.apache.flink:flink-runtime | >=1.5.1<1.11.3 | 1.11.3 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
(Appears in the following advisories)
CVE-2020-17518 is considered a high severity vulnerability due to its potential to allow unauthorized file access and modification.
To fix CVE-2020-17518, upgrade Apache Flink to version 1.11.3 or later.
Apache Flink versions from 1.5.1 up to but not including 1.11.3 are affected by CVE-2020-17518.
CVE-2020-17518 is associated with an attack that can exploit a REST handler to overwrite files on the server's file system.
Yes, CVE-2020-17518 is a file upload vulnerability that allows malicious uploads to be written to arbitrary locations.