Client crash via uninitialized logging argument
Published Jul 29, 2021 · Updated Aug 4, 2024
Improper initialization in Fetchmail 6.3.8 and earlier and 6.3.17 through 6.4.19 allows remote attackers to crash the client. During long-message buffer reallocation, report_vbuild passes vsnprintf a va_list that has not been reinitialized, causing reads from invalid memory. Long server-supplied headers must trigger the path; results depend on the platform and configuration and include garbage logging, data exposure, or stalled mail retrieval after a crash.
Summary
What happened
Improper initialization in Fetchmail 6.3.8 and earlier and 6.3.17 through 6.4.19 allows remote attackers to crash the client. During long-message buffer reallocation, report_vbuild passes vsnprintf a va_list that has not been reinitialized, causing reads from invalid memory. Long server-supplied headers must trigger the path; results depend on the platform and configuration and include garbage logging, data exposure, or stalled mail retrieval after a crash.
The record
- CVE
- CVE-2021-36386
- Published
- Jul 29, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-665, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 29, 2021CVE 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
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