cve.bz

CVE-2024-52046 apache mina: Deserialization of Untrusted Data

10.0 criticalEPSS 25%Fix available

Critical (10.0) in apache mina. EPSS 25% estimated probability of exploitation activity in the next 30 days. Fixed in org.apache.mina:mina-core 2.0.27, 2.1.10, 2.2.4.

On this page
The ObjectSerializationDecoder in Apache MINA uses Java’s native deserialization protocol to process incoming serialized data but lacks the necessary security checks and defenses. This vulnerability allows attackers to exploit the deserialization process by sending specially crafted malicious serialized data, potentially leading to remote code execution (RCE) attacks. This issue affects MINA core versions 2.0.X, 2.1.X and 2.2.X, and will be fixed by the releases 2.0.27, 2.1.10 and 2.2.4. It's also important to note that an application using MINA core library will only be affected if the IoBuffer#getObject() method is called, and this specific method is potentially called when adding a ProtocolCodecFilter instance using the ObjectSerializationCodecFactory class in the filter chain. If your application is specifically using those classes, you have to upgrade to the latest version of MINA core library. Upgrading will  not be enough: you also need to explicitly allow the classes the decoder will accept in the ObjectSerializationDecoder instance, using one of the three new methods: /**      * Accept class names where the supplied ClassNameMatcher matches for * deserialization, unless they are otherwise rejected. * * @param classNameMatcher the matcher to use */ public void accept(ClassNameMatcher classNameMatcher) /** * Accept class names that match the supplied pattern for * deserialization, unless they are otherwise rejected. * * @param pattern standard Java regexp */ public void accept(Pattern pattern) /** * Accept the wildcard specified classes for deserialization, * unless they are otherwise rejected. * * @param patterns Wildcard file name patterns as defined by * {@link org.apache.commons.io.FilenameUtils#wildcardMatch(String, String) FilenameUtils.wildcardMatch} */ public void accept(String... patterns) By default, the decoder will reject *all* classes that will be present in the incoming data. Note: The FtpServer, SSHd and Vysper sub-project are not affected by this issue.

Severity

CVSS 4.0

10.0 critical
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H

CVSS 3.1

9.8 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
25% (unchanged from 25% a week ago; 24% 30 days ago) estimated probability of exploitation activity in the next 30 days; 98th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: total, assessed 2025-08-01. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-502 Deserialization of Untrusted Data
OWASP Top 10
A08:2025 Software or Data Integrity Failures
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2024-52046 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2024-52046?via=ask-ai-copy and https://cve.bz/cve/CVE-2024-52046?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2024-52046 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Apache Software Foundation Apache MINAfrom 2.1 through 2.1.9
Apache Software Foundation Apache MINAfrom 2.2 through 2.2.3

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-76h9-2vwh-w278Mavenorg.apache.mina:mina-core>=2.2.0 <2.2.42.2.4
GHSA-76h9-2vwh-w278Mavenorg.apache.mina:mina-core>=2.1.0 <2.1.102.1.10
GHSA-76h9-2vwh-w278Mavenorg.apache.mina:mina-core>=2.0.0-M1 <2.0.272.0.27

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12mina, mina2no fix listedDEBIAN-CVE-2024-52046
Debian13mina2no fix listedDEBIAN-CVE-2024-52046
Debian14mina22.2.9-1DEBIAN-CVE-2024-52046
Ubuntu16.04:LTS, 18.04:LTS, 20.04:LTSmina, mina2no fix listedUBUNTU-CVE-2024-52046
Ubuntu22.04:LTS, 24.04:LTSminano fix listedUBUNTU-CVE-2024-52046
Ubuntu25.10, 26.10mina2no fix listedUBUNTU-CVE-2024-52046
UbuntuPro:22.04:LTSmina22.1.5-1ubuntu0.1~esm1USN-8465-1
UbuntuPro:24.04:LTSmina22.2.1-3ubuntu0.1~esm1USN-8465-1
UbuntuPro:26.04:LTSmina22.2.1-4ubuntu0.1~esm1USN-8465-1

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu.

Red Hat

Red Hat rates this Important.

Red Hat's statement

This vulnerability is rated as Important due to the risk of remote code execution via insecure Java deserialization in Apache MINA, where attackers can exploit the lack of security checks in the deserialization process, potentially compromising systems that use specific MINA classes.

Apache Mina is a transitive dependency of Apache Directory that is used only in Apache Kafka tests. Therefore, streams for Apache Kafka is not vulnerable to this issue.

Red Hat's mitigation

Configure the Apache MINA ObjectSerializationDecoder to allow only the classes required by the application for deserialization, using accept(ClassNameMatcher), accept(Pattern), or accept(String... patterns). By default, the decoder rejects all classes in incoming data. Applications using the affected deserialization path should also upgrade Apache MINA core to a vendor-fixed release; upgrading alone is insufficient without explicitly configuring the allowed classes.

ProductPackageStateAdvisory
Red Hat build of Apache Camel 4.8.3 for Spring Bootmina-coreFixed 2025-02-05RHSA-2025:1078
A-MQ Clients 2mina-coreAffected
Red Hat AMQ Broker 7mina-coreWill not fix
Red Hat build of Apache Camel - HawtIO 4mina-coreNot affected
Red Hat Build of Keycloakmina-coreWill not fix
Red Hat Data Grid 8mina-coreWill not fix
Red Hat Fuse 7mina-coreOut of support scope
Red Hat Integration Camel K 1mina-coreWill not fix
Red Hat JBoss Data Grid 7mina-coreAffected
Red Hat JBoss Enterprise Application Platform 7mina-coreNot affected
Red Hat JBoss Enterprise Application Platform 8mina-coreNot affected
Red Hat JBoss Enterprise Application Platform Expansion Packmina-coreNot affected
Red Hat Process Automation 7mina-coreNot affected
Red Hat Single Sign-On 7mina-coreNot affected
streams for Apache Kafkamina-coreWill not fix

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2024-52046.

Attack patterns (CAPEC)

  • CAPEC-586 Object Injection Likelihood: Medium · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON