Headline
GHSA-v4v2-8h88-65qj: Attribute Injection leading to XSS(Cross-Site-Scripting)
Summary
Google Analytics element Attribute Injection leading to XSS
Details
Since the custom status interface can set an independent Google Analytics ID and the template has not been sanitized, there is an attribute injection vulnerability here, which can lead to XSS attacks.
PoC
- Run the latest version of the louislam/uptime-kuma container and initialize the account password.
- Create a new status page.
- Edit the status page and change the Google Analytics ID to following payload(it only works for firefox. Any attribute can be injected, but this seems the most intuitive):
123123" onafterscriptexecute=alert(window.name+1),eval(window.name) a="x
- Click Save and return to the interface. XSS occurs.
screenshots:
Impact
Latest docker version (Other versions have not been tested accurately)
Summary
Google Analytics element Attribute Injection leading to XSS
Details
Since the custom status interface can set an independent Google Analytics ID and the template has not been sanitized, there is an attribute injection vulnerability here, which can lead to XSS attacks.
PoC
Run the latest version of the louislam/uptime-kuma container and initialize the account password.
Create a new status page.
Edit the status page and change the Google Analytics ID to following payload(it only works for firefox. Any attribute can be injected, but this seems the most intuitive):
123123" onafterscriptexecute=alert(window.name+1),eval(window.name) a="x
- Click Save and return to the interface. XSS occurs.
screenshots:
Impact
Latest docker version (Other versions have not been tested accurately)
References
- GHSA-v4v2-8h88-65qj