GHSA-fv2p-qj5p-wqq4 LF Edge eKuiper vulnerable to File Path Traversal leading to file replacement

• Go github.com/lf-edge/ekuiper/v2: < 2.2.0 → fixed in 2.2.0 • Go github.com/lf-edge/ekuiper: <= 1.14.7 (no fix yet)

Summary Path traversal is also known as directory traversal. These vulnerabilities enable an attacker to read arbitrary files on the server that is running an application. In this case, an attacker might be able to write to arbitrary files on the server, allowing them to modify application data or behavior, and ultimately take full control of the server. Details The file handler function trusts the filename provided by the user. This includes the cases when the user uses a path instead of the filename. This makes possible to write arbitrary files to the system and replace the files owned by _kuiper_ user on the filesystem. The vulnerable function is `fileUploadHandler` which is shown below: https://github.com/lf-edge/ekuiper/blob/1e6b6b6601445eb05316532f5fbef7f0a863ecfe/internal/server/rest.go#L329-L359 Exploitation of this vulnerability allows an attacker to rewrite the files owned by ekuiper including the main kuiper binaries as they are owned by _kuiper_ user: PoC 0. The files should be uploaded to `/kuiper/data/uploads` directory. So let's move to the `/kuiper/data`, examine the existing files and create an empty `traversal-poc` file owned by _kuiper_: 1. Now, we can go to _Services > Configuration > File Management_ and try to upload file with name `../test`: In the response we can see the path of the uploaded file and can assume that the traversal worked. 2. Now we can try to change the `traversal-poc` file that we know exists on the server. It can be made with the following request: 3. Now, if we look at the server, we can see the file created in the traversed directory and the replaced poc-file: Impact • Possibility to upload files to external directories; • Possibility to rewrite any file owned by _kuiper_ user on the filesystem. Reported by Alexey Kosmachev, Lead Pentester from Bi.Zone