CVE-2023-51518: Apache James server: Privilege escalation via JMX pre-authentication deserialisation

                							

                <!--X-Body-Begin-->
<!--X-User-Header-->

oss-sec
mailing list archives
<!--X-User-Header-End-->
<!--X-TopPNI-->

By Date

By Thread

</form>

<!--X-TopPNI-End-->
<!--X-MsgBody-->
<!--X-Subject-Header-Begin-->
CVE-2023-51518: Apache James server: Privilege escalation via JMX pre-authentication deserialisation

<!--X-Subject-Header-End-->
<!--X-Head-of-Message-->

From: Benoit Tellier &lt;btellier () apache org&gt;

Date: Mon, 26 Feb 2024 17:10:05 +0000

<!--X-Head-of-Message-End-->
<!--X-Head-Body-Sep-Begin-->

<!--X-Head-Body-Sep-End-->
<!--X-Body-of-Message-->
Severity: low

Affected versions:

- Apache James server through 3.7.4
- Apache James server 3.8 through 3.8.0

Description:

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:
&nbsp;- Upgrade to a non-vulnerable Apache James version

&nbsp;- Run Apache James isolated from other processes (docker - dedicated virtual machine)
&nbsp;- If possible turn off JMX

Credit:

Mal Aware (reporter)
Arnout Engelen (analyst)

References:

https://james.apache.org/
https://www.cve.org/CVERecord?id=CVE-2023-51518

<!--X-Body-of-Message-End-->
<!--X-MsgBody-End-->
<!--X-Follow-Ups-->

<!--X-Follow-Ups-End-->
<!--X-References-->
<!--X-References-End-->
<!--X-BotPNI-->

By Date

By Thread

Current thread:

CVE-2023-51518: Apache James server: Privilege escalation via JMX pre-authentication deserialisation Benoit Tellier (Feb 26)

<!--X-BotPNI-End-->
<!--X-User-Footer-->
<!--X-User-Footer-End-->