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.
[ Parent
| on HN ]
There are no comments on this comment yet.