Issues in index.php (master) - Issues in master - ngodingbang/laravel-stisla-starter - Measure and Improve Code Quality continuously with Scrutinizer

Issues (35)

Security Analysis not enabled

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.

Regex Injection

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

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.

Response Splitting

Response Splitting can be used to send arbitrary responses.

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.

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.

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.

Code Injection

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

Variable Injection

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

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.

Other Vulnerability

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

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.

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.

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.

Header Injection

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 (1 issue)

Labels

Bug 1

Severity

Major 1

Septianata Rizky Pratama 1

<?php

use Illuminate\Contracts\Http\Kernel;
use Illuminate\Http\Request;
.
|-- OtherDir
|   |-- Bar.php
|   `-- Foo.php
`-- SomeDir
    `-- Foo.php

define('LARAVEL_START', microtime(true));

/*
|--------------------------------------------------------------------------
| Check If The Application Is Under Maintenance
|--------------------------------------------------------------------------
|
| If the application is in maintenance / demo mode via the "down" command
| we will load this file so that any pre-rendered content can be shown
| instead of starting the framework, which could cause an exception.
|
*/

if (file_exists($maintenance = __DIR__.'/../storage/framework/maintenance.php')) {
    require $maintenance;
}

/*
|--------------------------------------------------------------------------
| Register The Auto Loader
|--------------------------------------------------------------------------
|
| Composer provides a convenient, automatically generated class loader for
| this application. We just need to utilize it! We'll simply require it
| into the script here so we don't need to manually load our classes.
|
*/

require __DIR__.'/../vendor/autoload.php';

/*
|--------------------------------------------------------------------------
| Run The Application
|--------------------------------------------------------------------------
|
| Once we have the application, we can handle the incoming request using
| the application's HTTP kernel. Then, we will send the response back
| to this client's browser, allowing them to enjoy our application.
|
*/

$app = require_once __DIR__.'/../bootstrap/app.php';

$kernel = $app->make(Kernel::class);

$response = $kernel->handle(
    $request = Request::capture()
)->send();

$kernel->terminate($request, $response);


1			<?php
2
3			use Illuminate\Contracts\Http\Kernel;
4			use Illuminate\Http\Request;
			0 ignored issues – show Bug introduced 2022-02-25 16:21 UTC by Report Bug Copy Issue Report Show Similar Issues like this This use statement conflicts with another class in this namespace, `Request`. Consider defining an alias. Let?s assume that you have a directory layout like this: . \|-- OtherDir \| \|-- Bar.php \| `-- Foo.php `-- SomeDir `-- Foo.php and let?s assume the following content of `Bar.php`: // Bar.php namespace OtherDir; use SomeDir\Foo; // This now conflicts the class OtherDir\Foo If both files `OtherDir/Foo.php` and `SomeDir/Foo.php` are loaded in the same runtime, you will see a PHP error such as the following: PHP Fatal error: Cannot use SomeDir\Foo as Foo because the name is already in use in OtherDir/Foo.php However, as `OtherDir/Foo.php` does not necessarily have to be loaded and the error is only triggered if it is loaded before `OtherDir/Bar.php`, this problem might go unnoticed for a while. In order to prevent this error from surfacing, you must import the namespace with a different alias: // Bar.php namespace OtherDir; use SomeDir\Foo as SomeDirFoo; // There is no conflict anymore. Loading history...
5
6			define('LARAVEL_START', microtime(true));
7
8			/*
9			\|--------------------------------------------------------------------------
10			\| Check If The Application Is Under Maintenance
11			\|--------------------------------------------------------------------------
12			\|
13			\| If the application is in maintenance / demo mode via the "down" command
14			\| we will load this file so that any pre-rendered content can be shown
15			\| instead of starting the framework, which could cause an exception.
16			\|
17			*/
18
19			if (file_exists($maintenance = __DIR__.'/../storage/framework/maintenance.php')) {
20			require $maintenance;
21			}
22
23			/*
24			\|--------------------------------------------------------------------------
25			\| Register The Auto Loader
26			\|--------------------------------------------------------------------------
27			\|
28			\| Composer provides a convenient, automatically generated class loader for
29			\| this application. We just need to utilize it! We'll simply require it
30			\| into the script here so we don't need to manually load our classes.
31			\|
32			*/
33
34			require __DIR__.'/../vendor/autoload.php';
35
36			/*
37			\|--------------------------------------------------------------------------
38			\| Run The Application
39			\|--------------------------------------------------------------------------
40			\|
41			\| Once we have the application, we can handle the incoming request using
42			\| the application's HTTP kernel. Then, we will send the response back
43			\| to this client's browser, allowing them to enjoy our application.
44			\|
45			*/
46
47			$app = require_once __DIR__.'/../bootstrap/app.php';
48
49			$kernel = $app->make(Kernel::class);
50
51			$response = $kernel->handle(
52			$request = Request::capture()
53			)->send();
54
55			$kernel->terminate($request, $response);
56

ngodingbang / laravel-stisla-starter

Issues (35)

Security Analysis not enabled

public/index.php (1 issue)

Labels

Severity

Introduced By

Duplication Side-by-Side

Filter issues like