2 ms·
> the fact that log4j (and its further dependencies like JNDI) can just create a network connection without having been explicitly given the ability to do so.
by chii 5y ago
> the fact that log4j (and its further dependencies like JNDI) can just create a network connection without having been explicitly given the ability to do so.
i dont think this is the responsibility of log4j to express it's capabilities like that. The responsibility should be in the runtime - like the JVM, or even the OS.
Services should run in a sandbox, like how a browser runs a webpage in a sandbox, and only allow capabilities explicitly being requested, and require a human to allow it. Or, have a sandbox such that no matter what code executes, it cannot do more harm than a pre-determined amount (such as limited disk space, limited CPU usage, network usage etc).
The root cause is the security model of modern applications.
- klodolph 5y agoRunning a whole service in a sandbox doesn't offer the kind of granularity you might want.