← Back to context Comment by aDyslecticCrow 6 hours ago Giving me log4j vibes. 3 comments aDyslecticCrow Reply Neikius 5 hours ago Much worse. Log4j was hard to exploit and worked only in specific condions. And it was bad. This is something else. aDyslecticCrow 3 hours ago 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. Lt_Riza_Hawkeye 4 hours ago log4j was indeed the last time the internet storm center went to threat level yellow (as it is today again)
Neikius 5 hours ago Much worse. Log4j was hard to exploit and worked only in specific condions. And it was bad. This is something else. aDyslecticCrow 3 hours ago 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.
aDyslecticCrow 3 hours ago 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.
Lt_Riza_Hawkeye 4 hours ago log4j was indeed the last time the internet storm center went to threat level yellow (as it is today again)
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.
log4j was indeed the last time the internet storm center went to threat level yellow (as it is today again)