Issues in start.php (master) - Issues in master - t2t2/draft - Measure and Improve Code Quality continuously with Scrutinizer

Issues (103)

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.

bootstrap/start.php (1 issue)

Labels

Documentation 1

Severity

Minor 1

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

/*
|--------------------------------------------------------------------------
| Create The Application
|--------------------------------------------------------------------------
|
| The first thing we will do is create a new Laravel application instance
| which serves as the "glue" for all the components of Laravel, and is
| the IoC container for the system binding all of the various parts.
|
*/

$app = new Illuminate\Foundation\Application;

/*
|--------------------------------------------------------------------------
| Detect The Application Environment
|--------------------------------------------------------------------------
|
| Laravel takes a dead simple approach to your application environments
| so you can just specify a machine name for the host that matches a
| given environment, then we will automatically detect it for you.
|
*/

$env = $app->detectEnvironment(function () {
function acceptsInteger($int) { }

$x = '123'; // string "123"

// Instead of
acceptsInteger($x);

// we recommend to use
acceptsInteger((integer) $x);
	if(file_exists($env = __DIR__.'/../.env')) {
		return file_get_contents($env);
	}
	return 'production';
});

/*
|--------------------------------------------------------------------------
| Bind Paths
|--------------------------------------------------------------------------
|
| Here we are binding the paths configured in paths.php to the app. You
| should not be changing these here. If you need to change these you
| may do so within the paths.php file and they will be bound here.
|
*/

$app->bindInstallPaths(require __DIR__.'/paths.php');

/*
|--------------------------------------------------------------------------
| Load The Application
|--------------------------------------------------------------------------
|
| Here we will load this Illuminate application. We will keep this in a
| separate location so we can isolate the creation of an application
| from the actual running of the application with a given request.
|
*/

$framework = $app['path.base'].
                 '/vendor/laravel/framework/src';

require $framework.'/Illuminate/Foundation/start.php';

/*
|--------------------------------------------------------------------------
| Return The Application
|--------------------------------------------------------------------------
|
| This script returns the application instance. The instance is given to
| the calling script so we can separate the building of the instances
| from the actual running of the application and sending responses.
|
*/

return $app;


1		<?php
2
3		/*
4		\|--------------------------------------------------------------------------
5		\| Create The Application
6		\|--------------------------------------------------------------------------
7		\|
8		\| The first thing we will do is create a new Laravel application instance
9		\| which serves as the "glue" for all the components of Laravel, and is
10		\| the IoC container for the system binding all of the various parts.
11		\|
12		*/
13
14	9	$app = new Illuminate\Foundation\Application;
15
16		/*
17		\|--------------------------------------------------------------------------
18		\| Detect The Application Environment
19		\|--------------------------------------------------------------------------
20		\|
21		\| Laravel takes a dead simple approach to your application environments
22		\| so you can just specify a machine name for the host that matches a
23		\| given environment, then we will automatically detect it for you.
24		\|
25		*/
26
27		$env = $app->detectEnvironment(function () {
		0 ignored issues – show Documentation introduced 2016-04-12 22:00 UTC by Report Bug Copy Issue Report Show Similar Issues like this `function () { if (fi... return 'production'; }` is of type `object<Closure>`, but the function expects a `array\|string`. It seems like the type of the argument is not accepted by the function/method which you are calling. In some cases, in particular if PHP’s automatic type-juggling kicks in this might be fine. In other cases, however this might be a bug. We suggest to add an explicit type cast like in the following example: function acceptsInteger($int) { } $x = '123'; // string "123" // Instead of acceptsInteger($x); // we recommend to use acceptsInteger((integer) $x); Loading history...
28	9	if(file_exists($env = __DIR__.'/../.env')) {
29		return file_get_contents($env);
30		}
31	9	return 'production';
32	9	});
33
34		/*
35		\|--------------------------------------------------------------------------
36		\| Bind Paths
37		\|--------------------------------------------------------------------------
38		\|
39		\| Here we are binding the paths configured in paths.php to the app. You
40		\| should not be changing these here. If you need to change these you
41		\| may do so within the paths.php file and they will be bound here.
42		\|
43		*/
44
45	9	$app->bindInstallPaths(require __DIR__.'/paths.php');
46
47		/*
48		\|--------------------------------------------------------------------------
49		\| Load The Application
50		\|--------------------------------------------------------------------------
51		\|
52		\| Here we will load this Illuminate application. We will keep this in a
53		\| separate location so we can isolate the creation of an application
54		\| from the actual running of the application with a given request.
55		\|
56		*/
57
58	9	$framework = $app['path.base'].
59	9	'/vendor/laravel/framework/src';
60
61	9	require $framework.'/Illuminate/Foundation/start.php';
62
63		/*
64		\|--------------------------------------------------------------------------
65		\| Return The Application
66		\|--------------------------------------------------------------------------
67		\|
68		\| This script returns the application instance. The instance is given to
69		\| the calling script so we can separate the building of the instances
70		\| from the actual running of the application and sending responses.
71		\|
72		*/
73
74		return $app;
75

t2t2 / draft

Issues (103)

Security Analysis not enabled

bootstrap/start.php (1 issue)

Labels

Severity

Introduced By

Upgrade to new PHP Analysis Engine

Duplication Side-by-Side

Filter issues like