Since the client is proprietary, it is also not possible to properly react to or even stop future issues.

While the initial vulnerability primarily related to users with WebUI enabled and was not necessarily a vulnerability in μTorrent versions itself, it still served to highlight the fact that these older versions are outdated legacy code surrounded by a whole lot more legacy code. Since the vast majority of μTorrent users are on 2.2.1 or below, we will put a special focus on addressing older versions. There are two primary reasons we would like to outline below. Once this happens, the tracker will no longer accept requests from μTorrent clients, meaning that anyone using μTorrent is no longer able to use our torrents. A more detailed explanationĪs mentioned above, we plan to remove μTorrent from our client whitelist. We will be removing μTorrent from the client whitelist.Īnyone using μTorrent should switch to a different client over the next 6 months. After careful deliberations, we have made a decision:

This incident made it clear that outdated, closed-source clients like μTorrent are a security vulnerability that can impact not just people that use them, but also peers connected to them. We reinstated the client again afterwards when the vulnerability was revealed to be somewhat limited in scope, however, this was ever only meant to be temporary while we thought about a better path forward. Here's the post: Removing μTorrent from WhitelistĪpproximately 4 years ago, we initially removed μTorrent from our whitelist after the discovery of a vulnerability that allowed remote access, specifically for users that had WebUI enabled.

Old version of utorrent 2.2.1 for mac