Utility crash via double free in another_hunk
Published Mar 25, 2020 · Updated Aug 5, 2024
Double free in GNU patch 2.7.6 and earlier allows local users to crash the utility by supplying a crafted patch file. In another_hunk in pch.c, crafted context-format input drives the cleanup loop to call free(p_line[p_end]) twice for the same allocation. Execution requires a user or automated workflow to process the malicious file; the documented consequence is a process crash, not code execution.
Summary
What happened
Double free in GNU patch 2.7.6 and earlier allows local users to crash the utility by supplying a crafted patch file. In another_hunk in pch.c, crafted context-format input drives the cleanup loop to call free(p_line[p_end]) twice for the same allocation. Execution requires a user or automated workflow to process the malicious file; the documented consequence is a process crash, not code execution.
The record
- CVE
- CVE-2019-20633
- Published
- Mar 25, 2020
- Updated
- Aug 5, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-415
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 25, 2020CVE publishedPublication date reported by the CVE source.
- Aug 5, 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.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
- UAFuzz proof-of-concept patch inputproof 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