Overview 8 matches · 5 protected · 0 exploited · 0 CISA KEV · 1 public PoC · 1 EPSS ≥ 0.5
Protected by Waratek
5
62.5%
Rule in development
0
0.0%
Mitigation candidate
0
0.0%
No exploit published
3
37.5%
blocked by ARMR today
5
62.5%
partly blocked
0
0.0%
not blocked
3
37.5%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
0
0.0%
Working exploit published
1
12.5%
Proof of concept only
0
0.0%
Forecast only
0
0.0%
No public exploit
7
87.5%
split by
peak 5 / year
20041
No exploit published1
Medium1
not blocked1
No public exploit1
20050
20060
20070
20080
20090
20100
20110
20120
20130
20140
20150
20161
Protected by Waratek1
High1
blocked by ARMR today1
Working exploit published1
20171
Protected by Waratek1
High1
blocked by ARMR today1
No public exploit1
20180
20190
20200
20210
20225
Protected by Waratek3
No exploit published2
Critical1
High1
Medium3
blocked by ARMR today3
not blocked2
No public exploit5
2004200620082010201220142016201820202022
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| 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-2017-12628 | High | 2017-10-20 | Protected by Waratek | No public exploit | 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. |
| CVE-2015-7611 | High | 2016-06-07 | Protected by Waratek | Working exploit published | Apache James Server 2.3.2, when configured with file-based user repositories, allows attackers to execute arbitrary system commands via unspecified vectors. |
| 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. |