CVE-2023-51518 — CRITICAL (9.8)

Vulnerability 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: - 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 Score

9.8

CRITICAL

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector

NETWORK

Attack Complexity

LOW

Privileges Required

NONE

User Interaction

NONE

Scope

UNCHANGED

Confidentiality

HIGH

Integrity

HIGH

Availability

HIGH

Affected Products

Vendor	Product	Versions
Apache	James	3.7.5

Related Weaknesses (CWE)

CWE-502

References

https://lists.apache.org/thread/wbdm61ch6l0kzjn6nnfmyqlng82qz0orMailing ListVendor Advisory
https://lists.apache.org/thread/wbdm61ch6l0kzjn6nnfmyqlng82qz0orMailing ListVendor Advisory

FAQ

What is CVE-2023-51518?

CVE-2023-51518 is a vulnerability with a CVSS score of 9.8 (CRITICAL). 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 leverag...

How severe is CVE-2023-51518?

CVE-2023-51518 has been rated CRITICAL with a CVSS base score of 9.8/10. This is considered a critical vulnerability requiring immediate attention.

Is there a patch for CVE-2023-51518?

Check the references section above for vendor advisories and patch information. Affected products include: Apache James.