Drawing attention on this instance so Admins are aware and can address the propagating exploit.

EDIT: Found more info about the patch.

A more thorough recap of the issue.

GitHub PR fixing the bug: https://github.com/LemmyNet/lemmy-ui/pull/1897/files

If your instance has custom emojis defined, this is exploitable everywhere Markdown is available. It is NOT restricted to admins, but can be used to steal an admin’s JWT, which then lets the attacker get into that admin’s account which can then spread the exploit further by putting it somewhere where it’s rendered on every single page and then deface the site.

If your instance doesn’t have any custom emojis, you are safe, the exploit requires custom emojis to trigger the bad code branch.

You are viewing a single thread.
View all comments View context
7 points

This comment further underlines to me that you have absolutely no idea what the fuck you’re talking about.

You’re out of your element, Donny.

permalink
report
parent
reply
-6 points

And you’re aggressively confidently wrong. Evidence by the fact that you give literally zero reasoning.

The fact a bug like this can happen is clear and obvious evidence for how these things can happen, and this was just stupidity, not targeted malice.

permalink
report
parent
reply
6 points

Lmao go touch grass my guy.

It’s not a backdoor. It wasn’t malicious. Yes, some major contributors are tankies, but that doesn’t really matter. That’s the beauty of OSS: everyone can see the code, which means everyone can spot sketchy shit - either malicious or completely accidental - and fix it. The fact that a patch was published in a matter of literally hours is confirmation of this.

If this was a malicious exploit, it’d have been obscured far more, it would likely encompass more than a handful of insecure data-handling statements, and we’d have seen a LOT more instances getting popped.

permalink
report
parent
reply
-3 points
*

It’s not a backdoor. It wasn’t malicious

Read my comment again. I literally said this wasn’t. I said this is experience that it could be easily done in the future.

everyone can see the code, which means everyone can spot sketchy shit - either malicious or completely accidental - and fix it.

Didn’t help in this case. Open Source doesn’t fix malicious contributions, and when the project owners are the malicious source your have no safeguards. Trust is still essential.

If this was a malicious exploit, it’d have been obscured far more,

Ex-fucking-xactly

permalink
report
parent
reply

Programming.dev Meta

!meta@programming.dev

Create post

Welcome to the Programming.Dev meta community!

This is a community for discussing things about programming.dev itself. Things like announcements, site help posts, site questions, etc. are all welcome here.

Links

Credits

  • Icon base by Lorc under CC BY 3.0 with modifications to add a gradient

Community stats

  • 195

    Monthly active users

  • 224

    Posts

  • 2.5K

    Comments