Re:Log4Shell update: second Log4j vulnerability published
by watwut on Wednesday December 15, 2021 @08:43AM
(#29565769)
You mean that they are adding log4j maven dependency where there was none?
[ Parent
| on HN ]
Re:Log4Shell update: second Log4j vulnerability published
by dboreham on Wednesday December 15, 2021 @09:45AM
(#29566596)
Reminds me of the advice to use two STOP statements in a Fortran program if you run it on a Cray. It's so fast that it could blow straight through the first one.
Re:Log4Shell update: second Log4j vulnerability published
by sporkland on Wednesday December 15, 2021 @11:01AM
(#29567819)
Yes
Re:Log4Shell update: second Log4j vulnerability published
by Hallucinaut on Wednesday December 15, 2021 @07:07PM
(#29573181)
Whilst that is ridiculous if they're bringing in a new dependency, if I squint I can see the thought process. Transitive dependencies are far harder to be certain about. It took a few seconds to scan our company's entire code base for log4j2.
But there's no easy way to verify that none of them might depend on, say, Spring Boot Web Starter, which brings in umpteen other dependencies.
Sure, you can resolve dependencies in each project and check at the individual level that the resolved dependencies for runtime don't include log4j2 but it's much more onerous. And you can take away that risk by declaring it in your parent POM so the version is fixed, regardless of what transitive deps may use.
Of course, I would always say if this what was being done, using the dependencyManagement would be a better solution. But a lot of this work will be under duress and in my experience the majority of people using systems like Maven don't really understand it.
Re:Log4Shell update: second Log4j vulnerability published
by john-shaffer on Thursday December 16, 2021 @04:05AM
(#29576415)
I just added a test case that importing org.apache.logging.log4j.core.lookup.JndiLookup throws a ClassNotFoundException. Any log4j2 class would work too.