Process crash via uninitialized pointers in another_hunk
Published Dec 22, 2021 · Updated Aug 4, 2024
Invalid-pointer handling in GNU patch 2.7 allows context-dependent attackers to crash the utility with a malformed patch file. In src/pch.c, another_hunk leaves p_line entries uninitialized before cleanup passes their invalid values to free. Exploitation requires a user to invoke the command-line tool on attacker-controlled input; the observed consequence is a segmentation fault confined to that process.
Summary
What happened
Invalid-pointer handling in GNU patch 2.7 allows context-dependent attackers to crash the utility with a malformed patch file. In src/pch.c, another_hunk leaves p_line entries uninitialized before cleanup passes their invalid values to free. Exploitation requires a user to invoke the command-line tool on attacker-controlled input; the observed consequence is a segmentation fault confined to that process.
The record
- CVE
- CVE-2021-45261
- Published
- Dec 22, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-763, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 22, 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.
Weakness, pattern, technique
Public exploit references
- Malformed patch-file crash reproducerproof 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