Process crash via malformed include argument
Published Mar 16, 2023 · Updated Feb 26, 2025
NULL pointer dereference in TCPprep 4.4.3 allows attackers to crash tcpprep via a malformed --include command-line argument. parse_list passes a null string produced from a two-character include value to regexec at list.c:81 instead of rejecting the invalid token. The attacker must cause tcpprep to run with the crafted value; successful exploitation terminates that process with SIGSEGV.
Summary
What happened
NULL pointer dereference in TCPprep 4.4.3 allows attackers to crash tcpprep via a malformed --include command-line argument. parse_list passes a null string produced from a two-character include value to regexec at list.c:81 instead of rejecting the invalid token. The attacker must cause tcpprep to run with the crafted value; successful exploitation terminates that process with SIGSEGV.
The record
- CVE
- CVE-2023-27787
- Published
- Mar 16, 2023
- Updated
- Feb 26, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-476, T1499.004
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 16, 2023CVE publishedPublication date reported by the CVE source.
- Feb 26, 2025Record 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 --include argument 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