First published: Sun Jan 02 2022(Updated: )
Apache Karaf allows monitoring of applications and the Java runtime by using the Java Management Extensions (JMX). JMX is a Java RMI based technology that relies on Java serialized objects for client server communication. Whereas the default JMX implementation is hardened against unauthenticated deserialization attacks, the implementation used by Apache Karaf is not protected against this kind of attack. The impact of Java deserialization vulnerabilities strongly depends on the classes that are available within the targets class path. Generally speaking, deserialization of untrusted data does always represent a high security risk and should be prevented. The risk is low as, by default, Karaf uses a limited set of classes in the JMX server class path. It depends of system scoped classes (e.g. jar in the lib folder).
Credit: security@apache.org security@apache.org
Affected Software | Affected Version | How to fix |
---|---|---|
maven/org.apache.karaf.management:org.apache.karaf.management.server | <4.3.6 | 4.3.6 |
Apache Karaf | <4.3.6 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2021-41766 is a vulnerability in Apache Karaf that allows monitoring of applications and the Java runtime.
CVE-2021-41766 allows unauthenticated deserialization of Java objects in the default JMX implementation of Apache Karaf.
The severity of CVE-2021-41766 is high with a CVSS score of 8.1.
To fix CVE-2021-41766 in Apache Karaf, upgrade to version 4.3.6.
More information about CVE-2021-41766 can be found at the following references: [Link 1](https://gitbox.apache.org/repos/asf?p=karaf.git;h=b42c82c), [Link 2](https://gitbox.apache.org/repos/asf?p=karaf.git;h=93a019c), [Link 3](https://issues.apache.org/jira/browse/KARAF-7312).