Apache MINAs 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.0.0 <= 2.0.27, 2.1.0 <= 2.1.10, and
2.2.0 <= 2.2.5.
The problem is resolved in Apache MINA 2.0.28, 2.1.11, and 2.2.6 by applying the classname allowlist earlier.
Affected are applications using Apache MINA that call IoBuffer.getObject().
Applications using Apache MINA are advised to upgrade.
Weakness
The product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid.
Affected Software
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Mina | Apache | 2.0.0 (including) | 2.0.28 (excluding) |
| Mina | Apache | 2.1.0 (including) | 2.1.11 (excluding) |
| Mina | Apache | 2.2.0 (including) | 2.2.6 (excluding) |
| Red Hat build of Apache Camel 4.18.1 for Spring Boot 3.5.14 | RedHat | mina-core | * |
| Mina | Ubuntu | esm-apps/xenial | * |
| Mina2 | Ubuntu | esm-apps/xenial | * |
Potential Mitigations
- Make fields transient to protect them from deserialization.
- An attempt to serialize and then deserialize a class containing transient fields will result in NULLs where the transient data should be. This is an excellent way to prevent time, environment-based, or sensitive variables from being carried over and used improperly.