dbcve.org
JamesApplication · Apache

CVE-2023-51518

CRITICAL · 9.8 CVSS v3.1 Published 2024-02-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Apache James mail server versions prior to 3.7.5 and 3.8.0 expose a JMX (Java Management Extensions) endpoint on localhost that allows pre-authentication deserialization of untrusted data. When combined with a deserialization gadget, this vulnerability enables privilege escalation as part of an exploit chain.

MitigationUpgrade Apache James to version 3.7.5 or 3.8.0, or disable the JMX endpoint if not required, and run the service in isolation (dedicated VM or container) to limit attack surface.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
JamesApplication
Affected:= 3.7.5= 3.8.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Apache James version
    Check the version file or startup logs for Apache James. Common locations: check the james-project.ini or version.info file in the James installation directory, or inspect the startup banner/logs when James launches.
    Affected if The installed version is earlier than 3.7.5 or earlier than 3.8.0 (versions prior to these releases are affected).
  2. Locate JMX configuration
    Examine the James configuration files for JMX settings. Look in the james-database.properties, jmx.properties, or similar configuration files in the conf/ directory of the James installation.
    Affected if JMX is enabled in the configuration files (look for jmx.enabled=true, jmx.port settings, or JMX-related beans in the configuration).
  3. Verify JMX network binding
    Check if the JMX endpoint is bound to localhost or an accessible network interface. Review the jmx configuration for the bind address. On Linux, you can also run 'netstat -tlnp | grep jmx_port' or 'ss -tlnp | grep jmx_port' to see what interface JMX listens on.
    Affected if JMX is listening on a reachable network interface (0.0.0.0 or non-localhost IP) rather than only localhost, or if the JMX port is exposed externally.
  4. Check for deserialization gadgets
    Review the classpath for known Java deserialization gadget libraries. Examine the lib/ or libs/ directory in the James installation for common gadget libraries such as Apache Commons Collections, Groovy, Spring Beans, CGLIB, or similar libraries that can be exploited for deserialization attacks.
    Affected if Deserialization gadget libraries are present in the classpath that could be chained with the JMX deserialization vulnerability.

You are affected if running Apache James version prior to 3.7.5 or prior to 3.8.0 with JMX enabled and accessible (even on localhost), combined with vulnerable deserialization gadgets in the classpath.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Apache James to version 3.7.5 or 3.8.0, or disable the JMX endpoint if not required, and run the service in isolation (dedicated VM or container) to limit attack surface.

Recommended fix High confidence

Apache James 3.8.1 or 3.7.6 (or latest stable 3.8.x)

  1. 1. Back up your current Apache James configuration and data directory
  2. 2. Stop the Apache James service
  3. 3. Upgrade Apache James to version 3.8.1 (or 3.7.6 for the 3.7.x branch) which contains the fix for CVE-2023-51518
  4. 4. Verify the JMX configuration - ensure it remains bound to localhost only if JMX is needed
  5. 5. Restart the Apache James service
  6. 6. Verify the service starts successfully and is functioning properly
Caveat Review release notes for any behavioral changes between your current version and the target upgrade version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in James Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-51518 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-51518 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data