cross-posted from: https://sh.itjust.works/post/923025
lemmy.world is a victim of an XSS attack right now and the hacker simply injected a JavaScript redirection into the sidebar.
It appears the Lemmy backend does not escape HTML in the main sidebar. Not sure if this is also true for community sidebars.

18 Comments
Gamingodcat@2dl.eu · 3 pts · 3y
This has nothing to do with XSS, it is a simple HTML injection vulnerability, and it can only be exploited by instance admins.
Also Lemmy.world appears to have been running a custom frontend so it’s hard to say how widespread the affects of this are.
TruckBC@lemmy.ca · 1 pts · 3y
You seem to be following the situation closely. Could you please DM me on Matrix?
pazukaza@lemmy.ml · -1 pts · 3y
Worst case scenario, they can steal your Lemmy session, right?
Which isn't super bad for a service like Lemmy. This isn't a social network, so most contact list scams would be useless.
Edit: just read the targets were admins. That IS bad.
Auli@lemmy.ca · 3 pts · 3y
Lemmy isn't a social network? Seems to be one to me.
pazukaza@lemmy.ml · 3 pts · 3y
I mean, not in the traditional sense. You don't have your family and friends as Lemmy contacts and share posts with them. It's more anonymous.
AlternateRoute@lemmy.ca · 2 pts · 3y
I wonder if there is something the Lemmy.ca admins can do to disable the sidebar or put a workaround in to prevent this.
TruckBC@lemmy.ca · 4 pts · 3y
At this point I'm monitoring inter-instance communications channels non stop even though I should be in bed. I will be temporarily removing admins that have not responded to my inquiry to confirm if they have 2FA authentication turned on as initial access appears to have been gained due to lack of 2FA.
If there's anything additinal we can do, we will.
tarjeezy@lemmy.ca · 1 pts · 3y
Good luck, and thanks for all your hard work. I don't know if you already saw this, but it looks like this might be the vector for the account compromise. If that's the case, I don't think 2FA is enough to protect, because it's exfiltrating the session cookies of someone already logged in. Seems like the precaution is for admins to avoid clicking any suspicious links. I realize the irony of sharing a link about this, but at least it's to a thread on this instance.
https://lemmy.ca/post/1311411
TruckBC@lemmy.ca · 2 pts · 3y
I'm copying all links into a brand new incognito mode window for now.
avidamoeba@lemmy.ca · 0 pts · 3y
Introduce minimum password complexity if there's a config option for it and force admins to reset passwords.
TruckBC@lemmy.ca · 1 pts · 3y
There's no minimum complexity but I've enforced 2FA for all admins. One admin that did not respond has been temporarily removed precautionarily.
minnieo@kbin.social · 0 pts · 3y
thanks for your hard work, even though i am sure you're tired as hell. i think that person's idea about a minimum complexity requirement in addition to 2FA is a good idea, perhaps something like a complex password generator like LastPass or something, anything.
TruckBC@lemmy.ca · 4 pts · 3y
We can put it in place as a internal policy. I'm 99% confident all admins on Lemmy.ca are using complex password generators, that are hopefully not LastPass with their history of being hacked 😅
Edit: yeah I'm tired. It's like 3 hours post bed time. I'm supposed to be at work in just over 5 hours.
minnieo@kbin.social · 2 pts · 3y
shit that sucks. this happened at a bad time, i'm sorry. are their people besides you who are keeping an eye on this and maintaining it, for when you go off to work or when you need to sleep? cause everyone needs their sleep
frankyboi@lemmy.ca · 1 pts · 3y
for some reason I had to reset my password.
Thelsim@kbin.social · 1 pts · 3y
So, as an average, less-technical, Lemmy user (this is my backup for now).
What can or should I do to stay safe?
jherazob@kbin.social · 0 pts · 3y
Beehaw completely shut down as a response
Edit: Post by the Beehaw admins, gonna stay down until fixed
TruckBC@lemmy.ca · 1 pts · 3y
While I respect their decision, I believe that's a over-reaction at this point and we will not be doing that, yet.