You've probably heard about the Log4j attack—a vulnerability in the Apache Log4j 2 utility that allowed remote code execution (RCE), enabling attackers to execute arbitrary code on servers or other computers running an affected version of Log4j without needing any special authorization.
Share this post
Years after Log4j, what has changed?
Share this post
You've probably heard about the Log4j attack—a vulnerability in the Apache Log4j 2 utility that allowed remote code execution (RCE), enabling attackers to execute arbitrary code on servers or other computers running an affected version of Log4j without needing any special authorization.