CVE-2024-52046

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.

• CWE-502
• CWE-502

• https://lists.apache.org/thread/4wxktgjpggdbto15d515wdctohb0qmv8Mailing List
• http://www.openwall.com/lists/oss-security/2024/12/25/1Mailing List
• https://security.netapp.com/advisory/ntap-20250103-0001/Third Party Advisory

Published

Dec 25, 2024

Last Modified

Jun 17, 2026

Status

Modified

• How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
• Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
• PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
• AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.

• CVE-2024-52032Mattermost versions 10.0.x <= 10.0.0 and 9.11.x <= 9.11.2 fa…4.3
• CVE-2024-52033Exposure of sensitive system information to an unauthorized …5.3
• CVE-2024-52034An OS Command Injection vulnerability exists within myPRO Ma…10
• CVE-2024-52035An integer overflow vulnerability exists in the OLE Document…7.8
• CVE-2024-5204The Swiss Toolkit For WP plugin for WordPress is vulnerable …8.8
• CVE-2024-52043Generation of Error Message Containing Sensitive Information…5.3
• CVE-2024-52047A widget local file inclusion vulnerability in Trend Micro A…8.8
• CVE-2024-52048A LogServer link following vulnerability in Trend Micro Apex…7.8
• CVE-2024-52049A LogServer link following vulnerability in Trend Micro Apex…7.8
• CVE-2024-5205The Videojs HTML5 Player plugin for WordPress is vulnerable …6.4
• CVE-2024-52050A LogServer arbitrary file creation vulnerability in Trend M…7.8
• CVE-2024-52051A vulnerability has been identified in SIMATIC S7-PLCSIM V17…7.3