Re:Log4j: The pain just keeps going
by stonemetal12 on Monday July 25, 2022 @11:33AM
(#32225809)
The issue is like SQL Injection. Much like SQL Injection protection the logger needs to separate "active" strings vs attacker controlled "data" strings. It is pretty easy to design boring Java types that solve the issue. The only problem is they didn't. Unless this effects system somehow forces them to not do something dumb, we will end up with a logger that has effects set to "does everything under the sun", and a similar bug.
[ Parent
| on HN ]
There are no comments on this comment yet.