CVE-2023-51518

Published: 27/02/2024 Updated: 27/02/2024

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

Severity: low Affected versions: - Apache James server through 374 - Apache James server 38 through 380 Description: Apache James prior to version 375 and 380 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 exploi ...

CVE-2023-51518: Preauthenticated Java Deserialization via JMX in Apache James

CVE-2023-51518: Preauthenticated Java Deserialization via JMX in Apache James Apache James distribution prior to release 375 and 381 allow privilege escalation via JMX pre-authentication deserialization Given a deserialization gadget, this could be leveraged as part of an exploit chain that could result in privilege escalation Note: For Apache James servers running using

CWE-502 https://lists.apache.org/thread/wbdm61ch6l0kzjn6nnfmyqlng82qz0or https://nvd.nist.gov https://github.com/mbadanoiu/CVE-2023-51518 https://seclists.org/oss-sec/2024/q1/161

CVE-2023-51518

Vulnerability Summary

Vulnerability Trend

Mailing Lists

Github Repositories

References

Vulmon Search

About

Products

Connect