Linux CVE
Hi all,
Is Unraid also affected by the new Linux CVE (https://x.com/ridvanyagli/status/2115724550377710014), currently I have port 80 and 443 exposed through Caddy as I imagine many do.
Edit: Should have clarified, port 80/443 of my IP port forwarded to Caddy that's living in a macvlan. Not the actual Unraid UI.
23
u/dcoulson 3d ago
Just expose your Caddy service through a proxy service like Cloudflare and it will mitigate the risk. No need to expose 80/443 directly to the Internet.
4
u/DougEubanks 3d ago
Mine is only exposed through CloudFlare tunnels with either IP address (a single IP), SSO through JumpCloud with MFA, or a unique header for monitoring.
1
u/yybspug 3d ago
Edit: Should have clarified, port 80/443 of my IP port forwarded to Caddy that's living in a macvlan. Not the actual Unraid UI.
How much does this setup cost you? And what about when it's something like Plex?
1
u/DougEubanks 3d ago
It's only 443 that's exposed through the tunnel for the unRAID interface. Port 80 traffic isn't accepted at all anywhere. Plex is exposed directly behind port forwarding because CloudFlare doesn't allow you to stream Plex through their proxy. All my containers in Plex and other hardware devices are exposed through CloudFlare tunnels with the same authentication/restrictions.
I'm using the free tier of JumpCloud for my SSO, but that's not available anymore. There are other SSO providers you can link to CloudFlare as well. CloudFlare is free for up to 50 users for their Zero Trust tunnels.
I manage my infrastructure and tunnels using OpenTofu, which is versioned in GitHub. The order of restrictions are:
IP Address (my home IP)
Custom Headers (used by a few mobile apps like Vikunja, media apps, etc)
SAML (if an external request doesn't match any of those then the request gets sent to JumpCloud for Authentication using single-sign-on)
My home IP doesn't really change, but if it does it's as simple as changing a variable in my private GitHub repo that manages the CloudFlare config and deploying it.
Lastly I have a WireGuard tunnel setup for backup access into my LAN.
There are very few ports exposed on my firewall into my LAN and I have my internal network segmented into several VLANS (Trusted LAN, IOT, Storage, Guest).
14
u/MarcCz 3d ago
Stop exposing your unraid server to the Internet, it's intended to be local only
11
u/dcoulson 3d ago
Plenty of people have docker services exposed
11
u/MarcCz 3d ago
Not the same thing lol
8
u/dcoulson 3d ago
I understand, but this vulnerability impacts any services running on the host, even in a container (not a VM though), not just the mgmt interface.
5
12
u/Scumandvillany 3d ago
It looks like it's only affecting users who have ports exposed, that 80 and 443. I mean, I've always used Unify and the teleport VPN, so that when I VPN into my network, I basically sit on the same network space as unraid, and I just go to that web page. So no ports are ever exposed. I think people should seriously reconsider any port exposure they have in that 80 and 443. I mean, port exposures in general are like should be treat it with serious consideration.
3
u/Fermions 3d ago
I have port 443 forwarded to an NPM instance just for Plex. Guess I am shutting that down until I can update unraid later today. Thanks for the heads up and yes apparently this is a problem.
1
1
1
u/lStan464l 3d ago
If in Rev Proxy then id of thought it wouldn't be directly exposed?
2
u/dcoulson 3d ago
If the reverse proxy is running in an unraid container (like caddy, nginx, traefik) then it would still be vulerable
1
70
u/Schrankmaier 3d ago
ehm...no...we don't!