CVE-2023-51518: Apache James server: Privilege escalation via JMX pre-authentication deserialisation
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
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2023-51518?
CVE-2023-51518 is classified as a medium severity vulnerability due to the potential for privilege escalation through deserialization issues.
How do I fix CVE-2023-51518?
To fix CVE-2023-51518, upgrade Apache James to version 3.8.1 or 3.7.5.
What versions of Apache James are affected by CVE-2023-51518?
Apache James versions prior to 3.7.5 and 3.8.0 are affected by CVE-2023-51518.
What type of attack does CVE-2023-51518 facilitate?
CVE-2023-51518 can facilitate privilege escalation attacks through the exploitation of a JMX endpoint vulnerability.
Is the JMX endpoint exposed to external access in CVE-2023-51518?
The JMX endpoint affected by CVE-2023-51518 is exposed on localhost, limiting access primarily to local attacks.