Issues in api.php (master) - Issues in master - eric98/articles - Measure and Improve Code Quality continuously with Scrutinizer

Issues (69)

Security Analysis no request data

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.

routes/api.php (1 issue)

Labels

Bug 1

Severity

Major 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

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

/*
|--------------------------------------------------------------------------
| API Routes
|--------------------------------------------------------------------------
|
| Here is where you can register API routes for your application. These
| routes are loaded by the RouteServiceProvider within a group which
| is assigned the "api" middleware group. Enjoy building your API!
|
*/

Route::middleware('auth:api')->get('/user', function (Request $request) {
    return $request->user();
});

Route::group(['namespace' => "Ergare17\Articles\Http\Controllers",'middleware' => 'api','prefix' => 'api/v1', 'middleware' => ['throttle','bindings']], function () {
    Route::group(['middleware' => 'auth:api'], function () {
        Route::get('/articles', 'APIArticlesController@index');
        Route::get('/articles/{article}', 'APIArticlesController@show');
        Route::post('/articles', 'APIArticlesController@store');
        Route::put('/articles/{article}', 'APIArticlesController@update');
        Route::delete('/articles/{article}', 'APIArticlesController@destroy');

        Route::post('read-article/{article}', 'ApiReadArticleController@store');
        Route::delete('read-article/{article}', 'ApiReadArticleController@destroy');

        Route::put('description-article/{article}', 'ApiDescriptionArticleController@update');

        Route::put('user_id-article/{article}', 'ApiUserIdArticleController@update');

        Route::get('users', 'ApiUserController@index');
        Route::get('users/{user}', 'ApiUserController@show');
        Route::post('users', 'ApiUserController@store');
        Route::put('users/{user}', 'ApiUserController@update');
        Route::delete('users/{user}', 'ApiUserController@destroy');
    });
});


1			<?php
2
3			use Illuminate\Http\Request;
			0 ignored issues – show Bug introduced 2017-11-24 16:52 UTC by Report Bug Copy Issue Report Show Similar Issues like this This use statement conflicts with another class in this namespace, `Request`. 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...
4
5			/*
6			\|--------------------------------------------------------------------------
7			\| API Routes
8			\|--------------------------------------------------------------------------
9			\|
10			\| Here is where you can register API routes for your application. These
11			\| routes are loaded by the RouteServiceProvider within a group which
12			\| is assigned the "api" middleware group. Enjoy building your API!
13			\|
14			*/
15
16			Route::middleware('auth:api')->get('/user', function (Request $request) {
17			return $request->user();
18			});
19
20			Route::group(['namespace' => "Ergare17\Articles\Http\Controllers",'middleware' => 'api','prefix' => 'api/v1', 'middleware' => ['throttle','bindings']], function () {
21			Route::group(['middleware' => 'auth:api'], function () {
22			Route::get('/articles', 'APIArticlesController@index');
23			Route::get('/articles/{article}', 'APIArticlesController@show');
24			Route::post('/articles', 'APIArticlesController@store');
25			Route::put('/articles/{article}', 'APIArticlesController@update');
26			Route::delete('/articles/{article}', 'APIArticlesController@destroy');
27
28			Route::post('read-article/{article}', 'ApiReadArticleController@store');
29			Route::delete('read-article/{article}', 'ApiReadArticleController@destroy');
30
31			Route::put('description-article/{article}', 'ApiDescriptionArticleController@update');
32
33			Route::put('user_id-article/{article}', 'ApiUserIdArticleController@update');
34
35			Route::get('users', 'ApiUserController@index');
36			Route::get('users/{user}', 'ApiUserController@show');
37			Route::post('users', 'ApiUserController@store');
38			Route::put('users/{user}', 'ApiUserController@update');
39			Route::delete('users/{user}', 'ApiUserController@destroy');
40			});
41			});
42

eric98 / articles

Issues (69)

Security Analysis no request data

routes/api.php (1 issue)

Labels

Severity

Introduced By

Upgrade to new PHP Analysis Engine

Duplication Side-by-Side

Filter issues like