Alerts This Week
Warning Icon 1 764
Alerts This Week
Warning Icon 1 764

Gentoo GLSA-201804-18 Normal: Tenshi Privilege Escalation Risk

gentoo
Calendar Grey April 22, 2018
Dist Gentoo Esm H88
Gentoo GLSA-202104-27 outlines a security vulnerability in the ninja's build scripts that arises from incorrect file permission settings.
Gentoo's tenshi ebuild is vulnerable to privilege escalation due to the way pid files are handled.

Summary

It was discovered that the tenshi ebuild creates a tenshi.pid file after dropping privileges to a non-root account.

Resolution

All tenshi users should upgrade to the latest version: # emerge --sync # emerge --ask --oneshot --verbose ">=app-admin/tenshi-0.17"

References

[ 1 ] CVE-2017-11746 https://nvd.nist.gov/vuln/detail/CVE-2017-11746

Availability

This GLSA and any updates to it are available for viewing at the Gentoo Security Website: https://security.gentoo.org/glsa/201804-18
style>.gentoo_availability{display:block;}

Concerns

Security is a primary focus of Gentoo Linux and ensuring the confidentiality and security of our users' machines is of utmost importance to us. Any security concerns should be addressed to security@gentoo.org or alternatively, you may file a bug at https://bugs.gentoo.org.

Severity: Normal
Title: tenshi: Privilege escalation
Date: April 22, 2018
Bugs: #626654
ID: 201804-18

Synopsis

Gentoo's tenshi ebuild is vulnerable to privilege escalation due to the way pid files are handled.

Background

A log monitoring program, designed to watch one or more log files for lines matching user defined regular expressions and report on the matches.

Get the latest News and Insights

Get the latest Linux and open source security news straight to your inbox.

Affected Packages

------------------------------------------------------------------- Package / Vulnerable / Unaffected ------------------------------------------------------------------- 1 app-admin/tenshi < 0.17 >= 0.17

Impact

===== A local attacker could escalate privileges to root or kill arbitrary processes.

Workaround

There is no known workaround at this time.

Your message here