News for hackers. Stuff that matters.
Re:Log4j: Between a rock and a hard place by hn_throwaway_99 on Saturday December 11, 2021 @05:32PM (#29524867)
I wish your comment would get higher visibility.

To clarify, the vulnerability would make it possible to post server environment variables to any remote server, regardless of JRE version. That could easily end up being as catastrophic as an RCE.

Re:Log4j: Between a rock and a hard place by ta45674754 on Saturday December 11, 2021 @07:18PM (#29525649)
Yeah that's a disaster, many applications/pods/docker containers store secrets in the environment. Even if it doesn't expose the service from the outside due to firewalls etc, its a(nother) way in for malicious internal users (which I believe are a large portion of, or the majority of, breaches).
Re:Log4j: Between a rock and a hard place by strenholme on Sunday December 12, 2021 @12:14AM (#29527339)
Indeed. Anything which exposes a program’s environment to other non-root programs which are not sub-processes should be considered a security bug.
Re:Log4j: Between a rock and a hard place by brabel on Sunday December 12, 2021 @02:01AM (#29527708)
> the vulnerability would make it possible to post server environment variables to any remote server, regardless of JRE version.

I've been able to achieve RCE as well by still using LDAP, but a different lookup mechanism (if you learn about LDAP, you'll quickly realize there's several ways to do this). RCE does not require remote class loading, that's just the easiest way to achieve it.

If your JVM triggered the evaluation of any unsafe jndi string, you should assume an RCE is very likely possible on your environment.