Apache MINA: Unsafe Deserialization (CWE-502) in JavaNativeMessageDecoder
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Apache MINA's MINA 3.0 codec module, specifically its JavaNativeMessageDecoder component, is affected. Because it deserializes incoming data without restricting which classes can be loaded, an attacker who can send data to an application using this decoder could potentially execute arbitrary code on the affected system.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
UNSUPPORTED WHEN ASSIGNED JavaNativeMessageDecoder in the MINA 3.0 codec module calls ObjectInputStream.readObject() on frame bytes with no class filter, so an application that puts it in front of an untrusted peer is open to gadget-chain RCE. As the 3.0.0 branch is inactive, we do not plan to release a version that fixes this issue. Users are recommended to use the latest Apache MINA 2.2.X branch.
Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
- Record last updated
Affected versions
- org.apache.mina:mina-core
From 3.0.0 · through 3.0.0-M2