This affects merge request/issue comments and probably other parts of the user interface. I am demonstrating PoCs on GitLab.com itself, as they don't affect anything outside of my test repo, which is private. It could be used to execute some js actions by contructing content that uses the pre-existing attached event handlers (for example, `onclick`), but I am not sure how far could that go — I have not reviewed that, the mentioned issues are already pretty bad. This could be used to make some issue/merge request pages inaccessible, to forge page content and potentially forge or hide other users comments in the thread. ## PoC 1 — full-size message Demo: https://gitlab.com/ChALkeR/my-private-test-project/issues/2 ```html

Hello there! Something has gone wrong, we are working on it.

In the meantime, play a game with us at example.com.

``` ## PoC 2 — basic JavaScript Demo: https://gitlab.com/ChALkeR/my-private-test-project/issues/3 ```html

click me

foo

``` There is a significant amout of onlick event listeners that are bound using just the classname, so it is possible to do some basic stuff with just classes and might be possible to execute more complex actions. I have not reviewed all instances in the JS where the classnames are used, that is irrelevant to fixing this issue. ## Suggested fix Both of the following should be applied: * Filter `class` attributes (higher priority). * Make sure that user content couldn't be displayed outside of the bounding box, e.g. by applying `oveflow:hidden` (lower priority).

GitLab: Unfiltered `class` attribute in markdown code