CVE-2023-51518
Apache James privilege escalation
- Published27 Feb 2024
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 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HAffected products
Remediation
No fixed version is recorded in the NVD data. Check the vendor advisory for the latest guidance.
Frequently asked
Is CVE-2023-51518 being actively exploited?
CVE-2023-51518 is not in the CISA KEV catalog. Its EPSS exploit probability is 1.19%.
How severe is CVE-2023-51518?
CVE-2023-51518 has a CVSS 3.1 base score of 9.8, rated critical. EPSS estimates a 1.19% probability of exploitation.
Which products are affected by CVE-2023-51518?
Affected products include Apache James.
How do I fix CVE-2023-51518?
Apply the vendor's patch or advisory guidance, then verify no affected versions remain across your devices.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2023-51518 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.