Issues in CreateWalletOrder.php (master) - Issues in master - nyacide/amma - Measure and Improve Code Quality continuously with Scrutinizer

Issues (415)

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.

app/Orders/CreateWalletOrder.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 App\Orders;

use App\Repositories\WalletRepository;
use App\User;

class CreateWalletOrder extends Order
{
    /**
     * @var User
     */
    protected $user;

    /**
     * @var int
     */
    protected $test_count;

    /**
     * CreateWalletOrder constructor.
     * @param User $user
     */
    public function __construct(User $user)
    {
        $this->user = $user;
        $this->test_count = config('testing_payment.amount');

        parent::__construct();
    }

    /**
     * Method witch run's on serialize object.
     *
     * @return void.

     */
    public function handle()
    {
//        if(! $this->user->hasWallet())

        if(! $this->user->wallet()->first())
        {
            $data['amount'] = 0;
foreach ($collection as $item) {
    $myArray['foo'] = $item->getFoo();

    if ($item->hasBar()) {
        $myArray['bar'] = $item->getBar();
    }

    // do something with $myArray
}
            if($this->checkIfTestWalletPeriodOn())
''   == false // true
''   == null  // true
'ab' == false // false
'ab' == null  // false

// It is often better to use strict comparison
'' === false // false
'' === null  // false
            {
                $data['amount'] = $this->test_count;
            }

            $this->getWalletsRepository()
                ->create($this->user, $data);
        }
    }

    /**
     * Check if testing period.
     *
     * @return string|null
     */
    public function checkIfTestWalletPeriodOn()
    {
        return settings()->getOption('site::testing_payment_period');
    }

    /**
     * @return WalletRepository
     */
    private function getWalletsRepository()
    {
        return (new WalletRepository());
    }
}

1			<?php
2
3			namespace App\Orders;
4
5			use App\Repositories\WalletRepository;
6			use App\User;
7
8			class CreateWalletOrder extends Order
9			{
10			/**
11			* @var User
12			*/
13			protected $user;
14
15			/**
16			* @var int
17			*/
18			protected $test_count;
19
20			/**
21			* CreateWalletOrder constructor.
22			* @param User $user
23			*/
24			public function __construct(User $user)
25			{
26			$this->user = $user;
27			$this->test_count = config('testing_payment.amount');
28
29			parent::__construct();
30			}
31
32			/**
33			* Method witch run's on serialize object.
34			*
35			* @return void.
			0 ignored issues – show Documentation introduced 2016-12-28 08:14 UTC by Report Bug Copy Issue Report Show Similar Issues like this The doc-type `void.` could not be parsed: Unknown type name "void." at position 0. (view supported doc-types) This check marks PHPDoc comments that could not be parsed by our parser. To see which comment annotations we can parse, please refer to our documentation on supported doc-types. Loading history...
36			*/
37			public function handle()
38			{
39			// if(! $this->user->hasWallet())
			0 ignored issues – show Unused Code Comprehensibility introduced 2016-12-28 08:14 UTC by Report Bug Copy Issue Report Show Similar Issues like this `70%` 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...
40			if(! $this->user->wallet()->first())
41			{
42			$data['amount'] = 0;
			0 ignored issues – show Coding Style Comprehensibility introduced 2016-12-28 08:14 UTC by Report Bug Copy Issue Report Show Similar Issues like this `$data` was never initialized. Although not strictly required by PHP, it is generally a good practice to add `$data = array();` before regardless. Adding an explicit array definition is generally preferable to implicit array definition as it guarantees a stable state of the code. Let’s take a look at an example: foreach ($collection as $item) { $myArray['foo'] = $item->getFoo(); if ($item->hasBar()) { $myArray['bar'] = $item->getBar(); } // do something with $myArray } As you can see in this example, the array `$myArray` is initialized the first time when the foreach loop is entered. You can also see that the value of the `bar` key is only written conditionally; thus, its value might result from a previous iteration. This might or might not be intended. To make your intention clear, your code more readible and to avoid accidental bugs, we recommend to add an explicit initialization `$myArray = array()` either outside or inside the foreach loop. Loading history...
43			if($this->checkIfTestWalletPeriodOn())
			0 ignored issues – show Bug Best Practice introduced 2016-12-28 08:14 UTC by Report Bug Copy Issue Report Show Similar Issues like this The expression `$this->checkIfTestWalletPeriodOn()` of type `string\|null` is loosely compared to `true`; this is ambiguous if the string can be empty. You might want to explicitly use `!== null` instead. In PHP, under loose comparison (like `==`, or `!=`, or `switch` conditions), values of different types might be equal. For `string` values, the empty string `''` is a special case, in particular the following results might be unexpected: '' == false // true '' == null // true 'ab' == false // false 'ab' == null // false // It is often better to use strict comparison '' === false // false '' === null // false Loading history...
44			{
45			$data['amount'] = $this->test_count;
46			}
47
48			$this->getWalletsRepository()
49			->create($this->user, $data);
50			}
51			}
52
53			/**
54			* Check if testing period.
55			*
56			* @return string\|null
57			*/
58			public function checkIfTestWalletPeriodOn()
59			{
60			return settings()->getOption('site::testing_payment_period');
61			}
62
63			/**
64			* @return WalletRepository
65			*/
66			private function getWalletsRepository()
67			{
68			return (new WalletRepository());
69			}
70			}

nyacide / amma

Issues (415)

Security Analysis not enabled

app/Orders/CreateWalletOrder.php (4 issues)

Labels

Severity

Introduced By

Upgrade to new PHP Analysis Engine

Duplication Side-by-Side

Filter issues like