Mail-filter crash via null buffer memset
Published Feb 26, 2024 · Updated Oct 29, 2024
Null pointer dereference in OpenDMARC 1.4.2 allows remote attackers to crash the mail filter through processed DMARC policy data. In opendmarc_policy.c, a positive buffer size can reach memset with list_buf set to NULL, causing a dereference at line 1480. Reachability requires the filter to process the triggering policy state; the published report establishes a crash, not code execution or data access.
Summary
What happened
Null pointer dereference in OpenDMARC 1.4.2 allows remote attackers to crash the mail filter through processed DMARC policy data. In opendmarc_policy.c, a positive buffer size can reach memset with list_buf set to NULL, causing a dereference at line 1480. Reachability requires the filter to process the triggering policy state; the published report establishes a crash, not code execution or data access.
The record
- CVE
- CVE-2024-25768
- Published
- Feb 26, 2024
- Updated
- Oct 29, 2024
- Vendor
- The Trusted Domain Project
- Product
- OpenDMARC
- Classifications
- CWE-476, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 26, 2024CVE publishedPublication date reported by the CVE source.
- Oct 29, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.4.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- OpenDMARC_detect_1 crash demonstrationproof of concept · unverified
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo