James Server
Approved changes feed: RSS · Atom
cpe:2.3:a:apache:james_server:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Apache (b0303047-b7dd-5cf8-abcc-71b7d9d80b95) |
|---|---|
| Product | James Server (1f975bb8-4841-5d1d-83c1-a7252782fba9) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from purl2cpe mapping |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:apache/james |
purl2cpe | 2026-06-01 10:14:28.677830 |
pkg:maven/org.apache.james/james-server |
purl2cpe | 2026-06-01 10:14:28.677832 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2024-45626 |
vulnerable | 2026-06-08 06:48:08.752712 |
Apache James: denial of service through JMAP HTML to text conversion
MEDIUM (6.5)
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.
Published: 2025-02-06T11:21:12.417Z
Updated: 2025-02-12T19:51:10.343Z Reference links |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-37358 |
vulnerable | 2026-06-08 06:39:47.283229 |
Apache James: denial of service through the use of IMAP literals
HIGH (8.6)
Similarly to CVE-2024-34055, Apache James is vulnerable to denial of service through the abuse of IMAP literals from both authenticated and unauthenticated users, which could be used to cause unbounded memory allocation and very long computations
Version 3.7.6 and 3.8.2 restrict such illegitimate use of IMAP literals.
Published: 2025-02-06T11:22:38.260Z
Updated: 2025-09-01T09:40:18.781Z Reference links |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-51518 |
vulnerable | 2026-06-08 06:17:53.401909 |
Apache James server: Privilege escalation via JMX pre-authentication deserialisation
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
Published: 2024-02-27T09:09:31.579Z
Updated: 2024-08-22T20:42:38.254Z Reference links |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-26269 |
vulnerable | 2026-06-08 05:57:39.001627 |
Apache James server: Privilege escalation through unauthenticated JMX
Apache James server version 3.7.3 and earlier provides a JMX management service without authentication by default. This allows privilege escalation by a
malicious local user.
Administrators are advised to disable JMX, or set up a JMX password.
Note that version 3.7.4 onward will set up a JMX password automatically for Guice users.
Published: 2023-04-03T07:59:13.228Z
Updated: 2025-02-13T16:44:53.250Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2017-12628 |
vulnerable | 2026-06-08 05:08:47.409461 |
Details available
The JMX server embedded in Apache James, also used by the command line client is exposed to a java de-serialization issue, and thus can be used to execute arbitrary commands. As James exposes JMX socket by default only on local-host, this vulnerability can only be used for privilege escalation. Release 3.0.1 upgrades the incriminated library.
Published: 2017-10-20T15:00:00.000Z
Updated: 2024-08-05T18:43:56.437Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.