full-disclosure - Frontpage Extensions Remote Command Execution

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: <247290000.1068674588@utd49554.utdallas.edu>
From: pauls at utdallas.edu (Paul Schmehl)
Subject: Frontpage Extensions Remote Command Execution

--On Wednesday, November 12, 2003 02:53:02 PM -0500 Damian Gerow 
<damian@...tex.net> wrote:

> Thus spake mattmurphy@...rr.com (mattmurphy@...rr.com) [12/11/03 14:41]:
>> bulletin.  A decent admin would configure FPSE such that this flaw is a
>> non-issue.  This is because no ordinary user has a reason to be accessing
>> FPSE's files.  If FPSE is secured, this means that an attacker is getting
>> their own privileges back.
>
> A decent OS shouldn't need the admin to go in and modify permissions on
> specific files in order to give a ensure a basic security requirement.
> While an ordinary user may have no reason to access those files, an
> ordinary admin should similarily have no reason for modifying the
> permissions on those files.
>
You're serious?   I mean *really* serious?  Or is this a test?

How do you explain this, for example?

http://httpd.apache.org/docs/misc/security_tips.html

Paul Schmehl (pauls@...allas.edu)
Adjunct Information Security Officer
The University of Texas at Dallas
AVIEN Founding Member
http://www.utdallas.edu