Skip to content

LF Edge eKuiper Vulnerable to Stored XSS in Configuration Key Functionality

Moderate severity GitHub Reviewed Published May 14, 2025 in lf-edge/ekuiper • Updated May 14, 2025

Package

gomod github.com/lf-edge/ekuiper (Go)

Affected versions

<= 1.14.7

Patched versions

None
gomod github.com/lf-edge/ekuiper/v2 (Go)
< 2.1.0
2.1.0

Description

Summary

Stored Cross-Site Scripting (XSS) vulnerability allows attackers to inject malicious scripts into web applications, which can then be executed in the context of other users' browsers. This can lead to unauthorized access to sensitive information, session hijacking, and spreading of malware, impacting user data privacy and application integrity.

Details

A user with rights to modificate the service (e.g. kuiperUser role) can inject XSS Payload into Connection Configuration key Name (confKey) parameter. Then, after any user with access to this service (e.g. admin) will try to delete this key, a payload will act in victim's browser.

PoC

  1. Authorize as a user with rights to modificate the service (e.g. kuiperUser role).
  2. Create a service or go to the existing one and access the Configuration > Connection page:

*Configuration > Connection page

  1. Open any existing Connection and press on Add configuration key:

image

  1. Set any name and Address, then intercept the request and add the following payload to the confKey parameter: 123%3Cimg%20src=1%20onerror%3dalert%281%29%3E:

image

  1. A new configuration key then will be set:

image

  1. (Optional) You can authorize another user with access to this service. For nexe steps I will use admin user
  2. After we push on delete button (trash icon) opposite the created connection, the payload will work:

image

Impact

Stored Cross-site Scripting (XSS) vulnerability

Reported by Alexey Kosmachev, Lead Pentester from Bi.Zone

References

@ngjaying ngjaying published to lf-edge/ekuiper May 14, 2025
Published by the National Vulnerability Database May 14, 2025
Published to the GitHub Advisory Database May 14, 2025
Reviewed May 14, 2025
Last updated May 14, 2025

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:L/A:N

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(8th percentile)

Weaknesses

CVE ID

CVE-2024-52290

GHSA ID

GHSA-9cwv-pxcr-hfjc

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.