eml_parser: Algorithmic-complexity DoS (O(n^4) regex backtracking) in Received-header parsing
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| GOVCERT-LU | eml_parser | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Govcert-lu | Eml Parser |
|
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
No EPSS score available.
Key SSVC decision points have not yet been added.
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Govcert-lu
Govcert-lu eml Parser |
|
| Vendors & Products |
Govcert-lu
Govcert-lu eml Parser |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | eml_parser serves as a python module for parsing eml files and returning various information found in the e-mail as well as computed information. In 3.0.3 and earlier, eml_parser.routing.parserouting() in eml_parser/routing.py builds a regular expression with multiple greedy capture groups and appends the npdate date literal extracted from a normalized copy of an attacker-controlled Received header, then searches that expression against the original unnormalized line. A formatting difference can make the trailing literal impossible to match, causing exhaustive backtracking across the greedy groups at each start position. The unsliced Received-header path is invoked by decode_email, decode_email_bytes, and parse_email, so one small unauthenticated message can pin a parser worker and create sustained queue backlog. This issue is fixed in version 3.0.4. | |
| Title | eml_parser: Algorithmic-complexity DoS (O(n^4) regex backtracking) in Received-header parsing | |
| Weaknesses | CWE-1333 CWE-407 |
|
| References |
| |
| Metrics |
cvssV3_1
|