News for hackers. Stuff that matters.
Re:Log4j: Between a rock and a hard place by Aeolun on Saturday December 11, 2021 @07:35PM (#29525792)
> There are going to be "OSS fires" more or less constantly so "some major OSS project has a bad vuln" is not the sort of thing that gets a CTO at a company like Google or Facebook out of bed.

If all your IT projects have an RCE vulnerability that’s relatively easy to exploit, that should keep you up at night.

Re:Log4j: Between a rock and a hard place by UncleMeat on Saturday December 11, 2021 @07:39PM (#29525835)
The RCE existed prior to this disclosure. If I can't sleep today, why should I have been able to sleep a week ago? The dirty secret is that an absolutely enormous amount of code is vulnerable and that the solution to software security is not "fix RCEs as they are discovered as fast as possible." If having RCEs keeps you up at night, then I don't believe that there is a single engineer at almost any company in the world that interfaces with the internet that should be able to sleep.

The actual solutions here are at a more abstract layer than individual vulns.

Re:Log4j: Between a rock and a hard place by cesarb on Saturday December 11, 2021 @08:33PM (#29526197)
> The RCE existed prior to this disclosure. If I can't sleep today, why should I have been able to sleep a week ago?

A week ago, this vulnerability might have been known at most to a few three-letter agencies. Today, every two-bit script kiddie will be trying to exploit it. It's not hard to see how the situation has changed.

Re:Log4j: Between a rock and a hard place by Aeolun on Saturday December 11, 2021 @07:41PM (#29525854)
No, the fact of having these vulnerabilities is not a problem (I mean, obviously, but at the level you describe). The problem is having them be known to the world. Especially with a level of publicity like this.