bugtraq - Re: Zip 2,31 bad default file-permissions vulnerability

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <7389fc4b0508051440654ee0c8@mail.gmail.com>
Date: Fri, 5 Aug 2005 22:40:59 +0100
From: Imran Ghory <imranghory@...il.com>
To: lupe@...e-christoph.de, bugtraq@...urityfocus.com
Subject: Re: Zip 2,31 bad default file-permissions vulnerability

On 8/5/05, Lupe Christoph <lupe@...e-christoph.de> wrote:
> 
> I still don't understand why this is a problem. If it were a problem, it
> would be one of humongous dimensions because it affects all programs
> that use open(..., 0666) to create non-executable files potentially
> containing sensitive contents. 

In cases where a "secure" file has permissions degraded yes, for
example  CAN-2005-1920 where an editor was creating a a backup with
less secure permissions than the original.

> For example all editors. And all shells
> because any redirection could create such a file.

Permission handling in shells is generally accepted to be insecure due
to other issues such  as lack of atomicity.

Imran