Vulnerabilidades do Maven Org.apache.mina:mina-core

The fix for CVE-2026-41635 was not applied to the 2.1.X and 2.2.X branches. Here was the original issue description: Apache MINA's AbstractIoBuffer.resolveClass() contains two branches, one of them (for static classes or primitive types) does not check the class at all, bypassing the classname allowlist and allowing arbitrary code to be executed. The fix checks if the class is present in the accepted class filter before calling Class.forName(). Affected versions are Apache MINA 2.1.0 <= 2.1.11, and 2.2.0 <= 2.2.6. The problem is resolved in Apache MINA 2.1.12, and 2.2.7 by applying the classname allowlist earlier. Affected are applications using Apache MINA that call IoBuffer.getObject(). Applications using Apache MINA are advised to upgrade.

The fix for CVE-2026-41409 was not applied to the 2.1.X and 2.2.X branches. Here was the original issue description: The fix for CVE-2024-52046 in Apache MINA AbstractIoBuffer.getObject() was incomplete. The classname allowlist of classes allowed to be deserialized was applied too late after a static initializer in a class to be read might already have been executed. Affected versions are Apache MINA 2.1.0 <= 2.1.11, and 2.2.0 <= 2.2.6. The problem is resolved in Apache MINA 2.1.12, and 2.2.7 by applying the classname allowlist earlier. Affected are applications using Apache MINA that call IoBuffer.getObject(). Applications using Apache MINA are advised to upgrade The fix for CVE-2024-52046 in Apache MINA AbstractIoBuffer.getObject() was incomplete. The classname allowlist of classes allowed to be deserialized was applied too late after a static initializer in a class to be read might already have been executed. Affected versions are Apache MINA 2.1.0 <= 2.1.110, and 2.2.0 <= 2.2.6. The problem is resolved in Apache MINA 2.1.12, and 2.2.7 by applying the classname allowlist earlier. Affected are applications using Apache MINA that call IoBuffer.getObject(). Applications using Apache MINA are advised to upgrade

A correção para CVE-2024-52046 em AbstractIoBuffer.getObject() do Apache MINA foi incompleta. A lista de permissões de nomes de classes permitidas para desserialização foi aplicada tarde demais, depois que um inicializador estático de uma classe a ser lida poderia já ter sido executado. As versões afetadas são Apache MINA 2.0.0 <= 2.0.27, 2.1.0 <= 2.1.10 e 2.2.0 <= 2.2.5. O problema é resolvido no Apache MINA 2.0.28, 2.1.11 e 2.2.6 ao aplicar a lista de permissões de nomes de classes mais cedo. São afetadas as aplicações que usam Apache MINA e chamam IoBuffer.getObject(). As aplicações que usam Apache MINA são aconselhadas a atualizar

A função resolveClass() de AbstractIoBuffer do Apache MINA contém dois ramos; um deles (para classes estáticas ou tipos primitivos) não verifica a classe, contornando a lista de permissão de nomes de classe e permitindo a execução de código arbitrário. A correção verifica se a classe está presente no filtro de classes aceitas antes de chamar Class.forName(). São afetadas as versões Apache MINA 2.0.0 <= 2.0.27, 2.1.0 <= 2.1.10 e 2.2.0 <= 2.2.5. O problema foi resolvido no Apache MINA 2.0.28, 2.1.11 e 2.2.6 ao aplicar a lista de permissão de nomes de classe mais cedo. São afetadas as aplicações que usam o Apache MINA e chamam IoBuffer.getObject(). Recomenda-se que as aplicações que usam o Apache MINA sejam atualizadas.

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.