First published: Sun Feb 27 2011(Updated: )
It was found that logrotate utility used insecure default permissions, when creating of new files (time-of-check, time-of-use, TOCTOU race condition). In some specific configurations, a local attacker could use this flaw to open the new file before the final permissions have been applied, leading to disclosure of sensitive information.
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
Logrotate | =3.6.5 | |
Logrotate | =3.7.8 | |
Logrotate | =3.5.9-r1 | |
Logrotate | =3.7.6 | |
Logrotate | =3.3-r2 | |
Logrotate | =3.7.2 | |
Logrotate | =3.7 | |
Logrotate | =3.7.1-r2 | |
Logrotate | =3.6.5-r1 | |
Logrotate | =3.5.9 | |
Logrotate | =3.7.1-r1 | |
Logrotate | <=3.7.9 | |
Logrotate | =3.7.1 | |
Logrotate | =3.7.7 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2011-1098 has a medium severity rating due to its potential to allow local attackers to exploit a TOCTOU race condition.
To fix CVE-2011-1098, update the logrotate utility to a patched version or adjust file permissions to prevent race conditions.
CVE-2011-1098 affects multiple versions of logrotate including 3.3, 3.5.9, 3.6.5, and various 3.7.x versions.
Users with vulnerable logrotate configurations, particularly in unsecure environments, are impacted by CVE-2011-1098.
CVE-2011-1098 can facilitate local privilege escalation attacks by allowing an attacker to open new log files before permissions are properly set.