First published: Mon Nov 25 2013(Updated: )
Augeas upstream commit 051c73a9: <a href="https://github.com/hercules-team/augeas/commit/051c73a9">https://github.com/hercules-team/augeas/commit/051c73a9</a> introduced a flaw in the way Augeas sets permissions on newly created files. The above commit aims to address a regression introduced in the fix for <a href="https://access.redhat.com/security/cve/CVE-2012-0786">CVE-2012-0786</a> (see <a class="bz_bug_link bz_status_CLOSED bz_closed bz_public " title="CLOSED ERRATA - CVE-2012-0786 augeas: susceptible to symlink attack" href="show_bug.cgi?id=772257#c39">bug 772257 comment 39</a>), which introduced a use of mkstemp() to create new files. mkstemp() always sets 0600 file permissions regardless of the current umask setting. Commit 051c73a9 attempts to fix file permissions based on umask setting, but it does not correctly handle certain umask values, causing Augeas to make newly created files world writable. A local user could possibly use this flaw to modify configuration files created by an application using Augeas.
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
Augeas Augeas | =1.0.0 | |
Augeas Augeas | =1.1.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.