Stored XSS in Configuration Key Functionality
lf-edge ekuiper
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/lf-edge/ekuiper Go |
| No fix yet |
| github.com/lf-edge/ekuiper/v2 Go |
|
|
lf-edge ekuiper
| Product | Affected | Fixed in |
|---|---|---|
| github.com/lf-edge/ekuiper Go |
| No fix yet |
| github.com/lf-edge/ekuiper/v2 Go |
|
|
LF Edge eKuiper is a lightweight internet of things (IoT) data analytics and stream processing engine. Prior to version 2.1.0 user with rights to modificate the service (e.g. kuiperUser role) can inject a cross-site scripting payload into Connection Configuration key `Name` (`confKey`) parameter. After this setup, when any user with access to this service (e.g. admin) tries to delete this key, a payload acts in the victim's browser. Version 2.1.0 fixes the issue.
From the CVE record · GitHub_M
A user with permission to modify an eKuiper service can place a cross-site scripting payload in a Connection Configuration key’s Name parameter. The payload runs in another user’s browser when that user deletes the key.
Check deployments using Go package github.com/lf-edge/ekuiper/v2 before 2.1.0 or github.com/lf-edge/ekuiper through 1.14.7, for which no fix is listed.