Alerts This Week
Warning Icon 1 727
Alerts This Week
Warning Icon 1 727

Gentoo: GLSA-201311-16 Low Severity fcron Information Exposure

gentoo
Calendar Grey November 25, 2013
Dist Gentoo Esm H88
Malicious users may take advantage of the symlink vulnerabilities in fcron on Gentoo Linux, resulting in unauthorized access to files. Discover further details.
A vulnerability has been found in fcron, allowing local attackers to conduct symlink attacks.

Summary

The fcrontab function contains a race condition relating to symlinks.

Resolution

All fcron users should upgrade to the latest version: # emerge --sync # emerge --ask --oneshot --verbose ">=sys-process/fcron-3.0.5-r2"

References

[ 1 ] CVE-2010-0792 http://nvd.nist.gov/nvd.cfm?cvename=CVE-2010-0792

Availability

This GLSA and any updates to it are available for viewing at the Gentoo Security Website: https://security.gentoo.org/glsa/201311-16
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
low
Lowest
Low
Medium
High
Critical

Severity: Low
Title: fcron: Information disclosure
Date: November 25, 2013
Bugs: #308075
ID: 201311-16

Synopsis

A vulnerability has been found in fcron, allowing local attackers to conduct symlink attacks.

Background

fcron is a periodic command scheduler for Unix-based systems

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 sys-process/fcron < 3.0.5-r2 >= 3.0.5-r2

Impact

===== A local attacker could perform symlink attacks to read arbitrary files with the privileges of the user running the application.

Workaround

There is no known workaround at this time.

Your message here