While I was asleep, apparently the site was hacked. Luckily, (big) part of the lemmy.world team is in US, and some early birds in EU also helped mitigate this.

As I am told, this was the issue:

  • There is an vulnerability which was exploited
  • Several people had their JWT cookies leaked, including at least one admin
  • Attackers started changing site settings and posting fake announcements etc

Our mitigations:

  • We removed the vulnerability
  • Deleted all comments and private messages that contained the exploit
  • Rotated JWT secret which invalidated all existing cookies

The vulnerability will be fixed by the Lemmy devs.

Details of the vulnerability are here

Many thanks for all that helped, and sorry for any inconvenience caused!

Update While we believe the admins accounts were what they were after, it could be that other users accounts were compromised. Your cookie could have been ‘stolen’ and the hacker could have had access to your account, creating posts and comments under your name, and accessing/changing your settings (which shows your e-mail).

For this, you would have had to be using lemmy.world at that time, and load a page that had the vulnerability in it.

  • pazukaza@lemmy.ml
    2·
    1 year ago

    If by location you mean IP address, the XSS script could also send the IP address of the user to the attacker. Then the attacker could do write operations spoofing that IP. They wouldn’t get a response but the write operation would be done anyways.

    Maybe doing a 3 way handshake before every administrative action to ensure the IP wasn’t spoofed? Idk, I’m not a security person.

    1. User sends IP and JWT + administrative action. I mean, IP is extracted from src addr, not sent.

    2. Server saves the command in a cache with a TTL of 10 seconds. Then sends a randomly generated string to the user. The random string is sent in A HTTP-only same-site cookie to avoid it being read by JS scripts or being sent to external domains.

    3. The user sends it’s JWT + randomly generated string cookie back to the server. The server checks the cache. If an action is found, it is executed.

    Edit: actually, after thinking about it. If the XSS is not sending the JWT to a remote location but running the attack directly in the victim’s browser, there’s nothing that can be done. XSS is fucked up.