Technical impact
The mail-parser library parses emails and produces detailed objects for downstream processing. Prior to version 4.6.2, parsing attacker‑controlled input can trigger uncaught exceptions or silently discard header data. When malformed headers collide with internal methods, objects can be inserted into the parsed output, causing TypeErrors during JSON serialization. Byte‑based input can also produce header objects that raise exceptions when exposed through JSON. In addition, rewritten header names might be omitted from the final output, and a headerless message may be treated as falsy, leading to empty body and attachment fields without an error signal. These situations can abort message handling or conceal malicious indicators from scanning tools. The vulnerability does not provide a direct code‑execution path but results in application crashes or failure to detect threat indicators, effectively disrupting mail processing pipelines or allowing undetected malicious content to pass unseen. The security impact is limited to the service that relies on mail-parser to parse inbound mail. An attacker who can supply malicious email content to the parser can cause the application to crash, leading to a denial‑of‑service that may affect mail delivery or analysis, or can hide malicious headers from downstream scanners.
Affected Systems
The affected vendor is SpamScope. The product is the mail-parser library. Versions prior to 4.6.2 are vulnerable; the fix is available in release 4.6.2 and later.
Risk and Exploitability
The CVSS score of 6.5 classifies the issue as medium severity. EPSS data is not available, and the vulnerability is not listed in the CISA KEV catalog, so the current exploitation probability is unknown. The likely attack vector is the delivery of crafted email messages to the system that uses mail-parser. Because the exception occurs during message parsing and can result in application termination or loss of header data, an attacker could cause a denial‑of‑service condition or conceal malicious indicators from downstream security tools. No authentication bypass or privilege escalation is described, so the scope is limited to the application runtime environment where the library is executed.
Github GHSA