CVE-2024-52046 Apache MINA: MINA applications using unbounded deserialization may allow RCE

Critical 10.0 Published Updated

Attackers can achieve remote code execution by sending malicious serialized data to Apache MINA applications using unbounded deserialization.

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-52046?

CVE-2024-52046 is a critical unsafe deserialization vulnerability in Apache MINA, published on 25 Dec 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

Official description

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.

Weakness: CWE-502

Which versions are affected by CVE-2024-52046?

6 open source packages ship an affected version, including org.apache.mina:mina-core. It affects 1 product.

PackageAffectedFixed in
org.apache.mina:mina-core MavenFrom 2.0.0-M12.0.27
org.apache.mina:mina-core MavenFrom 2.0.0-M12.0.27
org.apache.mina:mina-core MavenFrom 2.1.02.1.10
org.apache.mina:mina-core MavenFrom 2.1.02.1.10
org.apache.mina:mina-core MavenFrom 2.2.02.2.4
org.apache.mina:mina-core MavenFrom 2.2.02.2.4

Products include Apache Mina.

How do I fix CVE-2024-52046?

Upgrade org.apache.mina:mina-core to a fixed version for your release line: 2.0.27, 2.1.10 or 2.2.4.

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

Is CVE-2024-52046 being exploited?

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

Sources

Also known as CLEANSTART-2026-CR72646, CLEANSTART-2026-LT24627, CLEANSTART-2026-XR50607, DEBIAN-CVE-2024-52046, GHSA-76h9-2vwh-w278, OESA-2025-1044 and 1 more.

Is CVE-2024-52046 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free