Issues in CustomRule.php (master) - Issues in master - perfect-oblivion/valid - Measure and Improve Code Quality continuously with Scrutinizer

Issues (31)

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.

src/CustomRule.php (1 issue)

Labels

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

namespace PerfectOblivion\Valid;

use Illuminate\Http\Request;
use Illuminate\Contracts\Validation\Rule;
use Illuminate\Contracts\Validation\Validator;
use PerfectOblivion\Valid\Contracts\ValidationService\ValidationService;

abstract class CustomRule implements Rule
{
    /**
     * The current validator instance.
     *
     * @var \Illuminate\Contracts\Validation\Validator
     */
    protected static $validator;

    /**
     * The current FormRequest instance.
     *
     * @var \Illuminate\Http\Request
     */
    protected static $request;

    /**
     * The current ValidationService instance.
     *
     * @var \PerfectOblivion\Valid\ValidationService\ValidationService
     */
    protected static $service;

    /**
     * Set the validator property.
     *
     * @param  \Illuminate\Contracts\Validation\Validator  $validator
     */
    public static function validator(?Validator $validator = null)
    {
        if (! isset(static::$validator) && $validator) {
            static::$validator = $validator;
        }

        return static::$validator;
    }

    /**
     * Set the request property.
     *
     * @param  \Illuminate\Http\Request  $request
     */
    public static function request(?Request $request = null)
    {
        if (! isset(static::$request) && $request) {
            static::$request = $request;
        }

        return static::$request;
    }

    /**
     * Set the Validation Service property.
     *
     * @param  \PerfectOblivion\Valid\Contracts\ValidationService\ValidationService  $service
     */
    public static function service(? ValidationService $service = null)
    {
        if (! isset(static::$service) && $service) {
            static::$service = $service;
class Alien {}

class Dalek extends Alien {}

class Plot
{
    /** @var  Dalek */
    public $villain;
}

$alien = new Alien();
$plot = new Plot();
if ($alien instanceof Dalek) {
    $plot->villain = $alien;
}
        }

        return static::$service;
    }

    /**
     * Determine if the validation rule passes.
     *
     * @param  string  $attribute
     * @param  mixed  $value
     *
     * @return bool
     */
    abstract public function passes($attribute, $value);

    /**
     * Get the validation error message.
     *
     * @return string
     */
    abstract public function message();

    /**
     * Handle property accessibility for CustomRule.
     *
     * @param  string  $property
     *
     * @return mixed
     */
    public function __get($property)
    {
        if ('validator' === $property || 'request' === $property || 'service' === $property) {
            return static::$property ?? static::$property();
        }

        return $this->$property;
    }
}


1			<?php
2
3			namespace PerfectOblivion\Valid;
4
5			use Illuminate\Http\Request;
6			use Illuminate\Contracts\Validation\Rule;
7			use Illuminate\Contracts\Validation\Validator;
8			use PerfectOblivion\Valid\Contracts\ValidationService\ValidationService;
9
10			abstract class CustomRule implements Rule
11			{
12			/**
13			* The current validator instance.
14			*
15			* @var \Illuminate\Contracts\Validation\Validator
16			*/
17			protected static $validator;
18
19			/**
20			* The current FormRequest instance.
21			*
22			* @var \Illuminate\Http\Request
23			*/
24			protected static $request;
25
26			/**
27			* The current ValidationService instance.
28			*
29			* @var \PerfectOblivion\Valid\ValidationService\ValidationService
30			*/
31			protected static $service;
32
33			/**
34			* Set the validator property.
35			*
36			* @param \Illuminate\Contracts\Validation\Validator $validator
37			*/
38			public static function validator(?Validator $validator = null)
39			{
40			if (! isset(static::$validator) && $validator) {
41			static::$validator = $validator;
42			}
43
44			return static::$validator;
45			}
46
47			/**
48			* Set the request property.
49			*
50			* @param \Illuminate\Http\Request $request
51			*/
52			public static function request(?Request $request = null)
53			{
54			if (! isset(static::$request) && $request) {
55			static::$request = $request;
56			}
57
58			return static::$request;
59			}
60
61			/**
62			* Set the Validation Service property.
63			*
64			* @param \PerfectOblivion\Valid\Contracts\ValidationService\ValidationService $service
65			*/
66			public static function service(? ValidationService $service = null)
67			{
68			if (! isset(static::$service) && $service) {
69			static::$service = $service;
			0 ignored issues – show Documentation Bug introduced 2019-04-03 21:18 UTC by Report Bug Copy Issue Report Show Similar Issues like this `$service` is of type `object<PerfectOblivion\V...vice\ValidationService>`, but the property `$service` was declared to be of type `object<PerfectOblivion\V...vice\ValidationService>`. Are you sure that you always receive this specific sub-class here, or does it make sense to add an `instanceof` check? Our type inference engine has found a suspicous assignment of a value to a property. This check raises an issue when a value that can be of a given class or a super-class is assigned to a property that is type hinted more strictly. Either this assignment is in error or an instanceof check should be added for that assignment. class Alien {} class Dalek extends Alien {} class Plot { /** @var Dalek */ public $villain; } $alien = new Alien(); $plot = new Plot(); if ($alien instanceof Dalek) { $plot->villain = $alien; } Loading history...
70			}
71
72			return static::$service;
73			}
74
75			/**
76			* Determine if the validation rule passes.
77			*
78			* @param string $attribute
79			* @param mixed $value
80			*
81			* @return bool
82			*/
83			abstract public function passes($attribute, $value);
84
85			/**
86			* Get the validation error message.
87			*
88			* @return string
89			*/
90			abstract public function message();
91
92			/**
93			* Handle property accessibility for CustomRule.
94			*
95			* @param string $property
96			*
97			* @return mixed
98			*/
99			public function __get($property)
100			{
101			if ('validator' === $property \|\| 'request' === $property \|\| 'service' === $property) {
102			return static::$property ?? static::$property();
103			}
104
105			return $this->$property;
106			}
107			}
108

perfect-oblivion / valid

Issues (31)

Security Analysis no request data

src/CustomRule.php (1 issue)

Labels

Severity

Introduced By

Upgrade to new PHP Analysis Engine

Duplication Side-by-Side

Filter issues like