News for hackers. Stuff that matters.
Re:Jndi: An irresponsibly bad logging library by pja on Saturday December 11, 2021 @05:06AM (#29519825)
This was by design. Java has a history of these kinds of wild exploits ever since the XML days.

The original use case was probably something like: we want to be able to customise the logging on a per user/customer basis, so if we can make a call to our LDAP server, we can return a Java class that will implement that customisation.

This is enterprise level thinking.

Some history from cloudflare here: https://blog.cloudflare.com/inside-the-log4j2-vulnerability-...

Re:Jndi: An irresponsibly bad logging library by ljm on Saturday December 11, 2021 @05:47AM (#29519972)
This is definitely the kind of thing you'd get from an enterprise IT consultancy when you ask for an ERP system and require services to authenticate via ActiveDirectory.
Re:Jndi: An irresponsibly bad logging library by sildur on Saturday December 11, 2021 @09:30AM (#29521091)
> This is enterprise level thinking.

An enterprise-level app must be like a slum built on a minefield, then.

Re:Jndi: An irresponsibly bad logging library by dtgriscom on Saturday December 11, 2021 @04:47PM (#29524569)
More like a disco dance floor built on a minefield.
Re:Jndi: An irresponsibly bad logging library by xvector on Saturday December 11, 2021 @08:20AM (#29520670)
Never go full enterprise level thinking.