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.
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