Bug 680789 - logrotate: Race condition by creation of new files after renaming the previous version if compression or copy creation requested (arbitrary system file integrity corruption)
Summary: logrotate: Race condition by creation of new files after renaming the previou...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-27 19:17 UTC by Jan Lieskovsky
Modified: 2019-09-29 12:43 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-03-11 06:30:25 UTC


Attachments (Terms of Use)
proposed patch (929 bytes, patch)
2011-03-01 09:15 UTC, Jan Kaluža
no flags Details | Diff

Description Jan Lieskovsky 2011-02-27 19:17:28 UTC
A race condition was found in the way the logrotate utility created
new files after renaming the previous version if compression or
creation of a copy was requested in the configuration file. If the
logrotate utility was run on a log file contained within an attacker
controllable directory, a local attacker could use this flaw to trick
the logrotate utility into replacing arbitrary system files (if
logrotate was run under privileged user account, root) with the copied
or compressed contents of a log file.

Comment 3 Jan Kaluža 2011-03-01 09:15:16 UTC
Created attachment 481568 [details]
proposed patch

This is backported patch from Debian without unlink command which fixes this issue.

Comment 4 Jan Kaluža 2011-03-01 09:17:49 UTC
Note that final patch can change, because this issue is tightly connected with other bugs, so there will be maybe one bigger patch which will cover more bugs.

Comment 7 Jan Lieskovsky 2011-03-03 10:15:05 UTC
Further clarified details from Stefan Fritsch of Debian Security Team:
=======================================================================

There is a race between renaming

950 if (!debug && rename(oldName, newName)) {

a previous generation log file (say from "foo.1" to "foo.2") and
opening a file with the old name ("foo.1") for writing. The open for
write can happen both in copyTruncate() or in compressLogFile() at

302 outFile = createOutputFile(compressedName, O_RDWR | O_CREAT |
O_TRUNC, sb);

The fix would be to use O_EXCL.


Note You need to log in before you can comment on or make changes to this bug.