Bug 2046282 (CVE-2021-41766) - CVE-2021-41766 karaf: insecure java deserialization
Summary: CVE-2021-41766 karaf: insecure java deserialization
Status: NEW
Alias: CVE-2021-41766
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
Depends On:
Blocks: 2046286
TreeView+ depends on / blocked
Reported: 2022-01-26 14:08 UTC by Guilherme de Almeida Suckevicz
Modified: 2022-04-19 04:39 UTC (History)
27 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
A flaw was found in Apache Karaf. This issue allows monitoring of applications and the Java runtime by using the Java Management Extensions (JMX).
Clone Of:
Last Closed:

Attachments (Terms of Use)

Description Guilherme de Almeida Suckevicz 2022-01-26 14:08:11 UTC
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).

This has been fixed in revision:

Apache Karaf users should upgrade to 4.3.6 or later as soon as possible, or disable remote access to JMX server.

JIRA Tickets:

Note You need to log in before you can comment on or make changes to this bug.