Document-processor crash via double-free cleanup
Published May 24, 2022 · Updated Aug 4, 2024
Double free in cleanup_index in Halibut 1.2 allows attackers to crash the document processor via a crafted text document. The published analysis traces the second deallocation through free_word_list at index.c line 203 and identifies earlier frees of rsc.text in get_token as the root cause. Exploitation requires a user or automated workflow to process the malicious file with the WinHelp backend; the demonstrated consequence is an abort and service interruption.
Summary
What happened
Double free in cleanup_index in Halibut 1.2 allows attackers to crash the document processor via a crafted text document. The published analysis traces the second deallocation through free_word_list at index.c line 203 and identifies earlier frees of rsc.text in get_token as the root cause. Exploitation requires a user or automated workflow to process the malicious file with the WinHelp backend; the demonstrated consequence is an abort and service interruption.
The record
- CVE
- CVE-2021-42613
- Published
- May 24, 2022
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-415, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 24, 2022CVE 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
- Halibut WinHelp double-free proof of conceptproof 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