CVE-2021-40111 json
Apache James IMAP parsing Denial Of Service
published 4y ago modified last mo. also GHSA-fqgw-6qj5-8hmp , EUVD-2022-0588
- cvss
- 6.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.2%
- EPSS 2.2% chance of exploitation in 30 days, percentile 82%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- maven org.apache.james:james-server 3.6.1
- apache james 3.6.1
Is CVE-2021-40111 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
2.19% chance of exploitation in the next 30 days, higher than 82% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
| NVD | 2.0 | 4.0 | AV:N/AC:L/Au:S/C:N/I:N/A:P |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.apache.james:james-server | <3.6.1 |
3.6.1 |
Affected products
- Apache Software Foundation Apache James
Classification
- Weakness
-
- CWE-835 Loop with Unreachable Exit Condition
References
-
openwall.com
/lists/oss-security/2022/01/04/3
web, mailing-list, third-party-advisory
-
openwall.com
/lists/oss-security/2022/01/04/3
mailing-list, web, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2021-40111
advisory
Sources
- CVE List CVE-2021-40111
- GitHub Advisory GHSA-fqgw-6qj5-8hmp
- NVD CVE-2021-40111
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.