CVE-2023-51518: Apache James server: Privilege escalation via JMX pre-authentication deserialization
Apache James prior to version 3.7.5 and 3.8.0 exposes a JMX endpoint on localhost subject to pre-authentication deserialisation of untrusted data. Given a deserialisation gadjet, this could be leveraged as part of an exploit chain that could result in privilege escalation. Note that by default JMX endpoint is only bound locally.
Published Feb 27, 2024 · Updated Mar 15, 2026
Affected packages
org.apache.james:james-server
- Ecosystem
- Maven
- Affected
- <= 3.7.4
- Fixed in
- 3.7.5
- Check
mvn dependency:tree -Dincludes=org.apache.james:james-server
org.apache.james:james-server
- Ecosystem
- Maven
- Affected
- >= 3.8.0, < 3.8.1
- Fixed in
- 3.8.1
- Check
mvn dependency:tree -Dincludes=org.apache.james:james-server
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Apache James prior to version 3.7.5 and 3.8.0 exposes a JMX endpoint on localhost subject to pre-authentication deserialisation of untrusted data. Given a deserialisation gadjet, this could be leveraged as part of an exploit chain that could result in privilege escalation. Note that by default JMX endpoint is only bound locally.
We recommend users to:
- Upgrade to a non-vulnerable Apache James version
- Run Apache James isolated from other processes (docker - dedicated virtual machine)
- If possible turn off JMX
Credited to oscerd.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology