Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Possible self-XSS vulnerability in matrix tool #647

Open
4 tasks
kltm opened this issue Apr 19, 2022 · 0 comments
Open
4 tasks

Possible self-XSS vulnerability in matrix tool #647

kltm opened this issue Apr 19, 2022 · 0 comments

Comments

@kltm
Copy link
Member

kltm commented Apr 19, 2022

It is currently possible to inject possibly problematic code into the matrix interface that might be approaching an exploitable XSS attack for users (self-XSS). For example, unsanitized around:

jQuery("#info").empty();
jQuery("#info").append("x: <b>" + xn.name + "</b> (" + xn.id + ")");
jQuery("#info").append("<br />");
jQuery("#info").append("y: <b>" + yn.name + "</b> (" + yn.id + ")");
jQuery("#info").append("<br />");
jQuery("#info").append("SBC: <b>" + sbc + "</b>");
jQuery("#info").show();

or, for example, entering the following ID:

<script>alert()</script>

Currently, tagged as enhancement; will recode as showstopper if this gets elevated by security.


Two known parts, and one notice:

  • matrix layout itself (enter script term)
  • in hover pop-up
  • let Miguel know when done for re-scan
  • roll out to all amigo endpoints
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

1 participant