PSA: Lemmy.world was compromised! - eviltoast

Discussion from here: https://lemmy.ml/post/1895271

Relevance: Infosec.pub may wish to consider defederation temporarily.

Temporary fix in place, but instances remain vulnerable. Post: https://lemmy.world/post/1290412

  • UPDATE 2:58 UTC the injected code was removed from the main page, but cleanup efforts are still underway.
  • UPDATE 3:11 UTC situation appears to be under control, but browse with caution.
  • UPDATE 3:35 UTC main page exploited again! Website is unsafe.
  • UPDATE 4:01 UTC reports coming in that other instances are getting owned. One report of comments trying to inject JavaScript into the page.
  • UPDATE 4:13 UTC XSS vulnerability in page sidebar is reported relationship to the event is unknown.
  • UPDATE 7:17 UTC Root cause was identified a while ago.
  • SimplePhysics@sh.itjust.worksEnglish
    8·
    1 year ago

    Yep, redirects to very strange websites. I created this shitjustworks account because my main is on .world. This is very concerning.

  • solarzones@programming.devEnglish
    8·
    1 year ago

    I hope everything will be resolved quickly. Saw a post on kbin about it, and I was just about to login my .world account and see what’s up. ~ Waiting on updates…

    • henfredemars@infosec.pubOPEnglish
      18·
      1 year ago

      Tbf, I’m surprised this hasn’t happened already. The software is not mature and is suddenly being exposed to a huge group of people. There are lots of eyes on it that weren’t on the code before, and the big audience makes Lemmy a juicy target.

      Other instances should be vigilant in case Lemmy could have an exploit until we know for sure what happened.

  • faebudo@infosec.pubEnglish
    5·
    1 year ago

    According to one of the vuln posts a redirect and cookie stealing code was added as onload js (can even be seen in a screenshot).

    Together with the JWT that are valid for a year and non revokable (https://github.com/LemmyNet/lemmy/issues/3364) that means if you logged in or browsed an affected instance while logged in to it the attacker got your account and the only way to get it back is not in your hands but in the instance admins (they have to delete all sessions from the DB).

    • henfredemars@infosec.pubOPEnglish
      2·
      1 year ago

      Correct. We don’t know for sure what the initial injection was, but they did manage to inject and all the accounts will need their sessions purged maybe force password reset as well.

  • jerry@infosec.pubMEnglish
    1·
    1 year ago

    I’ve turned off federation and the ability to create new communities until a fix is released.