Security readout for executives and security teams
Plain-English summary
Tenshi 0.15 can create a PID file after dropping from root to a lower-privileged account. If a local user can modify that file, a later root script may kill a process ID chosen by that user. This is a local operational risk, not evidence of remote compromise.
Executive priority
Treat as a targeted hardening issue for legacy hosts. Prioritize if Tenshi runs on shared systems, multi-user servers, or hosts where service-account compromise is plausible.
Technical view
The issue is a PID-file trust problem in Tenshi 0.15. A non-root-writable tenshi.pid can be altered before a root-level script runs a kill command using that file contents, potentially terminating arbitrary local processes. The source bundle provides no CVSS, CWE, or fixed-version details.
Likely exposure
Exposure appears limited to systems running Tenshi 0.15 with local users or compromised service-account access able to modify tenshi.pid before a privileged script consumes it.
Exploitation context
The provided sources do not show active exploitation, and KEV is false. Exploitation requires local access or control of the non-root account/path that can modify the PID file.
Researcher notes
Evidence is sparse: the CVE description defines the unsafe sequence, Gentoo advisory and upstream issue are cited, but no CVSS, CWE, exploit activity, or fixed version is included in the bundle.
Mitigation direction
- Check Gentoo GLSA-201804-18 and upstream issue 6 for vendor remediation guidance.
- Inventory systems for Tenshi 0.15 and related service scripts.
- Prevent untrusted users from modifying the Tenshi service account or PID file path.
- Avoid root scripts that trust a PID file writable by a non-root account.
Validation and detection
- Identify any installed Tenshi version and confirm whether it is 0.15.
- Review ownership and permissions for tenshi.pid and its containing directory.
- Find root-run scripts that execute kill based on tenshi.pid contents.
- Confirm whether local users can access the Tenshi account or PID path.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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.
CVE-2017-11746 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
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.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- GLSA-201804-18CVE reference · vendor-advisory, x_refsource_GENTOO
- https://github.com/inversepath/tenshi/issues/6CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.