Cross-Site Scripting (XSS) in github.com/lf-edge/ekuiper/v2 (CVE-2025-24978)
Summary
Cross-site scripting in github.com/lf-edge/ekuiper/v2 (CVE-2025-24978). Risk of unauthorized operations or information disclosure. Exploitable via POST /services. Mitigation: upgrade to 2.4.0 or later.
Original description
The description as published by the source.
Summary
A Cross-Site Scripting (XSS) vulnerability in external service creation allows an authenticated attacker to inject HTML/script payloads into external service names, which may execute in a user's browser when rendered by administrative web interfaces.
Details
Prior to v2.4.0, external service registration endpoints did not strictly enforce alphanumeric character restrictions on service names. An operator or attacker with API access could register a service using a crafted name containing HTML elements (such as ``). If an administrative web UI rendered the unescaped service name, arbitrary script execution could occur in the context of the user's browser session.
PoC
- Create an external service JSON definition with a filename containing an XSS payload, e.g.
.jsoninside a ZIP archive. - In external service creation, upload the ZIP and provide the matching service name: ``.
- Upon service registration, the unescaped name executes when rendered in the UI context.
Impact
Self-XSS / Stored XSS leading to potential session token leakage or unauthorized actions in the context of the affected user's browser session.
Remediation & Patches
- Upgrade to eKuiper >= 2.4.0: Strict alphanumeric identifier validation (
validate.ValidateID) is now enforced on all external service creation and update endpoints, rejecting invalid characters.
Workarounds
- Protect eKuiper management endpoints (
POST /services) with authentication and network-level…
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-24978 has been found in github.com/lf-edge/ekuiper/v2.
Attackers can target a specific entry point like POST /services 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.0 or later.
If unsure, ask your IT team or search "github.com/lf-edge/ekuiper/v2 CVE-2025-24978" on the vendor's site.
CVE-2025-24978 (github.com/lf-edge/ekuiper/v2) — CWE-79
Attack surface: POST /services / validate.ValidateID
Patched: 2.4.0 — apply immediately
Workaround: - Protect eKuiper management endpoints (POST /services) with authentication and network-level firewalls.
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.
Cross-site scripting (XSS) (CWE-79) exists in github.com/lf-edge/ekuiper/v2. Attackers reach the vulnerable code path via POST /services.
Check the vendor advisory for the affected versions of github.com/lf-edge/ekuiper/v2. Attack surface: POST /services / validate.ValidateID.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 2.4.0.
Workaround: - Protect eKuiper management endpoints (POST /services) with authentication and network-level firewalls.
Search webserver/proxy logs for unusual POST /services 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
-
1Identify 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 し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'POST /services' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
POST /servicesへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply temporary workaround mitigate
- Protect eKuiper management endpoints (`POST /services`) with authentication and network-level firewalls.パッチが適用されるまでの応急処置として、- Protect eKuiper management endpoints (
POST /services) with authentication and network-level firewalls. を実施。回避策の副作用 (機能低下) を確認した上で。 -
4Apply patch patch
Upgrade github.com/lf-edge/ekuiper/v2 to 2.4.0ステージング環境で 2.4.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
5Post-deployment verification verify
Replay attack against POST /services on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
References
- web github.com
- web github.com
- web github.com