Of Peter
Bruderer
Sent: Tuesday, September 29, 2009 9:33 PM
To: full-disclosure@lists.grok.org.uk
Subject: Re: [Full-disclosure] Full Path Disclosure in most wordpress'
plugins [?]
The proposed fix is definitely something that helps. But to me it
looks like most people do not care anymore about
30, 2009 9:35 AM
To: Glafkos Charalambous
Cc: Peter Bruderer; full-disclosure@lists.grok.org.uk
Subject: Re: [Full-disclosure] Full Path Disclosure in most wordpress'
plugins [?]
Hello,
shared hosting environnement is not an option if you want to have a secure
website.
majinboo
2009/9/29
Charalambous
*Cc:* Peter Bruderer; full-disclosure@lists.grok.org.uk
*Subject:* Re: [Full-disclosure] Full Path Disclosure in most wordpress'
plugins [?]
Hello,
shared hosting environnement is not an option if you want to have a secure
website.
majinboo
2009/9/29 Glafkos Charalambous
-disclosure-boun...@lists.grok.org.uk
[mailto:full-disclosure-boun...@lists.grok.org.uk] *On Behalf Of
*majinboo
*Sent:* Monday, September 28, 2009 11:12 PM
*To:* Fernando A. Lagos B.
*Cc:* full-disclosure@lists.grok.org.uk
*Subject:* Re: [Full-disclosure] Full Path Disclosure in most
Hey
at first excuse my bad english. Thats a nice fix. But you need to change
the code for other plugins or files. This code works for all files which
should not be loaded directly:
if (basename($_SERVER['SCRIPT_NAME']) == basename(__FILE__))
exit('Please do not load this page directly');
The proposed fix is definitely something that helps. But to me it
looks like most people do not care anymore about server settings. As
soon as it is kind of working, it is pushed to the Internet.
Why not avoid these problems completely and follow the recommendations
in php.ini?
; Print out
-Original Message-
From: full-disclosure-boun...@lists.grok.org.uk
[mailto:full-disclosure-boun...@lists.grok.org.uk] On Behalf Of Peter
Bruderer
Sent: Tuesday, September 29, 2009 9:33 PM
To: full-disclosure@lists.grok.org.uk
Subject: Re: [Full-disclosure] Full Path Disclosure in most wordpress
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Exists an call to add_action() without validate with function_exists().
When I run the php script directly, I get the full path of wp installation.
Example:
[+] http://www.marco2010.cl/wp-content/plugins/akismet/akismet.php
[+]
Hello,
this kind of vulnerabilities exists whenever a PHP scripts issue a fatal
error on a poorly configured server. PHP should log errors in a local file
and not on the client screen. With this configuration, you will not see a
full path disclosure in each uncatched PHP exception. IMHO the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
majinboo wrote:
Hello,
Hi
this kind of vulnerabilities exists whenever a PHP scripts issue a
fatal error on a poorly configured server. PHP should log errors in a
local file and not on the client screen. With this configuration, you
will not
] On Behalf Of majinboo
Sent: Monday, September 28, 2009 11:12 PM
To: Fernando A. Lagos B.
Cc: full-disclosure@lists.grok.org.uk
Subject: Re: [Full-disclosure] Full Path Disclosure in most wordpress'
plugins [?]
Hello,
this kind of vulnerabilities exists whenever a PHP scripts issue a fatal
error
...@lists.grok.org.uk] *On Behalf Of *majinboo
*Sent:* Monday, September 28, 2009 11:12 PM
*To:* Fernando A. Lagos B.
*Cc:* full-disclosure@lists.grok.org.uk
*Subject:* Re: [Full-disclosure] Full Path Disclosure in most wordpress'
plugins [?]
Hello,
this kind of vulnerabilities exists
12 matches
Mail list logo
