As you might have heard several Lemmy instances have been attacked via a security vulnerability in the browser frontend related to custom emoji.

While SLRPNK was vulnerable to it, we seem to have not been actively targeted and I took the instance down as a precaution as soon as I learned about it.

I have applied all the currently known mitigations, which means that everyone got logged out of their account and needs to log back in manually.

As of writing this the API is working again and can be used with apps like Jerboa safely.

I am still contemplating if I want to re-enable the web frontend now or wait for a release that fixes the issues found.

Edit: the main issue was fixed and I restarted the web ui with it.

  • h3x@kbin.social
    0·
    2 years ago

    What’s your stance on users proactively finding and reporting possible vulnerabilities in kbin? It’d be great to have a bug bounty like model where white hats could test the app and report their findings to devs? Without the bounty part of course - this is a community effort after all.