hola a todos..

antes de que leas el post quiero aclarar que no tengo malas intenciones.. con lo que me podáis ayudar, simplemente quiero:
1). aprender mas
2). el creador del servidor al que intento acceder dice y asegura que es imposible que yo acceda a sus bases de datos o siquiera que haga algo en su servidor:)
3). curiosidad ......

exponiendo el caso


el servidor  http://xxxx/ sirve sus paginas web con apache lo que lo hace mas dificil de acceder a el,
la pagina esta hecha en php, y trabajan con short tags, sin embargo ya eh logrado pillar sus directorios y su estructura ( es decir como esta contruida la pagina ), ademas trabaja con bases de datos de sql server, en el servidor ay dos directorios que componen la pagina,  llamaremos estos dos directorios (dir1)= main (dir2)= backend , estos dos estan enlazados por short tags.

en el directorio main esta todo lo del diseño, contenidos, imagenes etc....
en el directorio backend esta toda la configuracion y los archivos de enlace al sql server....

es decir tenemos estos dos directorios http://xxxx/main    y    http://xxxx/main/backend/

explorando estos directorios encontre el archivo ADMIN.PHP  en el cual encontre que cita este otro archivo
<a href="<?PHP echo $_config['server_feed'];?>admincp.php   ( admin.php )

es decir existe un http://xxxx/main/modules/admin.php   --> este tiene el contenido y diseño

y existe un http://xxxx/main/backend/admin.php   --> este tiene la conguracion y enlace ala base de datos


asu vez el segundo archivo  http://xxxx/main/backend/admin.php  -->> cita un archivo config.php

ubicado en  http://xxxx/main/backend/config.php     

este archivo config.php contiene informacion como  nombre de usuario de sql password  tipos de db, tablas etc....


el archivo http://xxxx/main/backend/admin.php  tien algo asi como esto



include 'config.php'          esto es igual a  http://xxxx/main/backend/config.php

include 'includes/functions.php';        esto es igual a  http://xxxx/main/backend/includes/functions.php

require 'includes/dbconnect.php';      esto es igual a  http://xxxx/main/backend/includes/dbconnect.php


el archivo que realmente me intereso era "dbconnect.php"  pense que ay estaba la informacion de inicio de secion en sql  pero me encontre con esto

$db2 = ADONewConnection('mssql');
$db2->locale = 'us_english';
$db2->debug = $_config['dbdebug'];
$rs = $db2->NConnect($_config['Server'], $_config['User'], $_config['Pass'], $_config['DB2']) or die("Unable to connect DB2!");

es decir que este archivo "dbconnect.php" plantea la conexion de inicio de secion en sql usando los datos del archivo  http://xxxx/main/backend/config.php

supongo que el http://xxxx/main/backend/config.php      debe tener algo asi como


$_config['db_type'] = 'tipo de conexion';
$_config['Server'] = "ip del sql server";  -->> (que porcierto ya la tengo
$_config['User'] = "usuario sql";
$_config['Pass'] = "psword sql";
$_config['DB'] = "tipo de db";
$_config['DB2'] = "otro tipo de db";


lo único malo y a lo que viene mi petición de ayuda es que no eh podido ver la informacion del archivo  http://xxxx/main/backend/config.php    por mas que intento en ningun navegador puede mostrar http://xxxx/main/backend/config.php   ....   supongo que el servidor de apache obstaculiza y no permite el acceso a archivos de tipo config....

lo que yo quiero saber es de que manera puedo acceder a este archivo  (config.php) .... es decir ver el código que ay, hay dentro         


eh intentado muchas cosas y no eh podido por lo tanto hoy decidí acudir a ustedes


agradezco su ayuda


un saludo andres199

eh escaneado el server y note que no esta ejecutando php en safe_mode

el siguiente es un informe de vilnerabilidades en el servidor

1).Web Servers : OpenSSL DTLS Packets Multiple Denial of Service Vulnerabilities
*descripcion: OpenSSL is prone to multiple vulnerabilities that may allow attackers to cause denial-of-service conditions.



2).Web Servers : OpenSSL EVP_VerifyFinal Function Signature Verification Vulnerability
*descripcion: OpenSSL is prone to a signature-verification vulnerability.An attacker would likely leverage this issue by first carrying out a man-in-the-middle attack. The attacker would most likely exploit this issue to conduct phishing attacks or to impersonate legitimate sites. Other attacks are likely possible.Releases prior to OpenSSL 0.9.8j are affected.

3).Web Servers : OpenSSL Multiple Vulnerabilities
*descripcion: OpenSSL is prone to multiple vulnerabilities that may allow attackers to trigger denial-of-service conditions or bypass certain security checks.Versions prior to OpenSSL 0.9.8k are vulnerable.

4).Web Servers : PHP 5.2.10 and Prior Versions Multiple Vulnerabilities
*descripcion: PHP is prone to multiple security vulnerabilities.The impact of these issues has not been specified. We will update this BID when more information becomes available.These issues affect PHP 5.2.10 and prior versions.

5).Web Servers : PHP cURL safe_mode and open_basedir Restriction-Bypass Vulnerability
*descripcion: PHP is prone to a 'safe_mode' and 'open_basedir' restriction-bypass vulnerability. Successful exploits could allow an attacker to access files in unauthorized locations.This vulnerability would be an issue in shared-hosting configurations where multiple users can create and execute arbitrary PHP script code, with the 'safe_mode' and 'open_basedir' restrictions assumed to isolate the users from each other.PHP 5.2.9 is vulnerable; other versions may also be affected.

6).Web Servers : PHP exif_read_data JPEG Image Processing Denial Of Service Vulnerability
*descripcion:PHP is prone to a denial-of-service vulnerability in its 'exif_read_data()' function.Successful exploits may allow remote attackers to cause denial-of-service conditions in applications that use the vulnerable function.Versions prior to PHP 5.2.10 are affected.

7).Web Servers : PHP htmlspecialcharacters Malformed Multibyte Character Cross Site Scripting Vulnerability
*descripcion:PHP is prone to a cross-site scripting vulnerability because it fails to properly sanitize user-supplied input.An attacker may leverage this issue to execute arbitrary script code in the browser of an unsuspecting user in the context of the affected site. This may let the attacker steal cookie-based authentication credentials and launch other attacks.NOTE: In some configurations, attackers may exploit this issue to carry out HTML-injection attacks.Versions prior to PHP 5.2.12 are vulnerable.

8).Web Servers : PHP Interruptions and Calltime Arbitrary Code Execution Vulnerability
*descripcion: PHP is prone to an arbitrary-code-execution vulnerability.An attacker can exploit this issue to execute arbitrary with the privileges of the user running the affected application. Successfully exploiting this issue will compromise the affected application and possibly underlying computers.

9).Web Servers : PHP mb_ereg_replace String Evaluation Vulnerability
 *descripcion: The 'mb_ereg_replace()' function of PHP is prone to a vulnerability that can result in the improper evaluation of user-supplied input.Exploiting this issue may allow attackers to execute arbitrary PHP commands in the context of the affected application.

10).Web Servers : PHP Multiple Functions safe_mode Restriction Bypass Vulnerability
*descripcion: PHP is prone to 'safe_mode' restriction-bypass vulnerability. Successful exploits could allow an attacker to execute arbitrary code.This vulnerability would be an issue in hosting environments where users can create and execute arbitrary PHP script code; in such cases, the 'safe_mode' restriction is expected to enforce certain restrictions on executing system commands. This issue can also help in attacks exploiting other vulnerabilities, resulting in remote PHP code execution.Note that the issue affects only Windows PHP installations and can be exploited when 'safe_mode_exec_dir' is not set (holds a default value).PHP 5.2.9 and 5.2.10 are vulnerable; prior and newer versions may also be affected.

11). Web Servers : PHP proc_open safe_mode_protected_env_var Restriction-Bypass Vulnerability
*descripcion: PHP is prone to a safe_mode restriction-bypass vulnerability.Successfully exploiting this issue may allow attackers to alter the process environment, which may lead to other attacks.Versions prior to PHP 5.3.1 are vulnerable.


12).Web Servers : PHP session.save_path Arbitrary Code Execution Vulnerability
*descripcion: Attackers can exploit this issue to execute arbitrary code within the context of the PHP process. This may allow them to bypass intended security restrictions or gain elevated privileges.

13).Web Servers : PHP session_save_path safe_mode Restriction-Bypass Vulnerability
*descripcion: PHP is prone to a 'safe_mode' restriction-bypass vulnerability. Successful exploits could allow an attacker to write session files in arbitrary directions.This vulnerability would be an issue in shared-hosting configurations where multiple users can create and execute arbitrary PHP script code; the 'safe_mode' restrictions are assumed to isolate users from each other.PHP 5.2.12 and 5.3.1 are vulnerable; other versions may also be affected.

14).Web Servers : Apache APR apr_uri_parse_hostinfo Off By One Remote Code Execution Vulnerability
*descripcion:Apache Portable Runtime (APR) is prone to a remote code-execution vulnerability caused by an off-by-one error.Successful exploits allow attackers to execute arbitrary code in the context of a vulnerable application. Failed exploit attempts may result in denial-of-service conditions.NOTE: This BID is being retired because the issue discussed was based on misleading or incorrect information.

15).Web Servers : Apache HTTP Server Solaris Event Port Pollset Support Remote Denial Of Service Vulnerability
*descripcion: Apache HTTP Server is prone to a denial-of-service vulnerability because of faulty error handling.Successful exploits may allow remote attackers to trigger denial-of-service conditions.This issue affects versions prior to Apache 2.2.14 on Solaris platforms.

16).Web Servers : Apache mod_deflate Remote Denial Of Service Vulnerability
*descripcion: The Apache 'mod_deflate' module is prone to a denial-of-service vulnerability.Successful exploits may allow remote attackers to cause denial-of-service conditions and prevent legitimate users from accessing the services.

17).Web Servers : Apache mod_proxy Remote Denial Of Service Vulnerability
*descripcion: The Apache 'mod_proxy' module is prone to a denial-of-service vulnerability.Successful exploits may allow remote attackers to cause denial-of-service conditions and prevent legitimate users from accessing the services.

esto no hiria en la parte de bug y explits nivel web??