Client crash via repeated finalized MIME processing
Published Mar 2, 2020 · Updated Aug 4, 2024
NULL pointer dereference in Thunderbird before 68.5 allows remote attackers to crash the client via a message containing multiple S/MIME signatures. MimeMultipartSigned_emit_child processes the same MIME object twice, and MimeObject_write later dereferences its cleared state pointer. Opening the crafted message is required; the resulting availability impact is limited to an unexploitable client crash.
Summary
What happened
NULL pointer dereference in Thunderbird before 68.5 allows remote attackers to crash the client via a message containing multiple S/MIME signatures. MimeMultipartSigned_emit_child processes the same MIME object twice, and MimeObject_write later dereferences its cleared state pointer. Opening the crafted message is required; the resulting availability impact is limited to an unexploitable client crash.
The record
- CVE
- CVE-2020-6795
- Published
- Mar 2, 2020
- Updated
- Aug 4, 2024
- Vendor
- Mozilla
- Product
- Thunderbird
- Classifications
- CWE-476, T1204.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 2, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 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=unspecified <68.5
What conditions does exploitation require?
What is affected?
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
- Mozilla multi-signature S/MIME EML reproducerproof of concept · demonstrated
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