full-disclosure - Bug with .php extension?

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: <4394170D.2020406@hogyros.de>
Date: Mon Dec  5 10:31:57 2005
From: Simon.Richter at hogyros.de (Simon Richter)
Subject: Bug with .php extension?

Hello,

Ron wrote:

> In Apache 1.3.33 (untested on any other version), if you have a file 
> called file.php.bak, and you navigate to it in the browser, it will run 
> on the server as a .php file.  This works with any extension that isn't 
> known to the server (.rar, .bak, .test, .java, .cpp, .c, etc.)

I would think this is related to "Options MultiViews", where a file 
generally has many suffixes (file type, language, compression, ...). 
Does this also happen to you (yes, I'm too lazy to try right now) if you 
turn MultiViews off?

Nevertheless, good idea that script authors should possibly be aware 
that any suffix, not just the last, is interpreted.

    Simon
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 307 bytes
Desc: OpenPGP digital signature
Url : http://lists.grok.org.uk/pipermail/full-disclosure/attachments/20051205/c3196236/signature.bin