le_throoshCVE: Possible Organization/Secret Compromise from dangerous CI implementation
To clarify: This is about a possible supply chain attack. The possibility of it. Not about unsafe code in the app or anywhere else. It means that an attacker could have gained access to the ios repo and possibly any other repo. It is fixed now.
I imagine that hostile commits would have been caught by now, as would compromised releases. But the main issue for me is that we are pretty much left in the dark about this. Maybe the team checked everything well and came to the conclusion that this was nothing worry about and was catched before it could do any harm. Which is the most probable scenario I think. Still leaves a bit of a sour taste.
renegadesporkEveryone might want to freeze your Jellyfin versions until this gets sorted. As far as we know, nothing has been hijacked, but safer sit on your local copies for now.
Hasn’t it already been patched? https://github.com/jellyfin/jellyfin-ios/security/advisories/GHSA-7qhm-2m45-7fmh
Patches
CI workflows have been modified in all affected repositories, and secrets have been rotated.
slacktoidThis doesn’t affect the code or jellyfin. Its a problem with how github does CI that needs to be fixed.
I know. My comment stands. Though apparently it was already patched.
noodle@renegadespork @le_throosh
"Note: This is not a code vulnerability, but a vulnerability in the GitHub Actions workflows. No new version is required for this GHSA and end users do not need to take any actions."
Edit: This is just for context to save others looking up the CVE. 'wait and see' makes sense, particularly when a major update is potentially in the near future.
I know. My comment stands. Though apparently it was already patched.
I think its our local copies that might have issues if anything. If there is a threat at all, it would affect releases prior to the cve release not since then. Or yeah, if a possible attacker had gained access they may still have it, but its unlikely that would not have been caught.