If you are running Windows [...]
and
from June 2015 until the present, affecting v3.2.1 through v5.0.0 inclusive. The behaviour does not appear to be replicated for other OS variants
1. Posts must be related to the discussion of digital piracy
2. Don't request invites, trade, sell, or self-promote
3. Don't request or link to specific pirated titles, including DMs
4. Don't submit low-quality posts, be entitled, or harass others
📜 c/Piracy Wiki (Community Edition):
💰 Please help cover server costs.
Ko-fi | Liberapay |
If you are running Windows [...]
and
from June 2015 until the present, affecting v3.2.1 through v5.0.0 inclusive. The behaviour does not appear to be replicated for other OS variants
Will I be OK updating from the Debian repo?
Is there something we should do in the meantime? I’m not the most savvy individual when it comes to tech on this level.
Not really. This requires a sophisticated attacker. I’d suggest updating soon but I doubt most people are at risk. As always verify downloads before running them and check where you should be getting updates and if you’re sent to a sketchy file hosted try to find updates from the official website instead.
The biggest risk is MTM interception and replacement of the python executable if you try and use the search tool for the first time. I suppose avoid doing that until you update the client from their website.
Thanks. This makes it a lot clearer.
Just update it to the latest
Ah. So this has already been addressed? Okay, thanks for responding.
Mitigations
Just use another torrent client. Deluge and Transmission etc do not have this vulnerability.
Was wondering what the takeaway is here. I updated to 5.0.1. Does that fix all these? If not, guess I'll try a different torrent client.
The first patched release is version 5.0.1, released 2 days ago.
Containerization helps, but best to patch asap.