CVE-2024-52046: Apache MINA Deserialization RCE Vulnerability

Should you act?

High exploit likelihood

EPSS ranks it in the top 5% of all CVEs for likely exploitation in the next 30 days. This signal is computed from CISA KEV, EPSS and CVSS data; it is not an editorial verdict.

• No confirmed exploitation. It is not in CISA’s KEV catalog and CISA’s SSVC assessment records no known exploitation. That can change quickly after a public write-up; re-check if you are affected.
• EPSS 24.4%, percentile 98: FIRST’s model estimates a 24.4% chance of exploitation activity in the next 30 days, higher than 98% of all scored CVEs (very high). EPSS is a probability, not a verdict.
• Remotely reachable with no login and no user interaction. If the vulnerable service is exposed to the internet, prioritize it.
• Only applies if your dependency tree includes org.apache.mina:mina-core (Maven) >= 2.2.0, < 2.2.4, fixed in 2.2.4; org.apache.mina:mina-core (Maven) >= 2.1.0, < 2.1.10, fixed in 2.1.10; org.apache.mina:mina-core (Maven) >= 2.0.0-M1, < 2.0.27, fixed in 2.0.27. Check your lockfile, including transitive dependencies.

What it is

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.

From the GitHub advisory

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:

1. 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)

Weakness type: CWE-502, CWE-94.

Product: org.apache.mina:mina-core (Maven) · Assigned by: apache · Published: 2024-12-25

Affected and fixed versions

Severity scores

• Attack vector: network (remotely reachable)
• Attack complexity: low
• Attack requirements: none
• Privileges required: none (no login)
• User interaction: none

CVSS measures how bad a flaw is if exploited, not how likely exploitation is. Read it next to the exploitation data below.

Exploitation and urgency

• CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).
• CISA SSVC assessment: exploitation none, automatable yes, technical impact total.
• FIRST EPSS (model of 2026-10-21): 24.37% probability of exploitation activity in the next 30 days; percentile 98.

Timeline

• 2024-12-25 — CVE record published by apache
• 2024-12-25 — GitHub-reviewed advisory GHSA-76h9-2vwh-w278 published (critical)
• 2025-08-02 — CVE record last updated

Sources and references

Original sources first. Version and fix details should always be confirmed against the vendor or project advisory.

Vendor and project advisories, patches

1. lists.apache.org lists.apache.org

Vulnerability records

1. GitHub Advisory GHSA-76h9-2vwh-w278 github.com
2. CVE.org record CVE-2024-52046 cve.org
3. NVD entry CVE-2024-52046 nvd.nist.gov

Other references from the CVE record and advisory

1. openwall.com openwall.com
2. security.netapp.com security.netapp.com

Critical Maven advisories · Today’s Security Digest