full-disclosure - Re: Linux kernel source archive vulnerable

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>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <45014972.7070703@effective-it.co.uk>
Date: Fri, 08 Sep 2006 11:44:02 +0100
From: Lee Ball <lee@...ective-it.co.uk>
To: Hadmut Danisch <hadmut@...isch.de>
Cc: full-disclosure@...ts.grok.org.uk, bugtraq@...urityfocus.com
Subject: Re: Linux kernel source archive vulnerable

Hadmut Danisch wrote:
> On Fri, Sep 08, 2006 at 12:52:22AM +0530, Raj Mathur wrote:
>> I wouldn't know if something has changed drastically between 2.6.16
>> and 2.6.17.11, but:
>>
>> raju@...l:~$ find /usr/src/linux-2.6.16/ -perm -666 ! -type l
>> raju@...l:~$
>>
>> Not a single world-writable file or directory.  Perhaps pre-release
>> kernel tarballs are more lax?
> 
> 
> On my machine (I also have a 2.6.16):
> 
> # find /usr/src/linux-2.6.16/ -perm -666 ! -type l | wc -l
> 20434
> 
> Just to doublecheck I wrote a script which parses the kernel tar:
> 
> pax_global_header                                                              52 b mode=666 uid=    0 gid=    0
> linux-2.6.17.11/                                                                0 b mode=777 uid=    0 gid=    0
> linux-2.6.17.11/.gitignore                                                    462 b mode=666 uid=    0 gid=    0
> linux-2.6.17.11/COPYING                                                     18693 b mode=666 uid=    0 gid=    0
> linux-2.6.17.11/CREDITS                                                     89536 b mode=666 uid=    0 gid=    0
> linux-2.6.17.11/Documentation/                                                  0 b mode=777 uid=    0 gid=    0
> linux-2.6.17.11/Documentation/00-INDEX                                      10581 b mode=666 uid=    0 gid=    0
> linux-2.6.17.11/Documentation/BUG-HUNTING                                    7249 b mode=666 uid=    0 gid=    0
> linux-2.6.17.11/Documentation/Changes                                       11655 b mode=666 uid=    0 gid=    0
> linux-2.6.17.11/Documentation/CodingStyle                                   17843 b mode=666 uid=    0 gid=    0
> linux-2.6.17.11/Documentation/DMA-API.txt                                   21291 b mode=666 uid=    0 gid=    0
> linux-2.6.17.11/Documentation/DMA-ISA-LPC.txt                                5332 b mode=666 uid=    0 gid=    0
> linux-2.6.17.11/Documentation/DMA-mapping.txt                               32801 b mode=666 uid=    0 gid=    0
> linux-2.6.17.11/Documentation/DocBook/                                          0 b mode=777 uid=    0 gid=    0
> linux-2.6.17.11/Documentation/DocBook/.gitignore                               35 b mode=666 uid=    0 gid=    0
> ...
> 
> 
> A friend of mine confirmed to also have world writable dirs and files.
> 
> regards
> Hadmut

Sorry to add my 2 pence worth but I noticed that Raj ran his command as
a normal user and you Hadmut have ran yours as root. Isn't it going to
be ok as the directories above these world writeable files aren't
writeable/readable by a non-superuser?

Cheers

_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/