CVE-2024-54676: Apache OpenMeetings: Deserialisation of untrusted data in cluster mode
First published: Wed Jan 08 2025(Updated: )
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.
Credit: security@apache.org security@apache.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| maven/org.apache.openmeetings:openmeetings-parent | >=2.1.0<8.0.0 | 8.0.0 |
| Apache OpenMeetings | >=2.1<8.0.0 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://lists.apache.org/thread/o0k05jxrt5tp4nm45lj14yfjxmg67m95
- http://www.openwall.com/lists/oss-security/2025/01/08/1
- https://nvd.nist.gov/vuln/detail/CVE-2024-54676
- https://github.com/apache/openmeetings/commit/1c3426c6d3abbd984a3c01a61decf1242ea38923
- https://issues.apache.org/jira/browse/OPENMEETINGS-2787
- https://github.com/advisories/GHSA-mjf9-4pcv-vfg7 (Advisory)
Frequently Asked Questions
What is the severity of CVE-2024-54676?
CVE-2024-54676 has been assigned a critical severity due to its potential for remote code execution.
How do I fix CVE-2024-54676?
To resolve CVE-2024-54676, upgrade Apache OpenMeetings to version 8.0.0 or later.
What versions are affected by CVE-2024-54676?
CVE-2024-54676 affects Apache OpenMeetings versions from 2.1.0 to before 8.0.0.
What are the implications of CVE-2024-54676?
The implications of CVE-2024-54676 include potential unauthorized remote access and execution of arbitrary code.
Is there a workaround for CVE-2024-54676?
Currently, there are no effective workarounds for CVE-2024-54676 besides upgrading to the fixed version.
- collector/oss-sec
- source/oss-sec
- alias/CVE-2024-54676
- agent/title
- agent/first-publish-date
- agent/weakness
- agent/type
- agent/description
- agent/severity
- collector/github-advisory-latest
- source/GitHub
- alias/GHSA-mjf9-4pcv-vfg7
- agent/software-canonical-lookup
- agent/references
- agent/event
- agent/trending
- collector/nvd-cve
- source/NVD
- agent/author
- collector/mitre-cve
- source/MITRE
- collector/nvd-api
- agent/last-modified-date
- agent/softwarecombine
- agent/source
- agent/tags
- collector/github-advisory
- package-manager/maven
- vendor/apache
- canonical/apache openmeetings
- version/apache openmeetings/2.1