CVE-2025-24979: LF Edge eKuiper SSRF Vulnerability

MODERATE
Advisory Identifier: GHSA-pqqc-8v73-9gg2
CVSS 5.5
CWE-918
Published
Advisory Summary

CVE-2025-24979 is a MODERATE (CVSS 5.5) ssrf vulnerability (CWE-918: Server-Side Request Forgery (SSRF)) affecting LF Edge eKuiper libraries in the Go ecosystem. The issue involves ssrf in external service. Remediation is available by upgrading affected packages to version 2.4.0.

CVE-2025-24979 at a Glance

CVE Identifier CVE-2025-24979
GHSA Identifier GHSA-pqqc-8v73-9gg2
Severity MODERATE
CVSS v3.1 Base Score 5.5
CWE Classification CWE-918: Server-Side Request Forgery (SSRF)
Affected Product LF Edge eKuiper
Package Ecosystem Go
Published Date
Last Updated

Security Impact

CVSS: 5.5

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:L/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required High (PR:H)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity Low (I:L)
Availability None (A:N)

How to Fix CVE-2025-24979

To remediate this vulnerability, upgrade all affected LF Edge eKuiper dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/lf-edge/ekuiper/v2 fixed: 2.4.0
Upgrade github.com/lf-edge/ekuiper/v2 to 2.4.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for github.com/lf-edge/ekuiper/v2

How to Check if You Are Affected

To determine whether your application is affected by CVE-2025-24979, inspect your project dependencies for LF Edge eKuiper:

inspect dependencies for github.com/lf-edge/ekuiper/v2

Analyze the terminal output to locate any version of LF Edge eKuiper in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.4.0), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-918: Server-Side Request Forgery (SSRF), where the web server receives a url or similar request from an upstream component and retrieves the contents of this url, but it does not sufficiently ensure that the request is being sent to the expected destination. In LF Edge eKuiper, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### 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 1. Create an external service with an address pointing to an internal network / localhost: ```json { "interfaces": { "tsschemaless": { "address": "http://127.0.0.1:9081", "protocol": "rest", "options": { "insecureSkipVerify": true, "headers": { "Accept-Charset": "utf-8" } }, "schemaless": true } } } ``` 2. Load it to eKuiper and create a rule invoking it, e.g.: `SELECT tsschemaless("get", "/metadata/sources/yaml/mqtt", *) FROM demo`. 3. Run the rule. When data flows through the stream, the response from the internal service is retrieved and can be routed to an external sink or inspected. ### Impact Server-Side Request Forgery (SSRF) allowing unauthorized access / probing of internal network services. ### Remediation & Patches - **Upgrade to eKuiper >= 2.4.0**: Starting with v2.4.0, SSRF protection (`httpx.GetSSRFDialContext`) is enabled by default across HTTP clients, blocking requests to private, loopback, link-local, multicast, and unspecified IP addresses. ### Workarounds (for versions < 2.4.0) If unable to upgrade immediately: 1. **Restrict Management API Access**: Restrict access to the eKuiper REST API (port 9081) and CLI using network firewalls, reverse proxies, and authentication so only trusted administrators can create or update services and rules. 2. **Egress Network Filtering**: Use firewall / iptables rules or container network isolation to block outbound requests from eKuiper to private subnets, loopback addresses, and cloud metadata endpoints (`169.254.169.254`). 3. **Audit Service Definitions**: Regularly review registered external services (`GET /services` or `bin/kuiper show services`) to verify target hosts. ### Notes for Users Upgrading to >= 2.4.0 - In v2.4.0 and later, `basic.enablePrivateNet` in `kuiper.yaml` defaults to `false` (blocking private network access). - If a developer's deployment legitimately requires eKuiper to communicate with internal REST services or private networks, they can explicitly opt in by setting `basic.enablePrivateNet: true` (or via environment variable `KUIPER__BASIC__ENABLEPRIVATENET=true`). Ensure eKuiper's API is protected before enabling this setting. Reported by Alexey Kosmachev, Bi.Zone

CVE-2025-24979 Affected LF Edge eKuiper Versions

1 component(s)
Fixed Versions:
2.4.0
Product / Package Ecosystem Affected Versions Fixed Version
github.com/lf-edge/ekuiper/v2
Go
< 2.4.0
2.4.0

References

Frequently Asked Questions

What is CVE-2025-24979?
CVE-2025-24979 is a security vulnerability in LF Edge eKuiper involving SSRF in External Service under CWE-918: Server-Side Request Forgery (SSRF).
Which LF Edge eKuiper versions are affected?
Affected versions include releases prior to 2.4.0 across affected packages: github.com/lf-edge/ekuiper/v2.
What version fixes CVE-2025-24979?
Upgrading to 2.4.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/lf-edge/ekuiper/v2 affected?
Yes, github.com/lf-edge/ekuiper/v2 is affected in releases prior to 2.4.0. Upgrade your dependency to 2.4.0 or later.
What is the CVSS score of CVE-2025-24979?
CVE-2025-24979 has a CVSS v3.1 base score of 5.5 (MODERATE) with vector string CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:L/A:N.
What CWE is associated with CVE-2025-24979?
CVE-2025-24979 is classified under CWE-918: Server-Side Request Forgery (SSRF) (The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.).
How can I check Go dependencies for CVE-2025-24979?
Run the dependency tree command: 'inspect dependencies for github.com/lf-edge/ekuiper/v2'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-pqqc-8v73-9gg2",
  "modified" : "2026-09-09T17:56:32Z",
  "published" : "2026-09-09T17:56:32Z",
  "aliases" : [ "CVE-2025-24979" ],
  "summary" : "LF Edge eKuiper: SSRF in External Service",
  "details" : "### Summary\nServer-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.\n\n### Details\nPrior 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.\n\n### PoC\n1. Create an external service with an address pointing to an internal network / localhost:\n\n```json\n{\n  \"interfaces\": {\n    \"tsschemaless\": {\n      \"address\": \"http://127.0.0.1:9081\",\n      \"protocol\": \"rest\",\n      \"options\": {\n        \"insecureSkipVerify\": true,\n        \"headers\": {\n          \"Accept-Charset\": \"utf-8\"\n        }\n      },\n      \"schemaless\": true\n    }\n  }\n}\n```\n2. Load it to eKuiper and create a rule invoking it, e.g.: `SELECT tsschemaless(\"get\", \"/metadata/sources/yaml/mqtt\", *) FROM demo`.\n3. Run the rule. When data flows through the stream, the response from the internal service is retrieved and can be routed to an external sink or inspected.\n\n### Impact\nServer-Side Request Forgery (SSRF) allowing unauthorized access / probing of internal network services.\n\n### Remediation & Patches\n- **Upgrade to eKuiper >= 2.4.0**: Starting with v2.4.0, SSRF protection (`httpx.GetSSRFDialContext`) is enabled by default across HTTP clients, blocking requests to private, loopback, link-local, multicast, and unspecified IP addresses.\n\n### Workarounds (for versions < 2.4.0)\nIf unable to upgrade immediately:\n1. **Restrict Management API Access**: Restrict access to the eKuiper REST API (port 9081) and CLI using network firewalls, reverse proxies, and authentication so only trusted administrators can create or update services and rules.\n2. **Egress Network Filtering**: Use firewall / iptables rules or container network isolation to block outbound requests from eKuiper to private subnets, loopback addresses, and cloud metadata endpoints (`169.254.169.254`).\n3. **Audit Service Definitions**: Regularly review registered external services (`GET /services` or `bin/kuiper show services`) to verify target hosts.\n\n### Notes for Users Upgrading to >= 2.4.0\n- In v2.4.0 and later, `basic.enablePrivateNet` in `kuiper.yaml` defaults to `false` (blocking private network access).\n- If a developer's deployment legitimately requires eKuiper to communicate with internal REST services or private networks, they can explicitly opt in by setting `basic.enablePrivateNet: true` (or via environment variable `KUIPER__BASIC__ENABLEPRIVATENET=true`). Ensure eKuiper's API is protected before enabling this setting.\n\nReported by Alexey Kosmachev, Bi.Zone",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:L/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/lf-edge/ekuiper/v2"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "2.4.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/lf-edge/ekuiper/security/advisories/GHSA-pqqc-8v73-9gg2"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/lf-edge/ekuiper"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/lf-edge/ekuiper/releases/tag/v2.4.0"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-918" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-09-09T17:56:32Z",
    "nvd_published_at" : null
  }
}