Document processor crash via freed token text
Published May 24, 2022 · Updated Aug 4, 2024
Use-after-free in Halibut 1.2 allows local users to crash the document processor by opening a crafted text document. During tokenization, get_token frees resource text on brace and pushback paths, while the Info backend later traverses stale word data in info_width_internal. The published proof of concept requires the crafted file to be processed with the Info backend and ends in a segmentation fault; other impact remains unspecified.
Summary
What happened
Use-after-free in Halibut 1.2 allows local users to crash the document processor by opening a crafted text document. During tokenization, get_token frees resource text on brace and pushback paths, while the Info backend later traverses stale word data in info_width_internal. The published proof of concept requires the crafted file to be processed with the Info backend and ends in a segmentation fault; other impact remains unspecified.
The record
- CVE
- CVE-2021-42614
- Published
- May 24, 2022
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-416, T1204.002
- 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
- poc-halibut-info-uafproof 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