Issues in routes.php (master) - Issues in master - ddimaria/Laravel-REST-CMS - Measure and Improve Code Quality continuously with Scrutinizer

Issues (76)

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.

app/Http/routes.php (1 issue)

Labels

Unused Code 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

/*
|--------------------------------------------------------------------------
| Application Routes
|--------------------------------------------------------------------------
|
| Here is where you can register all of the routes for an application.
| It's a breeze. Simply tell Laravel the URIs it should respond to
| and give it the controller to call when that URI is requested.
|
*/

Route::pattern('id', '\d+');

// V1 API
Route::group(['prefix' => 'api/v1', 'namespace' => 'Api\V1'], function()
{
	// users/auth
	Route::post('user/login', 'UserController@authenticate');
	Route::get('user/logout/{api_key}', 'UserController@deauthenticate');

	// page
	Route::get('page/{id}', 'PageController@show');
	Route::get('page/{slug}', 'PageController@showBySlug');
	Route::post('page', 'PageController@create');
	Route::get('page/{id}/detail', 'PageController@showWithDetail');
	Route::get('pagedetail/{id}', 'PageDetailController@show');
	Route::post('pagedetail', 'PageDetailController@create');

	// template
	Route::get('template/{id}', 'TemplateController@show');
	Route::post('template', 'TemplateController@create');
	Route::get('template/{id}/detail', 'TemplateController@showWithDetail');
	Route::get('templatedetail/{id}', 'TemplateDetailController@show');
	Route::post('templatedetail', 'TemplateDetailController@create');
});

Route::any('{any}', function($route) 

{
	return \App\Http\Controllers\Api\V1\ApiController::respondNotFound('Invalid Route!');
})->where('any', '(.*)');

1			<?php
2
3			/*
4			\|--------------------------------------------------------------------------
5			\| Application Routes
6			\|--------------------------------------------------------------------------
7			\|
8			\| Here is where you can register all of the routes for an application.
9			\| It's a breeze. Simply tell Laravel the URIs it should respond to
10			\| and give it the controller to call when that URI is requested.
11			\|
12			*/
13
14			Route::pattern('id', '\d+');
15
16			// V1 API
17			Route::group(['prefix' => 'api/v1', 'namespace' => 'Api\V1'], function()
18			{
19			// users/auth
20			Route::post('user/login', 'UserController@authenticate');
21			Route::get('user/logout/{api_key}', 'UserController@deauthenticate');
22
23			// page
24			Route::get('page/{id}', 'PageController@show');
25			Route::get('page/{slug}', 'PageController@showBySlug');
26			Route::post('page', 'PageController@create');
27			Route::get('page/{id}/detail', 'PageController@showWithDetail');
28			Route::get('pagedetail/{id}', 'PageDetailController@show');
29			Route::post('pagedetail', 'PageDetailController@create');
30
31			// template
32			Route::get('template/{id}', 'TemplateController@show');
33			Route::post('template', 'TemplateController@create');
34			Route::get('template/{id}/detail', 'TemplateController@showWithDetail');
35			Route::get('templatedetail/{id}', 'TemplateDetailController@show');
36			Route::post('templatedetail', 'TemplateDetailController@create');
37			});
38
39			Route::any('{any}', function($route)
			0 ignored issues – show Unused Code introduced 2016-01-26 01:01 UTC by Report Bug Copy Issue Report Show Similar Issues like this The parameter `$route` is not used and could be removed. This check looks from parameters that have been defined for a function or method, but which are not used in the method body. Loading history...
40			{
41			return \App\Http\Controllers\Api\V1\ApiController::respondNotFound('Invalid Route!');
42			})->where('any', '(.*)');

ddimaria / Laravel-REST-CMS

Issues (76)

Security Analysis not enabled

app/Http/routes.php (1 issue)

Labels

Severity

Introduced By

Upgrade to new PHP Analysis Engine

Duplication Side-by-Side

Filter issues like