Issues in EloquentBuildsQueries.php (master) - Issues in master - recca0120/laravel-repository - Measure and Improve Code Quality continuously with Scrutinizer

Issues (20)

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/Concerns/EloquentBuildsQueries.php (4 issues)

Labels

Severity

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 Recca0120\Repository\Concerns;

use Illuminate\Database\Eloquent\Model;
use Recca0120\Repository\Method;

trait EloquentBuildsQueries
{
    /**
     * Add a where clause on the primary key to the query.
     *
     * @param  mixed  $id
     * @return $this
     */
    public function whereKey($id)
    {
        $this->methods[] = new Method(__FUNCTION__, [$id]);
class MyClass { }

$x = new MyClass();
$x->foo = true;

        return $this;
    }

    /**
     * Add a where clause on the primary key to the query.
     *
     * @param  mixed  $id
     * @return $this
     */
    public function whereKeyNot($id)
    {
        $this->methods[] = new Method(__FUNCTION__, [$id]);

        return $this;
    }

    /**
     * Set the relationships that should be eager loaded.
     *
     * @param  mixed  $relations
     * @return $this
     */
    public function with($relations)

    {
        $this->methods[] = new Method(__FUNCTION__, func_get_args());

        return $this;
    }

    /**
     * Prevent the specified relations from being eager loaded.
     *
     * @param  mixed  $relations
     * @return $this
     */
    public function without($relations)

    {
        $this->methods[] = new Method(__FUNCTION__, func_get_args());

        return $this;
    }

    /**
     * Set the underlying query builder instance.
     *
     * @param  \Illuminate\Database\Query\Builder  $query
     * @return $this
     */
    public function setQuery($query)
    {
        $this->methods[] = new Method(__FUNCTION__, [$query]);

        return $this;
    }

    /**
     * Set a model instance for the model being queried.
     *
     * @param  \Illuminate\Database\Eloquent\Model  $model
     * @return $this
     */
    public function setModel(Model $model)
    {
        $this->methods[] = new Method(__FUNCTION__, [$model]);

        return $this;
    }

    /**
     * Begin querying the model on the write connection.
     *
     * @return \Illuminate\Database\Query\Builder
     */
    public function onWriteConnection()
    {
        return $this->useWritePdo();
trait Idable {
    public function equalIds(Idable $other) {
        return $this->getId() === $other->getId();
    }
}
    }
}


1		<?php
2
3		namespace Recca0120\Repository\Concerns;
4
5		use Illuminate\Database\Eloquent\Model;
6		use Recca0120\Repository\Method;
7
8		trait EloquentBuildsQueries
9		{
10		/**
11		* Add a where clause on the primary key to the query.
12		*
13		* @param mixed $id
14		* @return $this
15		*/
16	1	public function whereKey($id)
17		{
18	1	$this->methods[] = new Method(__FUNCTION__, [$id]);
		0 ignored issues – show Bug introduced 2017-12-22 04:17 UTC by Report Bug Copy Issue Report Show Similar Issues like this The property `methods` does not exist. Did you maybe forget to declare it? In PHP it is possible to write to properties without declaring them. For example, the following is perfectly valid PHP code: class MyClass { } $x = new MyClass(); $x->foo = true; Generally, it is a good practice to explictly declare properties to avoid accidental typos and provide IDE auto-completion: class MyClass { public $foo; } $x = new MyClass(); $x->foo = true; Loading history...
19
20	1	return $this;
21		}
22
23		/**
24		* Add a where clause on the primary key to the query.
25		*
26		* @param mixed $id
27		* @return $this
28		*/
29	1	public function whereKeyNot($id)
30		{
31	1	$this->methods[] = new Method(__FUNCTION__, [$id]);
32
33	1	return $this;
34		}
35
36		/**
37		* Set the relationships that should be eager loaded.
38		*
39		* @param mixed $relations
40		* @return $this
41		*/
42	1	public function with($relations)
		0 ignored issues – show Unused Code introduced 2018-03-23 14:38 UTC by Report Bug Copy Issue Report Show Similar Issues like this The parameter `$relations` 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...
43		{
44	1	$this->methods[] = new Method(__FUNCTION__, func_get_args());
45
46	1	return $this;
47		}
48
49		/**
50		* Prevent the specified relations from being eager loaded.
51		*
52		* @param mixed $relations
53		* @return $this
54		*/
55	1	public function without($relations)
		0 ignored issues – show Unused Code introduced 2018-03-23 14:38 UTC by Report Bug Copy Issue Report Show Similar Issues like this The parameter `$relations` 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...
56		{
57	1	$this->methods[] = new Method(__FUNCTION__, func_get_args());
58
59	1	return $this;
60		}
61
62		/**
63		* Set the underlying query builder instance.
64		*
65		* @param \Illuminate\Database\Query\Builder $query
66		* @return $this
67		*/
68	1	public function setQuery($query)
69		{
70	1	$this->methods[] = new Method(__FUNCTION__, [$query]);
71
72	1	return $this;
73		}
74
75		/**
76		* Set a model instance for the model being queried.
77		*
78		* @param \Illuminate\Database\Eloquent\Model $model
79		* @return $this
80		*/
81	1	public function setModel(Model $model)
82		{
83	1	$this->methods[] = new Method(__FUNCTION__, [$model]);
84
85	1	return $this;
86		}
87
88		/**
89		* Begin querying the model on the write connection.
90		*
91		* @return \Illuminate\Database\Query\Builder
92		*/
93	1	public function onWriteConnection()
94		{
95	1	return $this->useWritePdo();
		0 ignored issues – show Bug introduced 2018-02-08 05:21 UTC by Report Bug Copy Issue Report Show Similar Issues like this It seems like `useWritePdo()` must be provided by classes using this trait. How about adding it as abstract method to this trait? This check looks for methods that are used by a trait but not required by it. To illustrate, let’s look at the following code example trait Idable { public function equalIds(Idable $other) { return $this->getId() === $other->getId(); } } The trait `Idable` provides a method `equalsId` that in turn relies on the method `getId()`. If this method does not exist on a class mixing in this trait, the method will fail. Adding the `getId()` as an abstract method to the trait will make sure it is available. Loading history...
96		}
97		}
98

recca0120 / laravel-repository

Issues (20)

Security Analysis no request data

src/Concerns/EloquentBuildsQueries.php (4 issues)

Labels

Severity

Introduced By

Upgrade to new PHP Analysis Engine

Duplication Side-by-Side

Filter issues like