Re:Log4Shell update: second Log4j vulnerability published
by teruakohatu on Tuesday December 14, 2021 @11:18PM
(#29562037)
How does the hot patch work?
[ Parent
| on HN ]
Re:Log4Shell update: second Log4j vulnerability published
by freeqaz on Tuesday December 14, 2021 @11:25PM
(#29562079)
It uses the Log4Shell exploit to load some Java bytecode (read through this[0] blog post for context on Log4Shell).
Then, once it loads that code, it scans the memory of the system and rewrites the various log4j classes that are loaded in memory. The code for that is this[1] Java file.
There is a good talk on JNDI exploits in that[0] blog post if you want more details. :)
0: https://www.lunasec.io/docs/blog/log4j-zero-day/#how-the-exp...
1: https://github.com/lunasec-io/lunasec/blob/master/tools/log4...
Re:Log4Shell update: second Log4j vulnerability published
by blondin on Tuesday December 14, 2021 @11:47PM
(#29562219)
uses the exploit to mitigate the exploit. brilliant!
Re:Log4Shell update: second Log4j vulnerability published
by avodonosov on Wednesday December 15, 2021 @09:15AM
(#29566203)
More precisely, it does not rewrite classes, but just changes log4j configuration programmatically.
Re:Log4Shell update: second Log4j vulnerability published
by indigodaddy on Wednesday December 15, 2021 @02:24AM
(#29563013)
Interesting.. kind of like a vaccine!