1 line
6.7 KiB
JSON
1 line
6.7 KiB
JSON
{"schema_version":"1.9.2","id":"GHSA-24mq-4vc6-2prf","published":"2026-11-16T22:12:51Z","modified":"2026-11-16T22:30:03.917752741Z","aliases":["CVE-2026-129299"],"summary":"mail-parser: Uncaught exceptions and silent header loss in mail-parser on attacker-controlled input","details":"### Impact\n\nTwo effects, sharing the root cause of Advisory 1 — header names chosen by the sender were\nresolved through Python attribute lookup and rewritten before lookup.\n\n**Uncaught exceptions.** A crafted message raises an exception that is *outside* the\n`MailParser*` hierarchy, so a caller catching only mail-parser exceptions does not catch it\nand the worker dies.\n\n*Header named after a method* (CWE-248, reported by @iam-niranjan). Python resolves real\nclass attributes before `__getattr__`, so a header named after a method put a bound method\nobject into the parsed mail dict. A 12-byte email is sufficient. Nine colliding names were\nconfirmed: `Parse`, `Message`, `Write_Attachments`, `From_File`, `From_File_Obj`,\n`From_File_Msg`, `From_String`, `From_Bytes`, `Get_Server_Ipaddress`. Also reproducible from\nthe CLI (`mail-parser -f evil.eml -j`).\n\n```python\nimport mailparser\nmailparser.parse_from_string(\"Parse: x\\r\\n\\r\\n\").mail_json\n# 4.6.1 -> TypeError: Object of type method is not JSON serializable\n# 4.6.2 -> {\"parse\": \"x\", \"has_defects\": false}\n```\n\n*Header carrying 8-bit bytes* (CWE-248). For a header containing raw 8-bit bytes, Python's\n`compat32` policy returns an `email.header.Header` rather than a `str`, which the `_raw`\naccessor passed straight to `json.dumps`. This fires on entirely benign non-ASCII mail via\n`parse_from_bytes()`, the normal entry point for mail off the wire.\n\n```python\nimport mailparser\nmailparser.parse_from_bytes(b\"Subject: caf\\xe9\\r\\n\\r\\nbody\\r\\n\").subject_raw\n# 4.6.1 -> TypeError: Object of type Header is not JSON serializable\n# 4.6.2 -> '[\"caf�\"]'\n```\n\n**Silent loss of message content** (CWE-436). A sender can make a header's value vanish from\nevery output surface, or be replaced by a different header's value, with `has_defects`\nremaining `false`. This is an evasion primitive: the tool's output diverges from the bytes\nactually in the message, and a pipeline scanning parsed output for indicators sees nothing\nand no failure signal.\n\nHeader names were normalised before lookup — underscores folded to dashes, and `_json` /\n`_raw` suffixes interpreted — so a header genuinely named `Subject_json` was reported with\nthe value of `Subject` and its own value discarded, and any header whose name contains an\nunderscore resolved to nothing.\n\n```python\nimport mailparser\n\nraw = (\"From: Real Sender <real@good.example>\\r\\n\"\n \"Subject: innocuous\\r\\n\"\n \"Subject_json: MALWARE-C2 http://evil.example/payload.exe\\r\\n\"\n \"X_Spam_Flag: YES\\r\\n\\r\\nbody\\r\\n\")\nmail = mailparser.parse_from_string(raw)\nprint(mail.mail[\"subject_json\"]) # 4.6.1 -> '\"innocuous\"' 4.6.2 -> the real value\nprint(mail.headers[\"X_Spam_Flag\"]) # 4.6.1 -> '' 4.6.2 -> 'YES'\nprint(\"MALWARE-C2\" in mail.mail_json) # 4.6.1 -> False 4.6.2 -> True\nprint(mail.has_defects) # both -> False\n```\n\nA related case: `email.message.Message.__len__` returns the header count, so a message with\n**no headers** is falsy. `parse()` returned before initialising state, and the unset\nattributes were then absorbed by `__getattr__` and answered as absent headers. Every\nproperty returned `''` — including `mail` and `attachments`, which are documented to return\na `dict` and a `list` — with no error and no defect flag.\n\n```python\nimport mailparser\nmail = mailparser.parse_from_string(\"Click http://evil.example/pay.exe now\\r\\n\")\nprint(repr(mail.body)) # 4.6.1 -> '' 4.6.2 -> the text\nprint(repr(mail.attachments)) # 4.6.1 -> '' 4.6.2 -> []\nprint(mail.has_defects) # 4.6.1 -> '' 4.6.2 -> True\n```\n\n### Patches\n\nFixed in **4.6.2**. Upgrade with `pip install --upgrade mail-parser`.\n\nHeader names taken from a message are now looked up literally — no attribute access, no\ncase or separator folding, no suffix interpretation — so no header name can collide with a\nmethod or property, and no value can be substituted or dropped. 8-bit values are coerced to\n`str` before serialisation. Parser state is initialised before the message check, which now\ntests `is None`, and attribute names beginning with `_` raise `AttributeError` instead of\nbeing answered as headers.\n\n**Behaviour changes.** Header names now appear in `mail` and `headers` exactly as sent, so a\nheader named `X_Spam_Flag` keeps that name and its own value. `X_raw` always returns a JSON\narray — an absent header yields `[]` where 4.6.1 returned `null`.\n\n### Workarounds\n\nNone for the data loss. For the uncaught exceptions, callers who cannot upgrade should wrap\n`mail_json`, `mail_partial_json`, `headers_json` and any `X_raw` access in a bare\n`except Exception` rather than catching only `MailParserError` subclasses.","affected":[{"package":{"name":"mail-parser","ecosystem":"PyPI","purl":"pkg:pypi/mail-parser"},"ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.6.2"}]}],"versions":["0.5.0","1.0.0","1.0.0rc1","1.1.0","1.1.1","1.1.10","1.1.2","1.1.3","1.1.4","1.1.5","1.1.6","1.1.7","1.1.8","1.1.9","1.2.0","1.2.1","1.2.2","1.2.4","1.2.5","1.2.6","2.0.0","2.0.1","2.1.0","3.0.0","3.1.0","3.10.0","3.11.0","3.12.0","3.13.0","3.14.0","3.15.0","3.2.0","3.2.1","3.2.2","3.2.3","3.2.4","3.2.5","3.2.6","3.2.7","3.3.0","3.3.1","3.3.2","3.3.3","3.4.0","3.4.1","3.5.0","3.5.1","3.6.0","3.6.1","3.7.0","3.7.1","3.8.0","3.8.1","3.9.0","3.9.1","3.9.2","3.9.3","4.0.0","4.1.0","4.1.2","4.1.3","4.1.4","4.2.0","4.2.1","4.3.0","4.4.0","4.5.0","4.6.0","4.6.1"],"database_specific":{"last_known_affected_version_range":"<= 4.6.1","source":"https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2026/11/GHSA-24mq-4vc6-2prf/GHSA-24mq-4vc6-2prf.json"}}],"references":[{"type":"WEB","url":"https://github.com/SpamScope/mail-parser/security/advisories/GHSA-24mq-4vc6-2prf"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-129299"},{"type":"WEB","url":"https://github.com/SpamScope/mail-parser/pull/167"},{"type":"WEB","url":"https://github.com/SpamScope/mail-parser/commit/ce3cf3559db1ff806bda598b378de9f8c2a5be96"},{"type":"PACKAGE","url":"https://github.com/SpamScope/mail-parser"},{"type":"WEB","url":"https://github.com/SpamScope/mail-parser/releases/tag/4.6.2"}],"database_specific":{"cwe_ids":["CWE-248","CWE-436"],"github_reviewed":true,"github_reviewed_at":"2026-11-16T22:12:51Z","nvd_published_at":"2026-11-16T18:17:30Z","severity":"MODERATE"},"severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L"}]} |