Live data from Hacker News

Show HN: HN comments sidebar bookmarklet

gist.github.com

1–10 of 14 posts

Re: Show HN: HN comments sidebar bookmarklet

#5

There was an extension called Epiverse that used to do this + reddit comments, I dearly miss it. Although I began to notice that I was more concerned with the comments than the pages themselves.

https://epiverse.co/

Relevant comment: https://news.ycombinator.com/item?id=30187483

Re: Show HN: HN comments sidebar bookmarklet

#8
This is trivially vulnerable to XSS [1]. Someone can leave a comment of the form:

    https://">alert(1)
and if you click the bookmarklet for the page that comment was discussing then their javascript will execute in your logged in context on that website.

[1]: https://gist.github.com/postmalloc/e2602752d46c5b9dee2446235...

Re: Show HN: HN comments sidebar bookmarklet

#9
post #8

This is trivially vulnerable to XSS [1]. Someone can leave a comment of the form: https://"> alert(1) and if you click the bookmarklet for the page that comment was discussing then their javascript will execute in your logged in context on that website. [1]: https://gist.github.com/postmalloc/e2602752d46c5b9dee2446235...

Thank you for spotting this! I updated the code to escape some special characters.

For people reading this, the parent comment is referring to this line[1] from a previous revision of the gist.

[1]: https://gist.github.com/postmalloc/e2602752d46c5b9dee2446235...

Re: Show HN: HN comments sidebar bookmarklet

#10
post #9
post #8

This is trivially vulnerable to XSS [1]. Someone can leave a comment of the form: https://"> alert(1) and if you click the bookmarklet for the page that comment was discussing then their javascript will execute in your logged in context on that website. [1]: https://gist.github.com/postmalloc/e2602752d46c5b9dee2446235...

Thank you for spotting this! I updated the code to escape some special characters. For people reading this, the parent comment is referring to this line[1] from a previous revision of the gist. [1]: https://gist.github.com/postmalloc/e2602752d46c5b9dee2446235...

> For people reading this, the parent comment is referring to this line[1] from a previous revision of the gist.

That was not the line, it was linking to this innerHTML call: https://gist.github.com/postmalloc/e2602752d46c5b9dee2446235...

Also as a defense mitigation I don't think escaping is ever going to be effective, it would be better to create anchor elements directly. With your current approach I can still XSS with, for instance:

    https://"onmouseenter=alert(1)"
Post reply on HN