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.

  • darkcalling@lemmygrad.ml
    link
    fedilink
    English
    arrow-up
    9
    ·
    edit-2
    1 year ago

    So the take-away so far is that lemmy.world including admin accounts may be compromised. XSS attacks are being used, perhaps in a targeted, perhaps generalized fashion to steal session cookies which is pretty bad as it allows the attacker to gain the login session of any victims. In the case of an admin they could do anything an admin could which is pretty bad as far as being able to steal user information, plant further malware, escalate the attack, etc.

    Do not visit lemmy.world, be wary of any and all links you click.

    Saw a claim on hexbear that the instance doing the attacks is zelensky dot zip which is definitely something though what I don’t know.

    You should be able to invalidate any active login sessions by changing your password.

  • ImOnADiet🇵🇸 (He/Him)@lemmygrad.ml
    link
    fedilink
    English
    arrow-up
    5
    ·
    1 year ago

    Wish I knew more about code, I don’t really understand what this means. I did see that blahaj and potentially beehaw have been hacked too, little worried about us

    • ☭ Chay [they/them] ☭@lemmygrad.ml
      link
      fedilink
      English
      arrow-up
      4
      ·
      edit-2
      1 year ago

      For the moment you can browse with Javascript disabled, though that will disable some functionality of the webpage, or if you have NoScript it stops XSS attacks mostly

          • sobuddywhoneedsyou@lemmygrad.ml
            link
            fedilink
            English
            arrow-up
            2
            ·
            1 year ago

            I saw on Hexbear that XSS affected them as well. Do you know how an instance gets targeted by it? The post (on shitjustworks) that I read about it seemed to be related to code execution in the sidebar. So I thought the only way to do this would be if an admin modified the sidebar. But seems like this is not the case from what I read on Hexbear.

        • ☭ Chay [they/them] ☭@lemmygrad.ml
          link
          fedilink
          English
          arrow-up
          2
          ·
          1 year ago

          I think it depends, I for one have no idea what other modifications the Lemmygrad team has done to their website, if it’s running stock Lemmy then it’s a chance it might be exploited. From what I’m reading in that thread, the whole Markdown parser doesn’t sanitize things, like this could get interpreted as valid code and run in the user’s browser. The attack on lemmy.world seems just to steal cookies in your browser, thus login credentials, or even more if your browser doesn’t separate cookies. For the moment I would suggest more vigilance when clicking unknown links and such

    • ☭ Chay [they/them] ☭@lemmygrad.ml
      link
      fedilink
      English
      arrow-up
      9
      ·
      1 year ago

      I’m not a programmer so disclaimer, from what I understand the HTML code in Lemmy’s sidebar is not “sanitized” so basically it’s not checked if it’s code or not, thus making it able to inject malicious code

  • darkcalling@lemmygrad.ml
    link
    fedilink
    English
    arrow-up
    3
    ·
    1 year ago

    Looks like it’s time to install noscript (you can set global allowed mode and it still mostly kills most xss attacks). Meanwhile here I am sitting on top of default deny javascript for unknown non-whitelisted websites and laughing at pitiful attacks that don’t even target browser zero-days.

  • Water Bowl Slime@lemmygrad.ml
    link
    fedilink
    English
    arrow-up
    2
    ·
    1 year ago

    Is this a default Lemmy thing? Cuz someone on that original thread said that an admin account was used to create this vulnerability. I really hope that’s the case because protecting against XSS attacks is like, JavaScript 101.