Program crash via freed caller-callee pointer
Published May 18, 2021 · Updated Aug 4, 2024
Use after free in the call function of GNU cflow 1.6 allows local users to crash the program with a crafted C source file during graph generation. Token processing at parser.c line 298 frees the object still referenced by caller->callee, and call later dereferences that dangling pointer. Exploitation requires local execution of cflow against attacker-controlled source and interrupts only that cflow process.
Summary
What happened
Use after free in the call function of GNU cflow 1.6 allows local users to crash the program with a crafted C source file during graph generation. Token processing at parser.c line 298 frees the object still referenced by caller->callee, and call later dereferences that dangling pointer. Exploitation requires local execution of cflow against attacker-controlled source and interrupts only that cflow process.
The record
- CVE
- CVE-2020-23856
- Published
- May 18, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-416
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 18, 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
- PoC_cflow_uaf_parser_line1284proof 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