News for hackers. Stuff that matters.
Re:Log4j: Between a rock and a hard place by dogma1138 on Saturday December 11, 2021 @06:35PM (#29525367)
TBH it’s also quite mind boggling that this level of an RCE was used to hack Minecraft servers of all things.

I wonder if this wasn’t intended for something bigger and they just got caught when testing this out in the field.

Re:Log4j: Between a rock and a hard place by shagie on Saturday December 11, 2021 @06:46PM (#29525432)
Minecraft servers were one part of it... Minecraft clients where another.

If you sent a message to everyone with a client (that logged that message), everyone with a client would at least ping back to the ldap server.

The issue where this was introduced was: https://issues.apache.org/jira/browse/LOG4J2-313

That's from 2013 (Minecraft was 2 years old then) On the other hand, nothing with it really happened until someone asked if it was a security vulnerability - https://github.com/apache/logging-log4j2/pull/608#issuecomme...

And then all hell broke loose.

Simply said, this was a feature that was intended to make it easier for one company to use their structure with ldap lookups for where/how to log. The author of the change did what many people encourage others to do when working with open source "here's some code that I wrote, I'm contributing it back upstream."

If this was part of something "bigger", it sat quiet for the better part of a decade.

Re:Log4j: Between a rock and a hard place by cannabis_sam on Sunday December 12, 2021 @07:15AM (#29528956)
Wow, that’s a scary read…

No consideration, no discussion, no security analysis, just “JDNI is cool, can I hav plz? Ofc!”

Did none of these people consider what JDNI is designed to do?

Did none of these people consider what side-effects are appropriate within a logging library?

Re:Log4j: Between a rock and a hard place by shagie on Sunday December 12, 2021 @01:37PM (#29532231)
Yes... but... realize that log4j2 was in beta releases at the time, being maintained by one developer as part of a "I want to redesign how it works".

As an open source developer working on a project that hadn't even been formally released, I'd be quite pleased to have someone else contributing the features that they found useful back upstream in an effort to make it a better project.

Yes, this is what jndi is supposed to do. Was it done as best as it could be? Probably not. But it isn't something that's only in log4j2

http://logback.qos.ch/manual/loggingSeparation.html#ContextJ...

https://dennis-xlc.gitbooks.io/the-logback-manual/content/en...

But I'm not going to fault a solo developer of some beta software in the world of 2013 for not rejecting a patch because every angle wasn't thought out.

Re:Log4j: Between a rock and a hard place by dumpsterdiver on Saturday December 11, 2021 @07:32PM (#29525769)
Considering that Minecraft players have built functional computers in-game using redstone circuits, it's not surprising to me at all. Minecraft tends to attract folks who have an eye for detail, and a passion for figuring out how things work (a.k.a. hacking).
Re:Log4j: Between a rock and a hard place by enkid on Saturday December 11, 2021 @06:39PM (#29525393)
Or they didn't know what they had. People spend a surprising large amount of time trying to cheat at video games. They could have stumbled onto it in this context without realizing the much larger picture.
Re:Log4j: Between a rock and a hard place by weaksauce on Saturday December 11, 2021 @07:16PM (#29525639)
yeah it's nuts. I wonder what the upper limit on a responsible disclosure bug bounty would have been(of course who would pay that is the question because it's an opensource project with a few maintainers) vs. the nation or underground price. This has been described as a once in a decade RCE.