Skip to main content
ACTIVELY MONITORED//Verified: Nov 16, 2026
Vulnerability WatchGovernance & Policy
6 min read

Rspamd 4.3.0: How to Fix DoS Crashes & DMARC Softening Flaw

•By CyberNewsAI Threat Research Team•VERIFIED INTEL
Rspamd 4.3.0: How to Fix DoS Crashes & DMARC Softening Flaw

SOC Briefing Summary :: Executive Key Takeaways

  • [01]Rspamd 4.3.0 resolves critical denial of service vulnerabilities caused by malformed HTTP headers and empty Deliver-To fields.
  • [02]Fixes a use-after-free memory flaw in the milter proxy (versions 4.0.0 to 4.2.3) that caused double-free crashes upon upstream failures.
  • [03]Addresses an ARC parsing flaw that allowed malicious forwarded emails to soften strict DMARC reject policies and bypass inbound filtering.

Executive Incident Briefing (2-Minute CISO Brief)

Quick Answer (At-A-Glance): The Rspamd open-source email filtering project released version 4.3.0, resolving multiple high-severity vulnerabilities affecting enterprise mail transport agents (MTAs). The release fixes a remote worker crash triggered by a single malformed HTTP header line lacking a colon or an empty Deliver-To header, a use-after-free (UAF) double-free memory corruption flaw in the milter proxy (versions 4.0.0 through 4.2.3), and a critical email authentication bypass where forwarded mail could soften strict DMARC reject policies. Mail administrators and SOC teams running Rspamd alongside Postfix, Sendmail, or Haraka must immediately upgrade to version 4.3.0, audit custom symbol scoring maps, and verify DKIM/SPF configuration strictness.

Rspamd is deployed globally across high-volume internet service providers (ISPs), enterprise mail gateways, and hosting providers to perform spam filtering, anti-phishing inspection, and cryptographic email authentication (SPF, DKIM, DMARC, and ARC). The vulnerabilities addressed in version 4.3.0 present both service availability risks and email spoofing exposure.

  • Software Impacted: Rspamd Mail Filtering System (Versions 4.0.0 through 4.2.3; Milter Proxy and Worker Daemons)
  • Primary Vulnerability Classes: Remote Denial of Service (Malformed HTTP Headers), Use-After-Free Memory Corruption, and Authentication Parsing Bypass (DMARC Policy Softening).
  • Operational Blast Radius: Gateway worker crashes leading to email delivery backlogs, unhandled MTA temporary failures (TEMPFAIL), and inbound spoofed emails evading strict DMARC domain enforcement.
  • Vendor Resolution: Rspamd 4.3.0 release incorporates strict HTTP header validation, atomic milter session teardown, and rigorous ARC chain verification.

Because email gateways constitute perimeter trust anchors, flaws that allow external senders to influence DMARC evaluation directly threaten enterprise brand protection and facilitate Business Email Compromise (BEC) attacks.

Technical Vulnerability Analysis & Attack Chain

Attack Chain Flow
// Attack Chain Flow

Rspamd 4.3.0 remediates three distinct technical flaws across separate architectural modules.

1. HTTP Worker Crash & Malformed Header DoS

The most severe availability flaw permitted an unauthenticated external client or upstream process to crash an Rspamd worker with a single crafted HTTP request:

  • Missing Colon: An HTTP request containing a header line lacking a colon delimiter caused the parsing logic to encounter an unexpected state, immediately halting the active worker daemon.
  • Empty Deliver-To Header: When processing inbound email with an empty Deliver-To: header field, internal pointer arithmetic resulted in an uncaught segmentation fault, repeatedly crashing workers handling queue batches.

2. Milter Proxy Use-After-Free Memory Corruption

In environments deploying the Rspamd milter proxy—the critical interface bridging Rspamd with MTAs such as Postfix and Sendmail—versions 4.0.0 through 4.2.3 contained a double-free memory condition.

  • When an upstream server connection timed out or failed, error-handling routines invoked the session cleanup handler twice.
  • This resulted in code referencing memory blocks that had already been returned to the operating system allocator (use-after-free).
  • In Rspamd 4.3.0, error dispatching has been overhauled to guarantee that each failed transaction receives exactly one TEMPFAIL code and cleans up memory atomically.

3. DMARC Policy Softening via Forged ARC Chains

Authenticated Received Chain (ARC) allows intermediate mail forwarders (e.g., mailing lists, outsourced relay services) to cryptographically vouch for authentication checks passed before forwarding.

  • Prior to 4.3.0, Rspamd allowed subsequent ARC header sets appended after a genuine forwarding signature to improperly alter the final DMARC disposition.
  • Specifically, an attacker could forward an email through an unvalidated relay, append a forged ARC signature set, and cause Rspamd to soften an otherwise strict DMARC reject or quarantine verdict down to a pass.
  • Furthermore, unescaped sender text injected into the Authentication-Results header allowed malicious senders to inject literal dmarc=pass strings into headers read by downstream filtering plugins.

4. Cryptographic Authentication & Behavioral Policy Shifts

Rspamd 4.3.0 introduces significant deliberate behavioral changes:

  • DKIM Enforcement: RSA keys under 1024 bits are now rejected as cryptographically invalid; duplicate DKIM tags are flagged as invalid; and body length parameter l=0 is strictly rejected on non-empty messages.
  • SPF Record Parsing: SPF mechanisms are strictly evaluated in record order, and redirect modifiers are deferred until all mechanisms are completed.
  • Symbol Output Standardization: Plugins including asn, rbl, and dmarc now emit separate symbol options rather than comma-joined strings, requiring adjustments to custom scoring scripts.

MITRE ATT&CK Tactics, Techniques & Procedures (TTPs)

MITRE ATT&CK • OPERATIONAL TTP MAPPING
TacticTechnique IDTechnique NameOperational Context
ImpactT1499.004Application or System ExploitationCrashing Rspamd worker processes via malformed HTTP headers and empty Deliver-To fields.
Initial AccessT1190Exploit Public-Facing ApplicationTriggering milter proxy use-after-free memory corruption during upstream failures.
Initial AccessT1566.002Spearphishing Link / AttachmentBypassing inbound gateway filtering by softening strict DMARC reject policies.
Defense EvasionT1036MasqueradingInjecting forged ARC headers and unescaped dmarc=pass tokens into Authentication-Results.

Detection, Hunting & SOC Mitigation Playbook

1. Immediate Containment Checklist

  • [ ] Upgrade Rspamd packages to version 4.3.0 via distribution package repositories (apt update && apt install rspamd or yum update rspamd).
  • [ ] Restart the Rspamd master daemon and milter proxy services (systemctl restart rspamd).
  • [ ] Audit custom Lua rules and symbol score configurations that parse dmarc, rbl, or asn symbol options to accommodate comma-separated string deprecation.
  • [ ] Verify that DNS maps defining DKIM signing domains use lowercase strings (d= tags) to match case-insensitive normalization.

2. Behavioral Detection Strategy

  • Monitor system service management logs for frequent Rspamd worker respawn events (rspamd_worker: child process terminated on signal 11).
  • Review MTA error logs for unusual spikes in 451 4.7.1 Service unavailable - try again later or milter timeout errors.
  • Audit inbound messages exhibiting discrepant DMARC verdicts between raw SPF/DKIM headers and internal ARC validation tokens.

3. Verification & Diagnostic Audit Checklist

Because this vulnerability involves software parsing errors within mail daemon processes and protocol softening rather than dropped malware binaries, security teams should execute the following diagnostic audit workflow:

QUERY / DETECTION_RULE
BASH / CLI
# 1. Verify Installed Rspamd Version
rspamc --version
# Output must indicate Rspamd 4.3.0 or later

# 2. Inspect Worker Health and Core Dumps
systemctl status rspamd
journalctl -u rspamd --since "24 hours ago" | grep -E "segmentation fault|terminated on signal|core dumped"

# 3. Check Milter Proxy Socket Status
rspamc stat | grep -E "Workers|Connections|Stat"

# 4. Audit DKIM Domain Maps for Mixed-Case Entries
grep -rn "[A-Z]" /etc/rspamd/local.d/dkim_signing.conf /etc/rspamd/local.d/maps.d/dkim_domains.map 2>/dev/null || echo "Maps are properly lowercased"

# 5. Test Live Message Processing
rspamc < /usr/share/doc/rspamd/examples/test_message.eml

4. Enterprise Hardening & Long-Term Resilience

  1. Strict MTA DMARC Alignment: Configure MTAs to validate DMARC at the perimeter boundary, enforcing strict alignment on root domains.
  2. Minimum Cryptographic Key Lengths: Deprecate all 1024-bit DKIM keys across outbound enterprise domains, transitioning immediately to 2048-bit RSA or Ed25519 signing keys.
  3. MTA Worker Memory Sandboxing: Enforce systemd service isolation for Rspamd using PrivateTmp=yes, ProtectSystem=strict, and MemoryLimit guards to prevent runaway memory leaks from crashing host MTAs.

Indicators of Compromise (IOCs)

No technical Indicators of Compromise (IOCs) are associated with this vendor software release and advisory.

---

Related Topic Cluster Intelligence

SHARE INTEL:Reddit