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

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

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 Jan 2025
- **Updated:** 8 Jan 2025
- **Also known as:** GHSA-mjf9-4pcv-vfg7

## 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 (Deserialization of Untrusted Data)

## 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 | Ecosystem | 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: Apache Openmeetings.

## How do I fix CVE-2024-54676?

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

## Is CVE-2024-54676 being exploited?

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

## Other vulnerabilities in Apache OpenMeetings

- [CVE-2017-7664](https://insights.sbomify.com/CVE-2017-7664/): Apache OpenMeetings does not correctly validate uploaded XML documents (critical 10.0)
- [CVE-2023-28326](https://insights.sbomify.com/CVE-2023-28326/): Apache OpenMeetings: allows user impersonation (critical 9.8)
- [CVE-2016-8736](https://insights.sbomify.com/CVE-2016-8736/): Apache OpenMeetings RCE (critical 9.8)
- [CVE-2017-7673](https://insights.sbomify.com/CVE-2017-7673/): Apache OpenMeetings has Inadequate Encryption Strength (critical 9.8)
- [CVE-2017-7666](https://insights.sbomify.com/CVE-2017-7666/): Apache OpenMeetings vulnerable to Cross-Site Request Forgery (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-54676 and fix it if it is affected.

What it is: 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.
Exploitation: There is no known exploitation of CVE-2024-54676 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.apache.openmeetings:openmeetings-parent (Maven): affected from 2.1.0; fixed in 8.0.0
- org.apache.openmeetings:openmeetings-parent (Maven): affected from 2.1.0; fixed in 8.0.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-54676/ (Markdown: https://insights.sbomify.com/CVE-2024-54676/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-54676
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-54676
- OSV: https://osv.dev/vulnerability/CVE-2024-54676

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-54676/
Summaries are generated and may contain mistakes; the official description above is the record.