, a Michigan-based provider of automated threat detection and response technology, explains, “While this vulnerability also utilizes remote JNDI class loading, it requires access that is not available with the default configuration of the H2 Database. Log4j was unique in that any number of attack-manipulated strings, from headers to URL paths, could result in exploitation of the victim depending on how the application was set up to utilize logging with Log4j.

Read full article on Security Magazine