CVE-2024-54676 Apache OpenMeetings: Deserialisation of untrusted data in cluster mode

Critical 9.8 Published 8 Jan 2025 Updated 8 Jan 2025

Attackers can execute arbitrary code via unsafe deserialization in Apache OpenMeetings when clustering is enabled without proper serialization filters.

Exploited in the wild: Not known
Login needed: Not needed
Attackable: Over the internet
Victim action needed: Not needed
Fix: Available

What is CVE-2024-54676?

CVE-2024-54676 is a critical unsafe deserialization vulnerability in Apache OpenMeetings, published on 8 Jan 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

Official description

Vendor: The Apache Software Foundation

Versions Affected: Apache OpenMeetings from 2.1.0 before 8.0.0

Description: Default clustering instructions at https://openmeetings.apache.org/Clustering.html doesn't specify white/black lists for OpenJPA this leads to possible deserialisation of untrusted data. Users are recommended to upgrade to version 8.0.0 and update their startup scripts to include the relevant 'openjpa.serialization.class.blacklist' and 'openjpa.serialization.class.whitelist' configurations as shown in the documentation.

Weakness: CWE-502

Which versions are affected by CVE-2024-54676?

2 open source packages ship an affected version, including org.apache.openmeetings:openmeetings-parent. It affects 1 product.

Package	Affected	Fixed in
`org.apache.openmeetings:openmeetings-parent` Maven	From `2.1.0`	`8.0.0`
`org.apache.openmeetings:openmeetings-parent` Maven	From `2.1.0`	`8.0.0`

Products include Apache Openmeetings.

How do I fix CVE-2024-54676?

Upgrade org.apache.openmeetings:openmeetings-parent to 8.0.0 or later.

Upgrade, and only deserialise data from trusted sources or with an allow-list of types. More about Unsafe deserialization.

Is CVE-2024-54676 being exploited?

There is no known exploitation of CVE-2024-54676 in the wild and no public exploit code.

Sources

Also known as GHSA-mjf9-4pcv-vfg7.