Issues in auth.php (master) - Issues in master - improv-ee/api - Measure and Improve Code Quality continuously with Scrutinizer

Issues (12)

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.

config/auth.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

<?php

return [

    /*
    |--------------------------------------------------------------------------
    | Authentication Defaults
    |--------------------------------------------------------------------------
    |
    | This option controls the default authentication "guard" and password
    | reset options for your application. You may change these defaults
    | as required, but they're a perfect start for most applications.
    |
    */

    'defaults' => [
        'guard' => 'web',
        'passwords' => 'users',
    ],

    /*
    |--------------------------------------------------------------------------
    | Authentication Guards
    |--------------------------------------------------------------------------
    |
    | Next, you may define every authentication guard for your application.
    | Of course, a great default configuration has been defined for you
    | here which uses session storage and the Eloquent user provider.
    |
    | All authentication drivers have a user provider. This defines how the
    | users are actually retrieved out of your database or other storage
    | mechanisms used by this application to persist your user's data.
    |
    | Supported: "session", "token"
    |
    */

    'guards' => [
        'web' => [
            'driver' => 'session',
            'provider' => 'users',
        ],

        'api' => [
            'driver' => 'token',
            'provider' => 'users',
        ],
    ],

    /*
    |--------------------------------------------------------------------------
    | User Providers
    |--------------------------------------------------------------------------
    |
    | All authentication drivers have a user provider. This defines how the
    | users are actually retrieved out of your database or other storage
    | mechanisms used by this application to persist your user's data.
    |
    | If you have multiple user tables or models you may configure multiple
    | sources which represent each model / table. These sources may then
    | be assigned to any extra authentication guards you have defined.
    |
    | Supported: "database", "eloquent"
    |
    */

    'providers' => [
        'users' => [
            'driver' => 'eloquent',
            'model' => App\User::class,
        ],

        // 'users' => [

        //     'driver' => 'database',

        //     'table' => 'users',

        // ],
    ],

    /*
    |--------------------------------------------------------------------------
    | Resetting Passwords
    |--------------------------------------------------------------------------
    |
    | Here you may set the options for resetting passwords including the view
    | that is your password reset e-mail. You may also set the name of the
    | table that maintains all of the reset tokens for your application.
    |
    | You may specify multiple password reset configurations if you have more
    | than one user table or model in the application and you want to have
    | separate password reset settings based on the specific user types.
    |
    | The expire time is the number of minutes that the reset token should be
    | considered valid. This security feature keeps tokens short-lived so
    | they have less time to be guessed. You may change this as needed.
    |
    */

    'passwords' => [
        'users' => [
            'provider' => 'users',
            'email' => 'auth.emails.password',
            'table' => 'password_resets',
            'expire' => 60,
        ],
    ],

];


1			<?php
2
3			return [
4
5			/*
6			\|--------------------------------------------------------------------------
7			\| Authentication Defaults
8			\|--------------------------------------------------------------------------
9			\|
10			\| This option controls the default authentication "guard" and password
11			\| reset options for your application. You may change these defaults
12			\| as required, but they're a perfect start for most applications.
13			\|
14			*/
15
16			'defaults' => [
17			'guard' => 'web',
18			'passwords' => 'users',
19			],
20
21			/*
22			\|--------------------------------------------------------------------------
23			\| Authentication Guards
24			\|--------------------------------------------------------------------------
25			\|
26			\| Next, you may define every authentication guard for your application.
27			\| Of course, a great default configuration has been defined for you
28			\| here which uses session storage and the Eloquent user provider.
29			\|
30			\| All authentication drivers have a user provider. This defines how the
31			\| users are actually retrieved out of your database or other storage
32			\| mechanisms used by this application to persist your user's data.
33			\|
34			\| Supported: "session", "token"
35			\|
36			*/
37
38			'guards' => [
39			'web' => [
40			'driver' => 'session',
41			'provider' => 'users',
42			],
43
44			'api' => [
45			'driver' => 'token',
46			'provider' => 'users',
47			],
48			],
49
50			/*
51			\|--------------------------------------------------------------------------
52			\| User Providers
53			\|--------------------------------------------------------------------------
54			\|
55			\| All authentication drivers have a user provider. This defines how the
56			\| users are actually retrieved out of your database or other storage
57			\| mechanisms used by this application to persist your user's data.
58			\|
59			\| If you have multiple user tables or models you may configure multiple
60			\| sources which represent each model / table. These sources may then
61			\| be assigned to any extra authentication guards you have defined.
62			\|
63			\| Supported: "database", "eloquent"
64			\|
65			*/
66
67			'providers' => [
68			'users' => [
69			'driver' => 'eloquent',
70			'model' => App\User::class,
71			],
72
73			// 'users' => [
			0 ignored issues – show Unused Code Comprehensibility introduced 2016-02-28 11:50 UTC by Report Bug Copy Issue Report Show Similar Issues like this `50%` 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...
74			// 'driver' => 'database',
			0 ignored issues – show Unused Code Comprehensibility introduced 2016-02-28 11:50 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...
75			// 'table' => 'users',
			0 ignored issues – show Unused Code Comprehensibility introduced 2016-02-28 11:50 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...
76			// ],
77			],
78
79			/*
80			\|--------------------------------------------------------------------------
81			\| Resetting Passwords
82			\|--------------------------------------------------------------------------
83			\|
84			\| Here you may set the options for resetting passwords including the view
85			\| that is your password reset e-mail. You may also set the name of the
86			\| table that maintains all of the reset tokens for your application.
87			\|
88			\| You may specify multiple password reset configurations if you have more
89			\| than one user table or model in the application and you want to have
90			\| separate password reset settings based on the specific user types.
91			\|
92			\| The expire time is the number of minutes that the reset token should be
93			\| considered valid. This security feature keeps tokens short-lived so
94			\| they have less time to be guessed. You may change this as needed.
95			\|
96			*/
97
98			'passwords' => [
99			'users' => [
100			'provider' => 'users',
101			'email' => 'auth.emails.password',
102			'table' => 'password_resets',
103			'expire' => 60,
104			],
105			],
106
107			];
108

improv-ee / api

Issues (12)

Security Analysis not enabled

config/auth.php (3 issues)

Labels

Severity

Introduced By

Upgrade to new PHP Analysis Engine

Duplication Side-by-Side

Filter issues like