WaratekVRT Sign in

James-server CVEs with no public exploit

11 CVEs, 5 protected by Waratek

Reset
More filters (1)
Columns
Product james-server✕
Overview 11 matches · 5 protected · 0 exploited · 0 CISA KEV · 0 public PoC · 0 EPSS ≥ 0.5
11matches 5protected45.5% 0exploited0.0% 0CISA KEV0.0% 0public PoC0.0% 0EPSS ≥ 0.50.0%
Protected by Waratek 5 45.5% Rule in development 0 0.0% Mitigation candidate 0 0.0% No exploit published 6 54.5%
Critical 2 18.2% High 4 36.4% Medium 5 45.5% Low 0 0.0% None 0 0.0% Unknown 0 0.0%
blocked by ARMR today 5 45.5% partly blocked 0 0.0% not blocked 6 54.5% not established 0 0.0% unrecorded 0 0.0%
Exploited 0 0.0% Working exploit published 0 0.0% Proof of concept only 0 0.0% Forecast only 0 0.0% No public exploit 11 100.0%
split by peak 6 / year
No exploit published: 6Protected by Waratek: 5 Medium: 5High: 4Critical: 2 not blocked: 6blocked by ARMR today: 5 No public exploit: 11
20041 No exploit published1 Medium1 not blocked1 No public exploit1 20050 20060 20070 20080 20090 20100 20110 20120 20130 20140 20150 20160 20170 20180 20190 20200 20210 20226 Protected by Waratek4 No exploit published2 Critical1 High2 Medium3 blocked by ARMR today4 not blocked2 No public exploit6 20231 No exploit published1 Medium1 not blocked1 No public exploit1 20242 Protected by Waratek1 No exploit published1 Critical1 High1 blocked by ARMR today1 not blocked1 No public exploit2 20251 No exploit published1 High1 not blocked1 No public exploit1
20052007200920112013201520172019202120232025
11 matches Sign in to download these CVEs as CSV or JSON, or to follow them in a feed.
CVE Severity Published▾ Status Exploitation Description
CVE-2024-45626 High 2025-02-06 No exploit published No public exploit 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.
CVE-2023-51747 High 2024-02-27 No exploit published No public exploit Apache James prior to versions 3.8.1 and 3.7.5 is vulnerable to SMTP smuggling. A lenient behaviour in line delimiter handling might create a difference of interpretation between the sender and the receiver which can be exploited by an attacker to forge an SMTP envelop, allowing for instance to bypass SPF checks. The patch implies enforcement of CRLF as a line delimiter as part of the DATA transaction. We recommend James users to upgrade to non vulnerable versions.
CVE-2023-51518 Critical 2024-02-27 Protected by Waratek No public exploit 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
CVE-2022-45935 Medium 2023-01-06 No exploit published No public exploit Usage of temporary files with insecure permissions by the Apache James server allows an attacker with local access to access private user data in transit. Vulnerable components includes the SMTP stack and IMAP APPEND command. This issue affects Apache James server version 3.7.2 and prior versions.
CVE-2022-28220 High 2022-09-08 Protected by Waratek No public exploit Apache James prior to release 3.6.3 and 3.7.1 is vulnerable to a buffering attack relying on the use of the STARTTLS command. Fix of CVE-2021-38542, which solved similar problem fron Apache James 3.6.1, is subject to a parser differential and do not take into account concurrent requests.
CVE-2022-22931 Medium 2022-02-07 Protected by Waratek No public exploit Fix of CVE-2021-40525 do not prepend delimiters upon valid directory validations. Affected implementations include: - maildir mailbox store - Sieve file repository This enables a user to access other users data stores (limited to user names being prefixed by the value of the username being used).
CVE-2021-40525 Critical 2022-01-04 Protected by Waratek No public exploit Apache James ManagedSieve implementation alongside with the file storage for sieve scripts is vulnerable to path traversal, allowing reading and writing any file. This vulnerability had been patched in Apache James 3.6.1 and higher. We recommend the upgrade. Distributed and Cassandra based products are also not impacted.
CVE-2021-40111 Medium 2022-01-04 No exploit published No public exploit In Apache James, while fuzzing with Jazzer the IMAP parsing stack, we discover that crafted APPEND and STATUS IMAP command could be used to trigger infinite loops resulting in expensive CPU computations and OutOfMemory exceptions. This can be used for a Denial Of Service attack. The IMAP user needs to be authenticated to exploit this vulnerability. This affected Apache James prior to version 3.6.1. This vulnerability had been patched in Apache James 3.6.1 and higher. We recommend the upgrade.
CVE-2021-40110 High 2022-01-04 No exploit published No public exploit In Apache James, using Jazzer fuzzer, we identified that an IMAP user can craft IMAP LIST commands to orchestrate a Denial Of Service using a vulnerable Regular expression. This affected Apache James prior to 3.6.1 We recommend upgrading to Apache James 3.6.1 or higher , which enforce the use of RE2J regular expression engine to execute regex in linear time without back-tracking.
CVE-2021-38542 Medium 2022-01-04 Protected by Waratek No public exploit Apache James prior to release 3.6.1 is vulnerable to a buffering attack relying on the use of the STARTTLS command. This can result in Man-in -the-middle command injection attacks, leading potentially to leakage of sensible information.
CVE-2004-2650 Medium 2004-12-31 No exploit published No public exploit Spooler in Apache Foundation James 2.2.0 allows local users to cause a denial of service (memory consumption) by triggering various error conditions in the retrieve function, which prevents a lock from being released and causes a memory leak.