I’m the administrator of kbin.life, a general purpose/tech orientated kbin instance.

  • 0 Posts
  • 577 Comments
Joined 3 years ago
cake
Cake day: June 29th, 2023

help-circle


  • However, my understanding is that this could be exploited only by authenticated users with permission to add new media. Not like that’s a risk to ignore, but it’s not like it could be exploited by anyone on the Internet.

    I wonder if that’s the reason for setting the default live TV management permission to false. Since that permission might well the the route to adding your own malicious m3u link for that second change.


  • Reverse proxy will let anyone connect to it. VPN, you can create keys/logins for your intended users only. Having said that, from what I could see, nothing in the security fixes were to do with authentication. I think (just from a cursory look), they could only be exploited, if at all from an authenticated user session.

    But personally, something like jellyfin where the number of people I want to be able to access it is very limited, stays behind a VPN. Better to limit your potential attack surface as much as you can.


  • This is kinda my thoughts too. I have a generally “OK” setup now. 7800X3D, 64GB DDR5-6400 (I think it is 6400 anyway), and a 3080. Should be fine for now. At least to wait and see if we’re:

    • Totally cooked and will eventually be forced to compute on the cloud
    • Things return to some level of normality as the AI hype bubble bursts and people start using it as a genuine tool and not the panacea for all of our problems that needs the insane level of investment it’s been given lately.

    Hell, if the bubble bursts hard enough there might be some cut price action, just like all those juicy cheap enterprise HDDs we could get during the covid times. Maybe wishful thinking though.

    Just remember who screwed you over if/when they come back to consumers, cap-in-hand.


  • From a cursory look at just the security commits. Looks like the following:

    • GHSA-j2hf-x4q5-47j3: Checks if a media shortcut is empty, and checks if it is remote and stores the remote protocol if so. Also prevent strm files (these are meant to contain links to a stream) from referencing local files. Indeed this might have been used to reference files jellyfin couldn’t usually see?
    • GHSA-8fw7-f233-ffr8: Seems to be similar, except for M3U file link validation and limiting allowed protocols. It also changes the default permissions for live TV management to false.
    • GHSA-v2jv-54xj-h76w: When creating a structure there should be a limit of 200 characters for a string which was not enforced.
    • GHSA-jh22-fw8w-2v9x: Not really completely sure here. They change regex to regexstr in a lot of places and it looks like some extra validation around choosing transcoding settings.

    I’m not really sure how serious any of these are, or how they could be exploited however. Well aside from the local file in stream files one.