Issues in index.php (master) - Issues in master - intraface/intraface.dk - Measure and Improve Code Quality continuously with Scrutinizer

Issues (4714)

Security Analysis not enabled

Cross-Site Scripting

Cross-Site Scripting enables an attacker to inject code into the response of a web-request that is viewed by other users. It can for example be used to bypass access controls, or even to take over other users' accounts.

File Exposure

File Exposure allows an attacker to gain access to local files that he should not be able to access. These files can for example include database credentials, or other configuration files.

File Manipulation

File Manipulation enables an attacker to write custom data to files. This potentially leads to injection of arbitrary code on the server.

Object Injection

Object Injection enables an attacker to inject an object into PHP code, and can lead to arbitrary code execution, file exposure, or file manipulation attacks.

Code Injection

Code Injection enables an attacker to execute arbitrary code on the server.

Response Splitting

Response Splitting can be used to send arbitrary responses.

File Inclusion

File Inclusion enables an attacker to inject custom files into PHP's file loading mechanism, either explicitly passed to include, or for example via PHP's auto-loading mechanism.

Command Injection

Command Injection enables an attacker to inject a shell command that is execute with the privileges of the web-server. This can be used to expose sensitive data, or gain access of your server.

SQL Injection

SQL Injection enables an attacker to execute arbitrary SQL code on your database server gaining access to user data, or manipulating user data.

XPath Injection

XPath Injection enables an attacker to modify the parts of XML document that are read. If that XML document is for example used for authentication, this can lead to further vulnerabilities similar to SQL Injection.

LDAP Injection

LDAP Injection enables an attacker to inject LDAP statements potentially granting permission to run unauthorized queries, or modify content inside the LDAP tree.

Header Injection

Other Vulnerability

This category comprises other attack vectors such as manipulating the PHP runtime, loading custom extensions, freezing the runtime, or similar.

Regex Injection

Regex Injection enables an attacker to execute arbitrary code in your PHP process.

XML Injection

XML Injection enables an attacker to read files on your local filesystem including configuration files, or can be abused to freeze your web-server process.

Variable Injection

Variable Injection enables an attacker to overwrite program variables with custom data, and can lead to further vulnerabilities.

Unfortunately, the security analysis is currently not available for your project. If you are a non-commercial open-source project, please contact support to gain access.

tests/xmlrpcservers/index.php (6 issues)

Labels

Severity

Upgrade to new PHP Analysis Engine

These results are based on our legacy PHP analysis, consider migrating to our new PHP analysis engine instead. Learn more

<?php
require_once dirname(__FILE__) . '/../unit/config.test.php';

require_once 'konstrukt/konstrukt.inc.php';

class MyIdentityLoader extends k_BasicHttpIdentityLoader {


    function selectUser($private_key, $session_id)
    {
        $auth_adapter = new Intraface_Auth_PrivateKeyLogin(MDB2::singleton(DB_DSN), $session_id, $private_key);
        $weblogin = $auth_adapter->auth();

        if ($weblogin) {


            $this->kernel = new Intraface_Kernel($session_id);
            $this->kernel->weblogin = $weblogin;

            $this->kernel->intranet = new Intraface_Intranet($weblogin->getActiveIntranetId());
            $this->kernel->setting = new Intraface_Setting($this->kernel->intranet->get('id'));

            // makes intranet_id accessable in Doctrine
            Intraface_Doctrine_Intranet::singleton($this->kernel->intranet->getId());

            return new k_AuthenticatedUser($private_key);
        }
    }
}

require_once 'Ilib/ClassLoader.php';
require_once 'konstrukt/konstrukt.inc.php';
//set_error_handler('k_exceptions_error_handler');
spl_autoload_register('k_autoload');

XML_RPC2_Backend::setBackend('php');
$HTTP_RAW_POST_DATA = file_get_contents('php://input');

k()
  ->setIdentityLoader(new MyIdentityLoader())
  // Use container for wiring of components
  // ->setComponentCreator(new k_InjectorAdapter(create_container()))

  // Enable file logging
  //->setLog(dirname(__FILE__) . '/../log/debug.log')

  // Uncomment the next line to enable in-browser debugging
  //->setDebug()
  // Dispatch request
  ->run('Intraface_XMLRPC_Controller')
  ->out();


1		<?php
2		require_once dirname(__FILE__) . '/../unit/config.test.php';
3
4		require_once 'konstrukt/konstrukt.inc.php';
5
6	View Code Duplication	class MyIdentityLoader extends k_BasicHttpIdentityLoader {
		0 ignored issues – show Comprehensibility Best Practice introduced 2016-04-20 09:50 UTC by Report Bug Copy Issue Report Show Similar Issues like this The type `MyIdentityLoader` has been defined more than once; this definition is ignored, only the first definition in `src/intraface.dk/tools/index.php` (L9-21) is considered. This check looks for classes that have been defined more than once. If you can, we would recommend to use standard object-oriented programming techniques. For example, to avoid multiple types, it might make sense to create a common interface, and then multiple, different implementations for that interface. This also has the side-effect of providing you with better IDE auto-completion, static analysis and also better OPCode caching from PHP. Loading history... Duplication introduced 2016-04-20 09:50 UTC by Report Bug Copy Issue Report Show Similar Issues like this This class seems to be duplicated in your project. Duplicated code is one of the most pungent code smells. If you need to duplicate the same code in three or more different places, we strongly encourage you to look into extracting the code into a single class or operation. You can also find more detailed suggestions in the “Code” section of your repository. Loading history...
7
8		function selectUser($private_key, $session_id)
9		{
10		$auth_adapter = new Intraface_Auth_PrivateKeyLogin(MDB2::singleton(DB_DSN), $session_id, $private_key);
11		$weblogin = $auth_adapter->auth();
12
13		if ($weblogin) {
		0 ignored issues – show Coding Style introduced 2016-04-20 09:50 UTC by Report Bug Copy Issue Report Show Similar Issues like this Blank line found at start of control structure Loading history...
14
15		$this->kernel = new Intraface_Kernel($session_id);
16		$this->kernel->weblogin = $weblogin;
		0 ignored issues – show Bug introduced 2016-04-20 09:50 UTC by Report Bug Copy Issue Report Show Similar Issues like this The property `weblogin` does not seem to exist in `Intraface_Kernel`. An attempt at access to an undefined property has been detected. This may either be a typographical error or the property has been renamed but there are still references to its old name. If you really want to allow access to undefined properties, you can define magic methods to allow access. See the php core documentation on Overloading. Loading history...
17		$this->kernel->intranet = new Intraface_Intranet($weblogin->getActiveIntranetId());
18		$this->kernel->setting = new Intraface_Setting($this->kernel->intranet->get('id'));
19
20		// makes intranet_id accessable in Doctrine
21		Intraface_Doctrine_Intranet::singleton($this->kernel->intranet->getId());
22
23		return new k_AuthenticatedUser($private_key);
24		}
25		}
26		}
27
28		require_once 'Ilib/ClassLoader.php';
29		require_once 'konstrukt/konstrukt.inc.php';
30		//set_error_handler('k_exceptions_error_handler');
31		spl_autoload_register('k_autoload');
32
33		XML_RPC2_Backend::setBackend('php');
34		$HTTP_RAW_POST_DATA = file_get_contents('php://input');
35
36		k()
37		->setIdentityLoader(new MyIdentityLoader())
38		// Use container for wiring of components
39		// ->setComponentCreator(new k_InjectorAdapter(create_container()))
		0 ignored issues – show Unused Code Comprehensibility introduced 2016-04-20 09:50 UTC by Report Bug Copy Issue Report Show Similar Issues like this `62%` of this comment could be valid code. Did you maybe forget this after debugging? Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it. The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production. This check looks for comments that seem to be mostly valid code and reports them. Loading history...
40		// Enable file logging
41		//->setLog(dirname(__FILE__) . '/../log/debug.log')
		0 ignored issues – show Unused Code Comprehensibility introduced 2016-04-20 09:50 UTC by Report Bug Copy Issue Report Show Similar Issues like this `59%` of this comment could be valid code. Did you maybe forget this after debugging? Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it. The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production. This check looks for comments that seem to be mostly valid code and reports them. Loading history...
42		// Uncomment the next line to enable in-browser debugging
43		//->setDebug()
44		// Dispatch request
45		->run('Intraface_XMLRPC_Controller')
46		->out();
47

intraface / intraface.dk

Issues (4714)

Security Analysis not enabled

tests/xmlrpcservers/index.php (6 issues)

Labels

Severity

Introduced By

Upgrade to new PHP Analysis Engine

Duplication Side-by-Side

Filter issues like