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

Issues (358)

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.

public/index.php (3 issues)

Labels

Severity

Minor 3

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

1			<?php
			0 ignored issues – show Coding Style Compatibility introduced 2017-06-14 03:34 UTC by Report Bug Copy Issue Report Show Similar Issues like this For compatibility and reusability of your code, PSR1 recommends that a file should introduce either new symbols (like classes, functions, etc.) or have side-effects (like outputting something, or including other files), but not both at the same time. The first symbol is defined on line 30 and the first side effect is on line 12. The PSR-1: Basic Coding Standard recommends that a file should either introduce new symbols, that is classes, functions, constants or similar, or have side effects. Side effects are anything that executes logic, like for example printing output, changing ini settings or writing to a file. The idea behind this recommendation is that merely auto-loading a class should not change the state of an application. It also promotes a cleaner style of programming and makes your code less prone to errors, because the logic is not spread out all over the place. To learn more about the PSR-1, please see the PHP-FIG site on the PSR-1. Loading history...
2
3			/*
4			\|--------------------------------------------------------------------------
5			\| Autoload
6			\|--------------------------------------------------------------------------
7			\|
8			\| After running "composer install", we can use the autoloader file created.
9			\|
10			*/
11
12			require '../vendor/autoload.php';
13
14			/*
15			\|--------------------------------------------------------------------------
16			\| Define Application Configuration Constants
17			\|--------------------------------------------------------------------------
18			\|
19			\| PUBLIC_ROOT: the root URL for the application (see below).
20			\| BASE_DIR: path to the directory that has all of your "app", "public", "vendor", ... directories.
21			\| IMAGES: path to upload images, don't use it for displaying images, use Config::get('root') . "/img/" instead.
22			\| APP: path to app directory.
23			\|
24			*/
25
26			// Config::set('base', str_replace("\\", "/", dirname(__DIR__)));
			0 ignored issues – show Unused Code Comprehensibility introduced 2016-10-17 10:25 UTC by Report Bug Copy Issue Report Show Similar Issues like this `58%` 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...
27			// Config::set('images', str_replace("\\", "/", __DIR__) . "/img/");
28			// Config::set('app', Config::get('base') . "/app/");
29
30			define('BASE_DIR', str_replace("\\", "/", dirname(__DIR__)));
31			define('IMAGES', str_replace("\\", "/", __DIR__) . "/img/");
32			define('APP', BASE_DIR . "/app/");
33
34			/*
35			\|--------------------------------------------------------------------------
36			\| Register Error & Exception handlers
37			\|--------------------------------------------------------------------------
38			\|
39			\| Here we will register the methods that will fire whenever there is an error
40			\| or an exception has been thrown.
41			\|
42			*/
43
44			Handler::register();
45
46			/*
47			\|--------------------------------------------------------------------------
48			\| Start Session
49			\|--------------------------------------------------------------------------
50			\|
51			*/
52
53			Session::init();
54
55			/*
56			\|--------------------------------------------------------------------------
57			\| Create The Application
58			\|--------------------------------------------------------------------------
59			\|
60			\| Here we will create the application instance which will take care of routing
61			\| the incoming request to the corresponding controller and action method if valid
62			\|
63			*/
64
65			$app = new App();
66
67			// Config::set('root', $app->request->root());
			0 ignored issues – show Unused Code Comprehensibility introduced 2016-10-17 10:25 UTC by Report Bug Copy Issue Report Show Similar Issues like this `65%` 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...
68			define('PUBLIC_ROOT', $app->request->root());
69
70			/*
71			\|--------------------------------------------------------------------------
72			\| Run The Application
73			\|--------------------------------------------------------------------------
74			\|
75			\| Once we have the application instance, we can handle the incoming request
76			\| and send a response back to the client's browser.
77			\|
78			*/
79
80			$app->run();

GitHub Access Token became invalid

Issues (358)

Security Analysis not enabled

public/index.php (3 issues)

Labels

Severity

Introduced By

Upgrade to new PHP Analysis Engine

OmarElGabry / miniPHP

GitHub Access Token became invalid

Issues (358)

Security Analysis not enabled

public/index.php (3 issues)

Labels

Severity

Introduced By

Upgrade to new PHP Analysis Engine

Duplication Side-by-Side

Filter issues like