Bug 2046282 (CVE-2021-41766)

Summary:	CVE-2021-41766 karaf: insecure java deserialization
Product:	[Other] Security Response	Reporter:	Guilherme de Almeida Suckevicz <gsuckevi>
Component:	vulnerability	Assignee:	Red Hat Product Security <security-response-team>
Status:	CLOSED ERRATA	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	unspecified	CC:	aileenc, akoufoud, alazarot, anstephe, ataylor, chazlett, drieden, etirelli, gmalinko, hbraun, ibek, janstey, jnethert, jochrist, jrokos, jross, jstastny, jwon, krathod, kverlaen, mnovotny, pantinor, pdelbell, pjindal, rrajasek, tzimanyi
Target Milestone:	---	Keywords:	Security
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
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).	Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-07-07 18:39:13 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	2046286

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:
https://gitbox.apache.org/repos/asf?p=karaf.git;h=b42c82c
https://gitbox.apache.org/repos/asf?p=karaf.git;h=93a019c

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

JIRA Tickets:
https://issues.apache.org/jira/browse/KARAF-7312

Comment 10 errata-xmlrpc 2022-07-07 14:22:06 UTC

This issue has been addressed in the following products:

  Red Hat Fuse 7.11

Via RHSA-2022:5532 https://access.redhat.com/errata/RHSA-2022:5532

Comment 11 Product Security DevOps Team 2022-07-07 18:39:10 UTC

This bug is now closed. Further updates for individual products will be reflected on the CVE page(s):

https://access.redhat.com/security/cve/cve-2021-41766