-
-
Notifications
You must be signed in to change notification settings - Fork 885
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
[Security]: Javascript links #3505
Comments
@dessalines @Nutomic Does this hack still work in Update: Tested on What is lemmy's designated procedure for sanitizing user input:
|
With this change only http(s) schemes are allowed for post.url field. This is checked for incoming api and federation requests. Existing posts in database which are sent to clients are not checked. Neither does it check urls in markdown.
With this change only http(s) schemes are allowed for post.url field. This is checked for incoming api and federation requests. Existing posts in database which are sent to clients are not checked. Neither does it check urls in markdown.
With this change only http(s) schemes are allowed for post.url field. This is checked for incoming api and federation requests. Existing posts in database which are sent to clients are not checked. Neither does it check urls in markdown.
The fix is deployed on voyager.lemmy.ml so you can test there (signups are open). Looks like the markdown parser already prohibits javascript links so this seems completely fixed to me. |
As basically all of what I discovered is being exploited in the wild I have posted what I found: https://akkoma.nrd.li/notice/AXXhAVF7N5ZH1V972W I did reply to the kind email I was sent, I assume my response and my earlier emails must have gotten caught in a spam filter or something. In my response I did mention that I signed up for a matrix account and my user id is |
@terribleplan Sent you a message. This issue is finished. |
Requirements
Summary
Javascript is allowed as a scheme in links. This should likely be restricted to only
http
andhttps
. This should probably be enforced at a federation level as well reject non-http(s) URIs on links. This was reported in the wild hereI tried to contact
[email protected]
over a week ago but gotten no response for a separate issue that is made much more severe due to this issue. Please contact me at [email protected] to discuss the other issue that has not yet been publicly disclosed elsewhere yet.Steps to Reproduce
javascript:alert('hacked')
Technical Details
You can see a link I tested this with here.
Version
0.17.4 and up
Lemmy Instance URL
lemmy.nrd.li
The text was updated successfully, but these errors were encountered: