dbcve.org
James ServerApplication · Apache

CVE-2024-45626

HIGH · 7.5 CVSS v3.1 Published 2025-02-06
Fix available
A fix is available. Upgrade to 3.7.6 / 3.8.2 or later.
See remediation →
84/100
Remediation priority · High
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 server JMAP HTML to text plain implementation in versions below 3.8.2 and 3.7.6 is subject to unbounded memory consumption that can result in a denial of service. Users are recommended to upgrade to version 3.7.6 and 3.8.2, which fix this issue.

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 server's JMAP HTML-to-plain-text conversion implementation suffers from unbounded memory consumption. An attacker can send specially crafted HTML content through the JMAP interface that causes excessive memory allocation, leading to denial of service. The vulnerability exists because the HTML parsing/conversion logic does not impose limits on memory usage during processing.

MitigationUpgrade Apache James to version 3.7.6 or 3.8.2 (depending on the release branch in use) to resolve the unbounded memory consumption issue.

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
James ServerApplication
Affected:< 3.7.6>= 3.8.0, < 3.8.2

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
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 Server version
    Run 'java -jar james-server.jar --version' or check the pom.xml/build.conf file in your deployment directory. Alternatively, check the JMX interface or administrative API for the server version.
    Affected if The installed version is less than 3.7.6, or greater than or equal to 3.8.0 but less than 3.8.2
  2. Verify JMAP protocol is enabled
    Check the james-database.properties or james-server.xml configuration file for 'jmap.enabled=true' or inspect the smtpserver.xml/jmapserver.xml to confirm the JMAP server is configured and listening.
    Affected if JMAP is enabled and the server version falls within the affected range
  3. Confirm JVM memory limits allow unbounded growth
    Inspect startup scripts (bin/run.sh, bin/run.bat, or systemd service files) for -Xmx settings. If no -Xmx limit is set or if the limit is very high, the DoS condition can fully manifest.
    Affected if No restrictive JVM heap limit is configured and the server version is affected

The server is affected if it runs Apache James version 3.7.5 or earlier, or 3.8.0-3.8.1, with JMAP enabled and without restrictive JVM memory constraints.

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
Upgrade available Upgrade to 3.7.6 / 3.8.2 or later
Fixed in 3.7.63.8.2
Interim mitigation

Upgrade Apache James to version 3.7.6 or 3.8.2 (depending on the release branch in use) to resolve the unbounded memory consumption issue.

Recommended fix High confidence

3.7.6 or 3.8.2 (depending on your release branch)

  1. Identify the currently running Apache James Server version
  2. Determine which release branch you are on (3.7.x or 3.8.x)
  3. For 3.7.x branch: upgrade to version 3.7.6
  4. For 3.8.x branch: upgrade to version 3.8.2
  5. Back up the current James Server installation and configuration
  6. Stop the running James Server instance
  7. Replace the James Server binaries with the new version
  8. Review and update configuration if needed for the new version

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

Fix this in James Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-45626 — 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-2024-45626 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