Apache James server: Privilege escalation via JMX pre-authentication deserialisation
48Vexday Risk Score
No sign of exploitation. It has a public proof of concept.
ssvc Attendcvss 9.8epss 1.2%
from disclosure to weapon97 days
Published on NVDFeb 27
1st PoC+97d
exploitation probability
1.2%top 35% of all CVEs
observed exploitation
nono source reports it
1 public exploit(s)
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
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Affected products
Apache Software Foundation · Apache James serverpublic PoCs found — 1
githubgithub.com/mbadanoiu/CVE-2023-51518★ 1⚠ Public resources, to assess the exposure of systems you control or are authorized to test. Test only with authorization.