Path Traversal in github.com/lf-edge/ekuiper/v2 (CVE-2025-58363)

Summary

Path traversal in github.com/lf-edge/ekuiper/v2 (CVE-2025-58363). Risk of unauthorized operations or information disclosure. Exploitable via POST /plugins/. Mitigation: upgrade to 2.4.1 or later.

Original description

The description as published by the source.

Summary

A path traversal vulnerability in eKuiper's administrative management endpoints allows privileged users or attackers with access to management APIs to delete arbitrary files or directories on the host system.

Details

In internal/plugin/native/manager.go, the plugin installation endpoint (POST /plugins/*) constructs a temporary directory path by directly joining user-supplied resource names (name) without sufficient sanitization. Supplying path traversal sequences (such as ../../...) causes the deferred cleanup operation (os.RemoveAll) to target arbitrary directories outside the intended plugin directory.

A related issue in configuration and rule lifecycle management where unvalidated rule identifiers could influence file deletion paths was also addressed by introducing unified identifier and file name validation.

PoC

Target file deletion via plugin installation endpoint:

POST /plugins/sources HTTP/1.1
Host: 127.0.0.1:9081
Content-Type: application/json

{
  "name": "../../../../../tmp/target.txt",
  "file": "http://example.com/plugin.zip",
  "shellParas": [],
  "functions": []
}

When the request finishes, /tmp/target.txt is removed by os.RemoveAll.

Impact

An attacker with access to eKuiper management APIs can cause arbitrary file or directory deletion, potentially leading to denial of service or disruption of the host environment. This vulnerability provides a delete-only capability and does not permit arbitrary file…

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2025-58363 has been found in github.com/lf-edge/ekuiper/v2.
Attackers can target a specific entry point like POST /plugins/ over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade github.com/lf-edge/ekuiper/v2 to 2.4.1 or later.
If unsure, ask your IT team or search "github.com/lf-edge/ekuiper/v2 CVE-2025-58363" on the vendor's site.

CVE-2025-58363 (github.com/lf-edge/ekuiper/v2) — CWE-22
Attack surface: POST /plugins/ / POST /plugins/sources / name / os.RemoveAll
Patched: 2.4.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

Path traversal (CWE-22) exists in github.com/lf-edge/ekuiper/v2. Attackers reach the vulnerable code path via POST /plugins/.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/lf-edge/ekuiper/v2. Attack surface: POST /plugins/ / POST /plugins/sources / name / os.RemoveAll.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 2.4.1.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual POST /plugins/ requests with malformed payloads or SQL meta-characters. Run grep -r 'github.com/lf-edge/ekuiper/v2' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

1
Identify exposure identify
```
grep -r 'github.com/lf-edge/ekuiper/v2' . | grep -v node_modules
```
リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で github.com/lf-edge/ekuiper/v2 を grep し、稼働しているサービス・バージョンを把握する。
2
Hunt for indicators of compromise detect
```
grep 'POST /plugins/' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'
```
アクセスログで POST /plugins/ への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。
3
Apply patch patch
```
Upgrade github.com/lf-edge/ekuiper/v2 to 2.4.1
```
ステージング環境で 2.4.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
4
Post-deployment verification verify
```
Replay attack against POST /plugins/ on staging to confirm patch closes the vector
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

go github.com/lf-edge/ekuiper/v2

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.4.1"}]}]

Summary

Original description

Summary

Details

PoC

Impact

Auto-generated summary

Response actions

Affected packages

References