Rspamd 4.3.0 fixes unauthenticated worker crashes, milter proxy use-after-free and forged ARC/Authentication-Results handling
Rspamd 4.3.0 fixes bugs that let an unauthenticated attacker crash the spam filter's workers or slip forged authentication results through it. One HTTP request with a header line lacking a colon could stop a worker, and an empty Deliver-To header could crash workers repeatedly. The release also fixes a use-after-free in the milter proxy (4.0.0 through 4.2.3), where a session was released twice when an upstream failed. Version 3.14 is not affected. The article gives no CVE IDs, CVSS scores or exploitation-in-the-wild information, and no vendor advisory was researched, so urgency rests on the article alone.
Detalhes técnicos
- Crash bugs: a header line without a colon and an empty Deliver-To header, both triggerable by an unauthenticated attacker.
- Milter proxy double release on upstream failure (use-after-free), 4.0.0 to 4.2.3. In 4.3.0 each failed message gets exactly one TEMPFAIL.
- ARC sets added after a genuine one could soften a DMARC reject. Rspamd now trusts a forwarder only for what it vouched for and requires the forwarder's own dmarc=pass.
- Sender text went unescaped into the Authentication-Results header, so a sender could inject dmarc=pass and have it read as a real result.
Remediação
Upgrade to Rspamd 4.3.0. Behavior changes will shift verdicts: SPF term order and redirects, DKIM rejecting RSA keys under 1024 bits, duplicate tags and l=0 on messages with a body, URL mismatch scoring separated from phishing scoring, and separate symbol options in the asn, rbl and dmarc plugins. DKIM d= values are now lowercased. Test local scores, scripts and domain maps before rollout.
Linha do tempo
-
Rspamd 4.3.0 fixes unauthenticated worker crashes, milter proxy use-after-free and forged ARC/Authentication-Results handling
ler a análise desta fonte ocultar
Rspamd 4.3.0 fixes bugs that let an unauthenticated attacker crash the spam filter's workers or slip forged authentication results through it. One HTTP request with a header line lacking a colon could stop a worker, and an empty Deliver-To header could crash workers repeatedly. The release also fixes a use-after-free in the milter proxy (4.0.0 through 4.2.3), where a session was released twice when an upstream failed. Version 3.14 is not affected. The article gives no CVE IDs, CVSS scores or exploitation-in-the-wild information, and no vendor advisory was researched, so urgency rests on the article alone.
Technical Details
- Crash bugs: a header line without a colon and an empty Deliver-To header, both triggerable by an unauthenticated attacker.
- Milter proxy double release on upstream failure (use-after-free), 4.0.0 to 4.2.3. In 4.3.0 each failed message gets exactly one TEMPFAIL.
- ARC sets added after a genuine one could soften a DMARC reject. Rspamd now trusts a forwarder only for what it vouched for and requires the forwarder's own dmarc=pass.
- Sender text went unescaped into the Authentication-Results header, so a sender could inject dmarc=pass and have it read as a real result.
Remediation
Upgrade to Rspamd 4.3.0. Behavior changes will shift verdicts: SPF term order and redirects, DKIM rejecting RSA keys under 1024 bits, duplicate tags and l=0 on messages with a body, URL mismatch scoring separated from phishing scoring, and separate symbol options in the asn, rbl and dmarc plugins. DKIM d= values are now lowercased. Test local scores, scripts and domain maps before rollout.