Servers have used resource pack requests to track players, and some have used them to find out which client a player is on. This goes further than the known Translation Exploit, which most clients have patched.
LiquidBounce, Meteor and Wurst now ship with a built-in fingerprint spoofer, so please update. If you stay on an old version, servers can track you across accounts and IPs. Older LiquidBounce builds could also be detected.
The security risk
Servers can point the resource pack URL anywhere, and your game will try to download it over HTTP or HTTPS. So a server can make your PC send web requests, including to localhost and your home network. In theory that could hit a vulnerable router page, local services, or internal websites that should never be reachable from outside.
This blog post explains how resource pack URLs can reach localhost, and how a resource pack crafted for each user can create a fingerprint that follows you across IPs and accounts.
The fixes
LiquidBounce's fingerprint spoofer uses a separate data folder for each account, so server resource packs can no longer be used to detect you. Meteor and Wurst made similar fixes.
LiquidBounce also runs a local HTTP server, and a resource pack request could check whether it answered. We fixed that by adding client authentication to the Interop Server, so not even local software can access it now.
Fixes for other clients
If you play on the vanilla client or another Fabric client without these fixes, there is a Fabric mod called ExploitPreventer. It patches all known client-side Minecraft exploits around resource pack requests: it blocks insecure requests to local addresses, stops translation key checks, and keeps a separate resource pack cache per account so you can't be fingerprinted.
From Minecraft 1.21.10 on, LiquidLauncher includes ExploitPreventer by default.
Links
- Blog Post: alaggydev.github.io/posts/cytooxien
- LiquidBounce Issue: #7007
- LiquidBounce Fixes: #7009, #7064, #7161
- Meteor Fix: e241e7d
- Wurst Fix: #1226
