LF Edge eKuiper has Stored XSS in Rules Functionality
lf-edge ekuiper
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/lf-edge/ekuiper/v2 Go |
|
|
| github.com/lf-edge/ekuiper Go |
| No fix yet |
lf-edge ekuiper
| Product | Affected | Fixed in |
|---|---|---|
| github.com/lf-edge/ekuiper/v2 Go |
|
|
| github.com/lf-edge/ekuiper Go |
| No fix yet |
LF Edge eKuiper is an internet-of-things data analytics and stream processing engine. Prior to version 2.0.8, auser with rights to modify the service (e.g. kuiperUser role) can inject a cross-site scripting payload into the rule `id` parameter. Then, after any user with access to this service (e.g. admin) tries make any modifications with the rule (update, run, stop, delete), a payload acts in the victim's browser. Version 2.0.8 fixes the issue.
From the CVE record · GitHub_M
A user with permission to modify the service, such as a kuiperUser, can inject a cross-site scripting payload into a rule's id parameter. The payload runs in another user's browser when that user tries to update, run, stop, or delete the rule.
Teams running LF Edge eKuiper through Go package github.com/lf-edge/ekuiper/v2 before 2.0.8 or github.com/lf-edge/ekuiper at version 1.14.7 or earlier should check.