ghsa-fqgw-6qj5-8hmp
Vulnerability from github
Published
2022-01-08 00:40
Modified
2022-01-07 18:33
Summary
Infinite Loop in Apache James
Details
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.
{ "affected": [ { "package": { "ecosystem": "Maven", "name": "org.apache.james:james-server" }, "ranges": [ { "events": [ { "introduced": "0" }, { "fixed": "3.6.1" } ], "type": "ECOSYSTEM" } ] } ], "aliases": [ "CVE-2021-40111" ], "database_specific": { "cwe_ids": [ "CWE-835" ], "github_reviewed": true, "github_reviewed_at": "2022-01-07T18:33:44Z", "nvd_published_at": "2022-01-04T09:15:00Z", "severity": "MODERATE" }, "details": "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.", "id": "GHSA-fqgw-6qj5-8hmp", "modified": "2022-01-07T18:33:44Z", "published": "2022-01-08T00:40:37Z", "references": [ { "type": "ADVISORY", "url": "https://nvd.nist.gov/vuln/detail/CVE-2021-40111" }, { "type": "WEB", "url": "https://www.openwall.com/lists/oss-security/2022/01/04/3" }, { "type": "WEB", "url": "http://www.openwall.com/lists/oss-security/2022/01/04/3" } ], "schema_version": "1.4.0", "severity": [], "summary": "Infinite Loop in Apache James" }
Loading…
Loading…
Sightings
Author | Source | Type | Date |
---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.