News for hackers. Stuff that matters.
Re:Log4Shell update: second Log4j vulnerability published by Bluecobra on Tuesday December 14, 2021 @11:53PM (#29562255)
Now that is really clever. One of affected products I use is Juniper Space to monitor our network infrastructure (which uses OpenNMS). Juniper’s only workaround currently is to completely disable OpenNMS, thereby leaving us in the dark for monitoring. This would be an excellent workaround, though I have been unable to trigger any PoC code.
Re:Log4Shell update: second Log4j vulnerability published by freeqaz on Wednesday December 15, 2021 @12:52AM (#29562571)
Shoot me an email -- we are also offering this "live patching" idea as a service now (due to Log4Shell). free at lunasec daht io (or use the contact form on https://www.lunasec.io instead)

It's just a Java dependency that you add to your classpath. Under the hood, it regularly checks for patches, and then live updates to patch a vulnerability (like Log4Shell) without you ever needing to do anything. The Open Source release is still a WIP (the Golang one here is a subset) but we have some paying customers for it already. Log4Shell has really accelerated the number of people asking us for this though!

Edit: We're offering basically this[0] project but commercially supported and, when the next Log4Shell happens, it'll patch your usage automatically.

0: https://github.com/corretto/hotpatch-for-apache-log4j2

Re:Log4Shell update: second Log4j vulnerability published by eptcyka on Wednesday December 15, 2021 @07:52AM (#29565280)
One has to be very trusting of you to give you an RCE to plug security holes
Re:Log4Shell update: second Log4j vulnerability published by hutzlibu on Wednesday December 15, 2021 @08:16AM (#29565469)
If you do not trust them, you probably should not use their code, without deeper examination, either.
Re:Log4Shell update: second Log4j vulnerability published by yccs27 on Thursday December 16, 2021 @07:15AM (#29577416)
The bigger problem is: You not only have to trust their good intentions now, but you also need to be able to trust them in the future, as long as the script is active. Additionally, you have to trust/hope that the patch security is absolutely waterproof and does not give RCE to attackers.
Re:Log4Shell update: second Log4j vulnerability published by xorcist on Wednesday December 15, 2021 @04:39AM (#29563780)
It is likely trivial to remove the jndi related classes from the package. That's what I did for similar network related third party software and so far without any trouble at all.