Log4j Critical RCE

Sky-Knight

Well-Known Member
Reaction score
5,513
Location
Arizona

How critical? Well, all you have to do is send a POST request against an impacted system and it'll happily run whatever you tell it to.


ConnectWise and N-Able have been confirmed vulnerable. Heck, Minecraft instances are vulnerable, note this is both server AND client. Though the latter is difficult to exploit unless you're sitting at the machine in question. https://help.minecraft.net/hc/en-us...urity-Vulnerability-in-Minecraft-Java-Edition

Untangle seems to be safe, as of yet because the only instance of log4j we've found on the platform is actually too old to be used in this exploit. That and you need root access to the platform to run the payload at present. But if you're using Untangle please double check your https admin access rules and close that crap to untrusted IP addresses just in case. (Note, you should be doing this already!)

It's bad enough that Cloudflare is considering giving even free customers projection against this mess if you're using their WAF.

Here have a Twitter feed full of people testing this against all sorts of crap, smart devices, everything you can imagine. Java is everywhere of course.


Ladies and Gentlemen... START YOUR PATCHING! :D

A general mitigation can be done on Windows by this:

If you're using a Unifi Controller on a Windows platform somewhere... this is a good idea to get that environment variable out. I'm currently testing use of this variable on all platforms.
 
Unifi has released Network 6.5.54 and Protect 1.20.1 to patch Log4j vulnerabilities. Hostifi customers already have this, everyone else... start your patching!

Omada is confirmed vulnerable too, but no patch is available from TP-Link yet.
 
Untangle uses log4j 1.2.16 which is a patched older version available via the Debian repos and no vulnerable to the current exploit.
 
Back
Top