SSRF (Server-Side Request Forgery) in github.com/lf-edge/eku… (CVE-2025-24979)

Summary

SSRF in github.com/lf-edge/ekuiper/v2 (CVE-2025-24979). Risk of unauthorized operations or information disclosure. Exploitable via GET /services. Mitigation: upgrade to 2.4.0 or later.

Original description

The description as published by the source.

Summary

Server-side request forgery (SSRF) vulnerability in eKuiper allows an attacker with permissions to register external services or create rules to induce the eKuiper server to make requests to unintended network locations, such as internal services, loopback interfaces (localhost), or cloud metadata endpoints.

Details

Prior to v2.4.0, eKuiper external service registrations and HTTP invocations did not validate destination IP addresses. An attacker with access to the eKuiper management API could register an external service pointing to an internal address (such as http://127.0.0.1:9081 or other internal network services) and trigger queries using service functions (e.g. SELECT tsschemaless(...) FROM demo). This allows probing internal networks, leaking sensitive information (such as internal endpoints/credentials), or interacting with internal APIs accessible to the eKuiper host.

PoC

Create an external service with an address pointing to an internal network / localhost:

{
  "interfaces": {
    "tsschemaless": {
      "address": "http://127.0.0.1:9081",
      "protocol": "rest",
      "options": {
        "insecureSkipVerify": true,
        "headers": {
          "Accept-Charset": "utf-8"
        }
      },
      "schemaless": true
    }
  }
}

Load it to eKuiper and create a rule invoking it, e.g.: SELECT tsschemaless("get", "/metadata/sources/yaml/mqtt", *) FROM demo.
Run the rule. When data flows through the stream, the response…

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-24979 has been found in github.com/lf-edge/ekuiper/v2.
Attackers can target a specific entry point like GET /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-24979" on the vendor's site.

CVE-2025-24979 (github.com/lf-edge/ekuiper/v2) — CWE-918
Attack surface: GET /services / httpx.GetSSRFDialContext / basic.enablePrivateNet / kuiper.yaml
Patched: 2.4.0 — 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

SSRF (CWE-918) exists in github.com/lf-edge/ekuiper/v2. Attackers reach the vulnerable code path via GET /services.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/lf-edge/ekuiper/v2. Attack surface: GET /services / httpx.GetSSRFDialContext / basic.enablePrivateNet / kuiper.yaml.

🔥 Severity

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

🔧 How to fix

Update to 2.4.0.

🛡️ 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 GET /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

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 'GET /services' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'
```
アクセスログで GET /services への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。
3
Apply patch patch
```
Upgrade github.com/lf-edge/ekuiper/v2 to 2.4.0
```
ステージング環境で 2.4.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
4
Post-deployment verification verify
```
Replay attack against GET /services 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.0"}]}]

SSRF (Server-Side Request Forgery) in github.com/lf-edge/ekuiper/v2 (CVE-2025-24979)

Summary

Original description

Summary

Details

PoC

Auto-generated summary

Response actions

Affected packages

References