Memory disclosure via uninitialized header start offset
Published Mar 2, 2020 · Updated Aug 4, 2024
Out-of-bounds read in Thunderbird before 68.5 allows remote attackers to disclose process memory through a crafted email message. nsParseMailMessageState::FinalizeHeaders leaves m_headerstartpos uninitialized when the envelope position is zero, then uses that offset during header-buffer processing. A recipient must interact with the crafted message; the documented consequence is memory disclosure, with no integrity or availability impact.
Summary
What happened
Out-of-bounds read in Thunderbird before 68.5 allows remote attackers to disclose process memory through a crafted email message. nsParseMailMessageState::FinalizeHeaders leaves m_headerstartpos uninitialized when the envelope position is zero, then uses that offset during header-buffer processing. A recipient must interact with the crafted message; the documented consequence is memory disclosure, with no integrity or availability impact.
The record
- CVE
- CVE-2020-6793
- Published
- Mar 2, 2020
- Updated
- Aug 4, 2024
- Vendor
- Mozilla
- Product
- Thunderbird
- Classifications
- CWE-125
- 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.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
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