Re:Log4j: Between a rock and a hard place
by brabel on Sunday December 12, 2021 @01:56AM
(#29527697)
The log4j exploit was based on remote class loading, not serialization... though if your JVM protected you against remote class loading, it's indeed correct that one way to bypass that protection was by using a serialization attack.
This would certainly have broken a large number of software, but it's the right way to go. Whichever way you define the "compatibility promise", I think security overrides that.
At least it looks like Oracle is going this way[1], I just wish that it would have been sooner.
[1] https://inside.java/2019/11/07/whywehateserialization/