Local code execution via oversized command-line argument
Published Mar 28, 2026 · Updated Mar 28, 2026
Stack buffer overflow in The Trn Project trn 3.6-23 allows local users to execute arbitrary code via an oversized command-line argument. Processing the oversized command-line argument overflows a stack buffer; after 156 padding bytes, attacker-controlled data reaches the saved instruction pointer. Local access sufficient to start trn is required, and successful exploitation runs shellcode with the invoking user's privileges.
Summary
What happened
Stack buffer overflow in The Trn Project trn 3.6-23 allows local users to execute arbitrary code via an oversized command-line argument. Processing the oversized command-line argument overflows a stack buffer; after 156 padding bytes, attacker-controlled data reaches the saved instruction pointer. Local access sufficient to start trn is required, and successful exploitation runs shellcode with the invoking user's privileges.
The record
- CVE
- CVE-2016-20042
- Published
- Mar 28, 2026
- Updated
- Mar 28, 2026
- Vendor
- The Trn Project
- Product
- trn
- Classifications
- CWE-787, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 28, 2026CVE publishedPublication date reported by the CVE source.
- Mar 28, 2026Record 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3.6-23
What conditions does exploitation require?
What is affected?
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
- TRN Threaded USENET News Reader 3.6-23 Local Stack Overflowproof 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