Bugtraq mailing list archives
Re: [Full-disclosure] Vim: Insecure Temporary File Creation During Build: Arbitrary Code Execution
From: "Steven M. Christey" <coley () linus mitre org>
Date: Fri, 25 Jul 2008 11:57:28 -0400 (EDT)
On Fri, 25 Jul 2008, [UTF-8] Jan Miná�^Y wrote:
The commands do not have to be written there between (1) and (2), they can be in the file long before the ./configure was started -- just because the script does care whether it can write to the file at all. So unlike stated in the advisory, and in CVE-2008-3294, the issue does not involve a race condition if the attacker would choose to create a 644 file.The file gets truncated in (1). You're wrong, the advisory is right.
Maybe the point here is that if the attacker owns the file and sets 644 permissions, then the truncation won't happen since ./configure won't have the permissions to modify the file. - Steve
Current thread:
- Vim: Insecure Temporary File Creation During Build: Arbitrary Code Execution Jan Minář (Jul 18)
- Re: Vim: Insecure Temporary File Creation During Build: Arbitrary Code Execution Nikolai Weibull (Jul 18)
- Re: [Full-disclosure] Vim: Insecure Temporary File Creation During Build: Arbitrary Code Execution Robert Buchholz (Jul 25)
- Re: [Full-disclosure] Vim: Insecure Temporary File Creation During Build: Arbitrary Code Execution Jan Minář (Jul 25)
- Re: [Full-disclosure] Vim: Insecure Temporary File Creation During Build: Arbitrary Code Execution Steven M. Christey (Jul 25)
- Re: [Full-disclosure] Vim: Insecure Temporary File Creation During Build: Arbitrary Code Execution Jan Minář (Jul 26)
- Re: [Full-disclosure] Vim: Insecure Temporary File Creation During Build: Arbitrary Code Execution Robert Buchholz (Jul 25)
- Re: [Full-disclosure] Vim: Insecure Temporary File Creation During Build: Arbitrary Code Execution Jan Minář (Jul 25)