GHSA-fv2p-qj5p-wqq4: LF Edge eKuiper vulnerable to File Path Traversal leading to file replacement
Noroxi assessment
Priority: Monitor (action score 34/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: github.com/lf-edge/ekuiper/v2 (Go) 2.2.0.
Low priority for now. Upgrade to github.com/lf-edge/ekuiper/v2 (Go) 2.2.0 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: OSV
### 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
- Published
- Jul 3, 2025
- Updated
- Jul 28, 2025
- EPSS
- —
- CWE
- CWE-24
Report tools
Action score
34
Low priority for now.
- CVSS
- 34 / 40 · 8.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · —
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| Go | github.com/lf-edge/ekuiper/v2 | pkg:golang/github.com/lf-edge/ekuiper/v2 |
| Go | github.com/lf-edge/ekuiper | pkg:golang/github.com/lf-edge/ekuiper |
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Go | github.com/lf-edge/ekuiper | from 0 | — |
| Go | github.com/lf-edge/ekuiper | up to and including 1.14.7 | — |
| Go | github.com/lf-edge/ekuiper/v2 | before 2.2.0 | 2.2.0 |
Same product
Go: all recordsOther highest-scoring records for the same primary product.
- GHSA-rj4j-2jph-gg43LF Edge eKuiper is vulnerable to Arbitrary File Read/Write via unsanitized names and zip extraction0Monitor
- GHSA-gj54-gwj9-x2c6eKuiper /config/uploads API arbitrary file writing may lead to RCE0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Go:github.com/lf-edge/ekuiper/v2 | 2.2.0 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- high · data or configuration can be modified
- Availability
- low · the service can be disrupted
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality impact
- None
- Integrity impact
- High
- Availability impact
- Low
Weakness class (CWE)
CWE-24 · Path Traversal: '../filedir'CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:L
osv
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.