Security researchers are warning of a critical new Java bug with the very same root induce as the notorious Log4Shell vulnerability currently getting exploited around the world.
CVE-2021-42392 has yet to be officially printed in the National Vulnerability Database (NVD), but in accordance to JFrog, it impacts the console of the preferred H2 Java SQL database.
The security business urged any group at the moment working an H2 console exposed to their LAN or WAN to update the databases instantly to model 2..206 or risk attackers exploiting it for unauthenticated distant code execution (RCE).
Protect and backup your data using AOMEI Backupper. AOMEI Backupper takes secure and encrypted backups from your Windows, hard drives or partitions. With AOMEI Backupper you will never be worried about loosing your data anymore.
Get AOMEI Backupper with 72% discount from an authorized distrinutor of AOMEI: SerialCart® (Limited Offer).
➤ Activate Your Coupon Code
Like Log4Shell, the bug relates to JNDI (Java Naming and Listing Interface) “remote course loading.” JNDI is an API that supplies naming and listing operation for Java applications. It means that if an attacker can get a malicious URL into a JNDI lookup, it could allow RCE.
“In a nutshell, the root lead to is very similar to Log4Shell – various code paths in the H2 databases framework move unfiltered attacker-managed URLs to the javax.naming.Context.lookup operate, which makes it possible for for distant codebase loading (AKA Java code injection AKA remote code execution),” JFrog defined.
“Specifically, the org.h2.util.JdbcUtils.getConnection process will take a driver class name and databases URL as parameters. If the driver’s class is assignable to the javax.naming.Context course, the system instantiates an object from it and calls its lookup technique.”
It additional that providing a driver class these kinds of as “javax.naming.InitialContext” and a URL as very simple as ldap://attacker.com/Exploit will direct to remote code execution.
JFrog reported the vulnerability is notably perilous as the H2 database offer is especially well-liked. It is a person of the prime 50 most well-liked Maven packages, with just about 7000 artifact dependencies, the agency claimed.
Nevertheless, there are some causes why exploitation will not be as common as Log4Shell. For just one, it has a “direct scope of effects,” meaning susceptible servers need to be less complicated to come across.
Second, in most H2 distributions, the console only listens to localhost connections, meaning the default setting is not exploitable.
“Many sellers may be working the H2 databases, but not functioning the H2 console,” JFrog additional. “Although there are other vectors to exploit this issue other than the console, these other vectors are context-dependent and fewer very likely to be exposed to distant attackers.”
Some areas of this write-up are sourced from: