Hacker News Reader

Much worse. Log4j was hard to exploit and worked only in specific condions. And it was bad. This is something else.

But log4j was also extremely painful to patch, since every application bundled the vulnerabile dependency.

This is a storm, but hopefully quick to blow over with a panic frency of apt update or docker build.

The immediate exposure is faar worse here though, since its by design internet facing code.

A college enabled logging on their server as soon as they saw the news, and got dozens of attempted requests against index.php.

Turning on logging and seeing bots for the first time does not equate to novel or specifically crafted attacks. Web services get hit regularly by bots. A few dozen an hour is almost nothing for a public facing web service.

Yes, but seeing a few dozen of a new type show up within less of a day of the exploit being public is pretty mad. The usual probing is nothing special.

Reply on news.ycombinator.com