This version again includes a couple of security fixes. Thanks to the people who found and reported them!

The first one in particular requires manual action from instance admins. Lemmy’s default Nginx config uses $proxy_add_x_forwarded_for to set the X-Forwarded-For header, which does not override existing values. So clients can spoof the IP and bypass rate limits. The solution is to use $remote_addr instead. If you use Ansible this will be changed automatically during the upgrade, otherwise you will need to do it manually. If you dont use Nginx, ensure that any X-Forwarded-For headers sent by the client are overwritten.

The remaining security vulnerabilities are in the Lemmy code itself, and will be fixed simply by upgrading.

Security:

no comments (yet)

sorted by: hot top controversial new old
there doesn't seem to be anything here
5 comments in c/announcements@lemmy.ml view that post
[–] 5 points 5 months ago

This is the way.

  • source
  • [–] 2 points 5 months ago* (last edited 5 months ago) (3 children)

    It might be unrelated, but I would recommend caution before updating to this release as ml currently has severe federation problems.

  • source
  • hideshow 3 child comments