This is only effective in 1.17 and above. The first was to introduce a command line argument to prevent the exploit from happening.

Mojang have already released a fix for the issue.ĪTLauncher has released 2 updates to also address this issue. For servers, you will need to recreate them to get the latest versions downloaded and applied.Īs we've always mentioned, you should also make sure you're using the latest Fabric/Forge version where possible.Īs you may or may not be aware, there was recently a security vulnerability exposed within Minecraft through the Log4J library that is included and used by Minecraft versions 1.7 and later. These libraries will automatically download and install themselves the next time you launch your instances, there's nothing you need to do. While the patches that Mojang applied to their own launcher, and were applied in our previous launcher updates will fix the issue, these fixes provide a complete fix to the issue and leave no doubt that there are any more issues going forward (at least for the issues that we know of today). Minecraft 1.12 and onwards uses an updated version of Log4J with the vulnerabilities fixed (version 2.16.0) Minecraft 1.7 to 1.11.2 now uses a patched version of Log4J (version 2.0-beta-9-fixed)

Further update on security vulnerability in MinecraftĪs a further news item on from the previous one around the Log4J exploit in Minecraft.ĪTLauncher has just released version 3.4.10.11 which fully patches all Log4J versions for all instances which include the Log4J library as follows:

Twitch minecraft jar launcher