Every CVESearch/Get API key

GHSA-fv2p-qj5p-wqq4

LF Edge eKuiper vulnerable to File Path Traversal leading to file replacement

8.5 HighFix available

GHSA-fv2p-qj5p-wqq4 is a high vulnerability (CVSS 8.5) in github.com/lf-edge/ekuiper, published July 3, 2025. No source lists public exploit code. Fixed in github.com/lf-edge/ekuiper/v2 2.2.0.

What does this mean?
Severity
8.5 HighCVSS 3.1, GitHub Advisories
Exploit chance
UnscoredNo EPSS score yet
Exploitation
None knownNot on CISA’s or ENISA’s lists

Description

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

  1. 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.

  1. 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:

  1. 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

Attack profile

How easy it is to exploit

Attack vector
Network
Complexity
Low
Privileges needed
Low
User interaction
None

What an attacker can affect

Confidentiality
None
Integrity
High
Availability
Low

Affected packages

Affected packages
PackageAffectedFixed
github.com/lf-edge/ekuiper/v2
Go
before 2.2.0
2.2.0
github.com/lf-edge/ekuiper
Go
through 1.14.7None known
github.com/lf-edge/ekuiper
Go
All versionsNone known

What each source reports

GitHub Advisories Score used8.5

LF Edge eKuiper vulnerable to File Path Traversal leading to file replacement

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

  1. 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.

  1. 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:

  1. 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

Record
GHSA-fv2p-qj5p-wqq4
CVSS 3.1
8.5 HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:L
Weakness
CWE-24
Updated
2026-11-02
OSV8.5

LF Edge eKuiper vulnerable to File Path Traversal leading to file replacement

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

  1. 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.

  1. 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:

  1. 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

Record
GHSA-fv2p-qj5p-wqq4
CVSS 3.1
8.5 HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:L
Weakness
CWE-24
Updated
2026-11-02
OSVGO-2025-3799No score

LF Edge eKuiper vulnerable to File Path Traversal leading to file replacement in github.com/lf-edge/ekuiper

LF Edge eKuiper vulnerable to File Path Traversal leading to file replacement in github.com/lf-edge/ekuiper

Record
GO-2025-3799
Updated
2026-11-02

History

History
RecordedChangedSources
first indexedGitHub Advisories, OSV

Dates are when Every CVE recorded each change. Upstream dates may differ.

References

MoveEnter Open