Issues (55)

Security Analysis    no request data  

This project does not seem to handle request data directly as such no vulnerable execution paths were found.

  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.

src/Models/Client.php (1 issue)

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

1
<?php
2
3
namespace CodexShaper\OAuth2\Server\Models;
4
5
use Illuminate\Database\Eloquent\Model;
6
7
class Client extends Model
8
{
9
    /**
10
     * The database table used by the model.
11
     *
12
     * @var string
13
     */
14
    protected $table = 'oauth_clients';
15
16
    /**
17
     * The guarded attributes on the model.
18
     *
19
     * @var array
20
     */
21
    protected $guarded = [];
22
23
    /**
24
     * The attributes excluded from the model's JSON form.
25
     *
26
     * @var array
27
     */
28
    protected $hidden = [
29
        'secret',
30
    ];
31
32
    /**
33
     * The attributes that should be cast to native types.
34
     *
35
     * @var array
36
     */
37
    protected $casts = [
38
        'grant_types'               => 'array',
39
        'personal_access_client'    => 'bool',
40
        'password_client'           => 'bool',
41
        'authorization_code_client' => 'bool',
42
        'revoked'                   => 'bool',
43
    ];
44
45
    /**
46
     * Enable skip authorization.
47
     *
48
     * @var string
49
     */
50
    protected static $skipsAuthorization = false;
51
52
    /**
53
     * Get the user that the client belongs to.
54
     *
55
     * @return \Illuminate\Database\Eloquent\Relations\BelongsTo
56
     */
57
    public function user()
58
    {
59
        return $this->belongsTo(User::class);
60
    }
61
62
    /**
63
     * Get all of the authentication codes for the client.
64
     *
65
     * @return \Illuminate\Database\Eloquent\Relations\HasMany
66
     */
67
    public function authCodes()
68
    {
69
        return $this->hasMany(AuthCode::class, 'client_id');
70
    }
71
72
    /**
73
     * Get all of the tokens that belong to the client.
74
     *
75
     * @return \Illuminate\Database\Eloquent\Relations\HasMany
76
     */
77
    public function tokens()
78
    {
79
        return $this->hasMany(Token::class, 'client_id');
80
    }
81
82
    /**
83
     * Determine if the client should skip the authorization prompt.
84
     *
85
     * @return bool
86
     */
87
    public function isSkipsAuthorization()
88
    {
89
        return static::$skipsAuthorization;
90
    }
91
92
    /**
93
     * Enable or disable skip authorization.
94
     *
95
     * @return void
96
     */
97
    public static function setSkipsAuthorization($skipsAuthorization = false)
98
    {
99
        static::$skipsAuthorization = (bool) $skipsAuthorization;
0 ignored issues
show
Documentation Bug introduced by
The property $skipsAuthorization was declared of type string, but (bool) $skipsAuthorization is of type boolean. Maybe add a type cast?

This check looks for assignments to scalar types that may be of the wrong type.

To ensure the code behaves as expected, it may be a good idea to add an explicit type cast.

$answer = 42;

$correct = false;

$correct = (bool) $answer;
Loading history...
100
    }
101
102
    /**
103
     * Determine if the client is a confidential client.
104
     *
105
     * @return bool
106
     */
107
    public function isConfidential()
108
    {
109
        return !empty($this->secret);
110
    }
111
}
112