socphoenix

Posting this for visibility: cross-posted from: https://lemmy.world/post/1299831

Hi all,

If you're just now signing in for the first time in 12+ hours, you may just now be finding out that Lemmy World and other instances where hijacked. The hijackers had the full abilities of hijacked user, mod, and admin accounts. At this time, I am only aware of instance defacing and URL redirections to have been done by the hijackers.

If you were not forced to sign back in this morning, contact your instance admin to verify mitigations were completed on your instance.

How?

This occurred due to an XSS attack in the recently added custom emojis. Instance admins should follow the issue tracker on the LemmyNet GitHub, as well as the Matrix Chat. Post-Incident Activity is still on-going.

Currently, it is likely that just your session cookie was stolen, with instance admins being targeted specifically by checking for navAdmin, an HTML element only instance admins had. I do not believe this to affect users across instances, but I have yet to confirm this.

What happens next?

As I am not the developers or affected instance admins, I cannot make any guarantees. However, here is what you'll likely see:

1. Post Incident investigation continues. This will include inspecting code, posts, websites, and more used by the hijackers. An official incident writeup may occur. You should expect the following from that report:

• Exactly what happened, when.
• The incident response that occurred from instance admins
• Information that might have helped resolve the issue sooner
• Any issues that prevented successful resolution
• What should have been done differently by admins
• What should be improved by developers
• What can be used to identify the next attack
• What tools are needed to identify that information

2. A CVE is created. This is an official alert of the issue, and notifies security experts (and enthusiasts), even those not using lemmy, about the issue.

3. A code security audit is done. This will likely just be casual reviews by technical lemmy users. However, I will be reaching out to the Mozilla Foundation and Cure53 as they recently did an audit of Mastodon. If there is interest in an external audit of lemmy and the costs are affordable, I'll look into crowdfunding this cost.

I'm trying to set up rules so I can access a few different containers from zerotier. I've already set up an ssh-x11 container and the passthrough is working fine with:

rdr on $ext_zero proto tcp from any to $ext_zero port 8000 -> 10.1.1.3 port 22

where $ext_zero is the variable for the zerotier bridge.

However, trying to stream music with jellyfin with:

rdr on $ext_zero proto tcp from any to $ext_zero port 8096 -> 10.1.1.6 port 8096

I get consistent connection refused messages.

The full pf.conf for redirections: Code:

table <jails> persist
nat on $ext_if from <jails> to any -> ($ext_if:0)
rdr-anchor "rdr/*"
rdr on $ext_zero proto tcp from any to $ext_zero port 8000 -> 10.1.1.3 port 22
rdr on $ext_zero proto tcp from any to $ext_zero port 8096 -> 10.1.1.6 port 8096
rdr on $ext_zero proto tcp from any to $ext_zero port 8920 -> 10.1.1.6 port 8920
rdr on $ext_zero proto udp from any to $ext_zero port 1900 -> 10.1.1.6 port 1900
rdr on $ext_zero proto udp from any to $ext_zero port 7359 -> 10.1.1.6 port 7359

The system is FreeBSD, the jails are roughly equivalent to a docker compose install.

Jellyfin is set to accept remote connections, with the whitelist left blank as per their instructions to allow all addresses. Why will ssh connect but not jellyfin?>>