LiveActive security incident?Get immediate response
CVE Record

CVE-2016-20042: TRN 3.6-23 Stack Buffer Overflow Local Code Execution

TRN 3.6-23 contains a stack buffer overflow vulnerability that allows local attackers to execute arbitrary code by supplying an oversized argument to the application. Attackers can craft a malicious command-line argument with 156 bytes of padding followed by a return address to overwrite the instruction pointer and execute shellcode with user privileges.

HighCVSS 8.6Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2016-20042 is a high-severity local stack buffer overflow in TRN 3.6-23, the Threaded USENET News Reader. A local attacker who can run the application may be able to execute code with that user's privileges by supplying an oversized command-line argument.

Executive priority

Treat as high priority for shared Linux/Unix systems, shell servers, development hosts, and any environment where untrusted local users can execute installed utilities. For single-user systems with no TRN installation, priority is low after inventory confirms non-exposure.

Technical view

The source bundle describes a CWE-787 out-of-bounds write affecting trn Threaded USENET News Reader version 3.6-23. The vulnerability is local-only per the CVSS vector and supplied description, with low attack complexity and no required privileges or user interaction in the CVSS assessment. Impact is listed as high for confidentiality, integrity, and availability within the vulnerable system context.

Likely exposure

Exposure is most likely on systems where TRN 3.6-23 is installed and local users, scripts, or job runners can invoke it. The bundle does not indicate network-reachable exploitation. Remote exposure should only be considered if a local wrapper, automation path, or service invokes TRN with attacker-controlled arguments.

Exploitation context

The bundle includes an ExploitDB reference tagged as an exploit, so public exploit material is referenced. However, KEV is false and no provided source states active exploitation in the wild. The described impact is local code execution with the privileges of the user running TRN.

Researcher notes

Assessment is limited to the provided source bundle. No active exploitation is claimed because KEV is false and the bundle does not state exploitation in the wild. No fixed version is listed in the bundle, so remediation should be validated against vendor or package maintainer guidance.

Mitigation direction

  • Inventory systems for TRN 3.6-23 and prioritize removal, replacement, or isolation where it is present.
  • Check vendor, project, OS distribution, or package maintainer guidance for an official fixed release or backported patch; the source bundle does not provide patch evidence.
  • Restrict local access to systems where the vulnerable binary remains installed, especially shared shell hosts and multi-user servers.
  • Avoid invoking TRN from scripts, services, mail/news workflows, or automation paths that could pass attacker-controlled arguments.
  • Where removal is not immediately possible, apply normal platform hardening and monitoring controls, including least-privilege execution and process/audit monitoring for unexpected TRN use.

Validation and detection

  • Confirm whether TRN is installed and whether the installed version is 3.6-23.
  • Confirm whether any users, cron jobs, services, or operational workflows can execute TRN.
  • Review whether any wrapper or integration passes untrusted input to TRN as command-line arguments.
  • Check official project, distribution, or package maintainer advisories for fixed package availability before declaring remediation complete.
  • Document affected hosts, mitigation status, and any exception where TRN must remain installed.
Prepared
Confidence
high
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-787: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2016-20042 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.6 (4.0)
Known Exploited
No
Published

Vector: CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.6CVSS 4.0HighCVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:NPrimary CVE score

Vulnerability scoring details

Base CVSS 4.0 score

8.6High
CVSS 4.0 vector shape for CVE-2016-20042Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
trnThreaded USENET News Reader3.6-23Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-787 · source CWE mapping

Out-of-bounds Write

Out-of-bounds Write represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.