Swear this is the same guy that did the trending community spam a few days ago, he was angry about being banned for squatting on known subreddit names here on Lemmy, even the compromised admin account said something about it in her comments before this happened π€¦ββοΈ
this post was submitted on 10 Jul 2023
321 points (98.5% liked)
Android
17730 readers
55 users here now
The new home of /r/Android on Lemmy and the Fediverse!
Android news, reviews, tips, and discussions about rooting, tutorials, and apps.
πUniversal Link: [email protected]
π‘Content Philosophy:
Content which benefits the community (news, rumours, and discussions) is generally allowed and is valued over content which benefits only the individual (technical questions, help buying/selling, rants, self-promotion, etc.) which will be removed if it's in violation of the rules.
Support, technical, or app related questions belong in: [email protected]
For fresh communities, lemmy apps, and instance updates: [email protected]
π¬Matrix Chat
π°Our communities below
Rules
-
Stay on topic: All posts should be related to the Android OS or ecosystem.
-
No support questions, recommendation requests, rants, or bug reports: Posts must benefit the community rather than the individual. Please post to [email protected].
-
Describe images/videos, no memes: Please include a text description when sharing images or videos. Post memes to [email protected].
-
No self-promotion spam: Active community members can post their apps if they answer any questions in the comments. Please do not post links to your own website, YouTube, blog content, or communities.
-
No reposts or rehosted content: Share only the original source of an article, unless it's not available in English or requires logging in (like Twitter). Avoid reposting the same topic from other sources.
-
No editorializing titles: You can add the author or website's name if helpful, but keep article titles unchanged.
-
No piracy or unverified APKs: Do not share links or direct people to pirated content or unverified APKs, which may contain malicious code.
-
No unauthorized polls, bots, or giveaways: Do not create polls, use bots, or organize giveaways without first contacting mods for approval.
-
No offensive or low-effort content: Don't post offensive or unhelpful content. Keep it civil and friendly!
-
No affiliate links: Posting affiliate links is not allowed.
Quick Links
Our Communities
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
Lemmy App List
Chat and More
founded 1 year ago
MODERATORS
Time to move from banning to contacting authorities then.... spam is one thing. This is criminal.
Wait, was that the one that had a community list well into the twenties? Or was that someone else? I don't think all that stuff reached me, but I did hear about a wannabe powermod like a week and a half ago. Much good that does anyone in a defederated system.
His username at the time was βLMAOβ and I think soβ¦ he did it again on another Lemmy instance but used a different username that time as well π
Deeply unfortunate that something like this could happen, you always hope that code injection vulnerabilities are found before someone is hacked. With that in mind, this shows the importance of two security principles: always parse and clean user input and don't click links (including images) before checking where they are going to send you.
This used an onLoad which isn't generally shown when you hover over a link in a browser. Most people, even devs, aren't going to jump on the console to check every link.
NoScript would probably have helped though.
What kind of terrible markdown editor allows adding onload scripts to images though.. it's insane.
Script kiddies. insert eyeroll emoji here
Here take this: π
Hey everyone, this exploit was present in the custom emoji feature of Lemmy. Because lemdro.id does not use custom emojis, we are not vulnerable at this time.
Some information I have posted to Lemmy.World:
I am not a super code-literate person so bare with me on this... But. Still please becareful. There appears to be a vulnerability.
Users are posting images like the following:
And inside hidden is JavaScript code that when executed can take cookie information and send it to a URL address.
Among other things. At this time if you see an image please click the icon circled before clicking the link. DO NOT CLICK THE IMAGE. If you see anything suspicious, please report it immediately. It is better a false report than a missed one.
I have seen multiple posts by these people during the attack. It is most certainly related to JS.
If it's onload then simply viewing the image runs that script. Yikes.
That's even worse, if Lemmy has a vulnerability like that it needs to get fixed ASAP... Also if that code actually works, I am going to have to secure my account.
I'd wager you're likely fine if you're using a mobile app when the affected image loads. Also, it appears they're stealing auth tokens.. not passwords or anything. At worst they could impersonate you until your token expires.. but you're not a high value target unless you're an admin of an instance.
I used Firefox... So I definitely reset my password. Thing is I do not see an option for Lemmy where you can "sign out everywhere" which is the counter to Auth token stealing.
So I had to change it so that the Auth token would expire. Whilst I am not an admin I won't take the chance. It could compromise other users and I do not want to take that risk.
Apparently the fix for the vulnerability signs everyone out.
the thing is right now lemmy by defaultNEVER expires the tokens... oops. Right now servers are manually expiring all their user's tokens by changing the secret in the database because of this attack.
Oops indeed. Lemmy needs a security audit π¬
load more comments
(14 replies)
Deeply unfortunate that something like this could happen, you always hope that code injection vulnerabilities are found before someone is hacked. With that in mind, this shows the importance of two security principles: always parse and clean user input and don't click links (including images) before checking where they are going to send you.
Itβs worse than that. Until Lemmy is more mature, I would reccomend using the lite version of Lemmy, the JS-free version, for sake of client side security. Alternatively, or as an added point of security, the front-ends themselves should implement more sanitazion themselves. Iβm willing to spend some free time vulnerability testing, but I would need a dedicated sand-box for that.
The ansible method of setting up a lemmy instance generally "just works". I set one up for federation tests with kbin recently.
Did this result in Lemmy.world being defederated from Lemdro.id?
Lemmy.world is back up and the hack is over, but when I view [email protected] using my lemmy.world account I can't see anything.
EDIT: In case anyone else is having this problem, the issue was my language settings. Despite having βUndeterminedβ set as a language, that was the problem - I clicked the little βXβ to unselect all languages and then saved, and now itβs working again.
I have not de-federated other instances simply because lemdro.id is not vulnerable to this particular exploit
When I wanted to do some lemmying earlier, the LemmyWorld logo said 'Israel', and when I put my cursor over it, it said 'N***a Style. Then when I clicked the logo (stupid me, no doubt), it redirected me to a pic of some dude with a cigar, with the caption (iirc) "I r * pe kids in the woods". I did a virus scan which came up clear. Dunno what else to do when shit like that happens, as I am not the brightest bulb in the chandelier.
I have not seen any notice as to how either users or admins should mitigate the problem so far. Obviously, admins should update once a new release is out, but beyond that...
From an end-user standpoint, I would guess -- I have not looked at the code and have not been working on the security hole -- the following:
-
This basically allows the attacker to masquerade as a currently-logged-in user who has viewed their link.
-
Viewing content on a lemmy server while logged in as an admin right now is probably a particularly bad idea.
-
I don't know what the full impact is for a regular user account, but it's probably possible for at minimum posts to be deleted, and posts to be made as someone. In kbin, my account shows my email address, so if lemmy does the same, it would be possible to link an email account used for registration with a username. If you used a throw-away email account that is publicly-accessible -- as I did -- that could allow for full account compromise.
-
Viewing content while not logged in is probably safe -- maybe they can make Javascript run from a link, but without you being logged in, there isn't anything interesting that the attacker can do. If I were going to be viewing content on lemmy servers right now, and okay with being limited to lurking, I might do that for a few days until the issue is resolved and lemmy servers update.
-
I don't know if kbin is vulnerable. It didn't accept the URL given in the bug as an example of a malicious URL when I tested submitting one, but it's possible that it trusts URLs coming from federated servers, which I did not check.
https://github.com/LemmyNet/lemmy-ui/issues/1895#issuecomment-1628270766
As for a user, I'd avoid using any Lemmy instances from the browser until they get updated.
beehaw isn't down, just very slow, which is it's normal state of being if we're being honest
I don't see any weird content, but I couldn't log in. There's a notification at the bottom that says "logged in" but I'm still blinded by light mode.
view more: next βΊ