Issues in UserTypesAssociatedToUserBehavior.php (master) - Issues in master - flipboxfactory/organizations - Measure and Improve Code Quality continuously with Scrutinizer

Issues (55)

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.

behaviors/UserTypesAssociatedToUserBehavior.php (1 issue)

Labels

Bug 1

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 flipbox\organizations\behaviors;

use craft\elements\User;
use flipbox\craft\ember\helpers\QueryHelper;
use flipbox\organizations\elements\Organization;
use flipbox\organizations\relationships\RelationshipInterface;
use flipbox\organizations\relationships\UserTypeRelationship;
use flipbox\organizations\queries\UserTypeQuery;
use flipbox\organizations\records\UserType;
use Tightenco\Collect\Support\Collection;
use yii\base\Behavior;
use yii\base\Exception;

/**
 * @property User|OrganizationsAssociatedToUserBehavior $owner;
 */
class UserTypesAssociatedToUserBehavior extends Behavior
{
    /**
     * @param Organization|int $organization
     * @return RelationshipInterface
     * @throws Exception
     */
    public function getUserTypes($organization): RelationshipInterface
    {
        return $this->owner->getOrganizations()
            ->findOrFail($organization)
            ->getTypes();
    }

    /**
     * @param array $criteria
     * @return UserTypeQuery
     */
    public function userTypeQuery($criteria = []): UserTypeQuery
    {
        $query = UserType::find()
            ->user($this->owner);
/**
 * @return array|string
 */
function returnsDifferentValues($x) {
    if ($x) {
        return 'foo';
    }

    return array();
}

$x = returnsDifferentValues($y);
if (is_array($x)) {
    // $x is an array.
}

        if (!empty($criteria)) {
            QueryHelper::configure(
                $query,
                $criteria
            );
        }

        return $query;
    }
}


1			<?php
2
3			namespace flipbox\organizations\behaviors;
4
5			use craft\elements\User;
6			use flipbox\craft\ember\helpers\QueryHelper;
7			use flipbox\organizations\elements\Organization;
8			use flipbox\organizations\relationships\RelationshipInterface;
9			use flipbox\organizations\relationships\UserTypeRelationship;
10			use flipbox\organizations\queries\UserTypeQuery;
11			use flipbox\organizations\records\UserType;
12			use Tightenco\Collect\Support\Collection;
13			use yii\base\Behavior;
14			use yii\base\Exception;
15
16			/**
17			* @property User\|OrganizationsAssociatedToUserBehavior $owner;
18			*/
19			class UserTypesAssociatedToUserBehavior extends Behavior
20			{
21			/**
22			* @param Organization\|int $organization
23			* @return RelationshipInterface
24			* @throws Exception
25			*/
26			public function getUserTypes($organization): RelationshipInterface
27			{
28			return $this->owner->getOrganizations()
29			->findOrFail($organization)
30			->getTypes();
31			}
32
33			/**
34			* @param array $criteria
35			* @return UserTypeQuery
36			*/
37			public function userTypeQuery($criteria = []): UserTypeQuery
38			{
39			$query = UserType::find()
40			->user($this->owner);
			0 ignored issues – show Bug introduced 2019-01-10 20:11 UTC by Report Bug Copy Issue Report Show Similar Issues like this It seems like `$this->owner` can also be of type `object<yii\base\Component>`; however, `flipbox\craft\ember\quer...rAttributeTrait::user()` does only seem to accept `string\|array<integer,str...ft\elements\User>>\|null`, maybe add an additional type check? If a method or function can return multiple different values and unless you are sure that you only can receive a single value in this context, we recommend to add an additional type check: /** * @return array\|string */ function returnsDifferentValues($x) { if ($x) { return 'foo'; } return array(); } $x = returnsDifferentValues($y); if (is_array($x)) { // $x is an array. } If this a common case that PHP Analyzer should handle natively, please let us know by opening an issue. Loading history...
41
42			if (!empty($criteria)) {
43			QueryHelper::configure(
44			$query,
45			$criteria
46			);
47			}
48
49			return $query;
50			}
51			}
52

flipboxfactory / organizations

Issues (55)

Security Analysis not enabled

behaviors/UserTypesAssociatedToUserBehavior.php (1 issue)

Labels

Severity

Introduced By

Upgrade to new PHP Analysis Engine

Duplication Side-by-Side

Filter issues like