Issues in MatchRoundService.php (master) - Issues in master - BigBad/golfleague - Measure and Improve Code Quality continuously with Scrutinizer

Issues (272)

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/library/Services/MatchRoundService.php (6 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 GolfLeague\Services;

use GolfLeague\Storage\Match\MatchRepository;
use GolfLeague\Storage\MatchRound\MatchRoundRepository;
use GolfLeague\Storage\Round\RoundRepository;

/**
* Our MatchService, containing all useful methods for business logic around Matches
*/
class MatchRoundService
{
    // Containing our pokemonRepository to make all our database calls to
    protected $matchRepo;

    /**
    * Loads our $matchRepo
    *
    * @param MatchRepository $matchRepo
/**
 * @param array $germany
 * @param array $island
 * @param array $italy
 */
function finale($germany, $island) {
    return "2:1";
}
    * @return MatchService

    */
    public function __construct(MatchRoundRepository $matchRoundRepo, RoundRepository $roundRepo, MatchRepository $match)
    {
        $this->matchRoundRepo = $matchRoundRepo;
class MyClass { }

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

        $this->match = $match;
class MyClass { }

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

    public function all()
    {
        return $this->matchRoundRepo->all();
    }
    /**
    * Method to get match data from input Match id
    *
    * @param mixed $matchdata
/**
 * @param array $germany
 * @param array $island
 * @param array $italy
 */
function finale($germany, $island) {
    return "2:1";
}
    * @return JSON object
    */
    public function getByMatch($matchId)
    {
        return $this->matchRoundRepo->getByMatch($matchId);
    }

    public function getByMatchAndGroup($matchdata)
    {
        //Retrieve players in group
        $players = $this->matchRoundRepo->matchGroup($matchdata['match_id'], $matchdata['group']);
        return $players;
    }
}


1			<?php namespace GolfLeague\Services;
2
3			use GolfLeague\Storage\Match\MatchRepository;
4			use GolfLeague\Storage\MatchRound\MatchRoundRepository;
5			use GolfLeague\Storage\Round\RoundRepository;
6
7			/**
8			* Our MatchService, containing all useful methods for business logic around Matches
9			*/
10			class MatchRoundService
11			{
12			// Containing our pokemonRepository to make all our database calls to
13			protected $matchRepo;
14
15			/**
16			* Loads our $matchRepo
17			*
18			* @param MatchRepository $matchRepo
			0 ignored issues – show Bug introduced 2016-01-06 18:35 UTC by Report Bug Copy Issue Report Show Similar Issues like this There is no parameter named `$matchRepo`. Was it maybe removed? This check looks for PHPDoc comments describing methods or function parameters that do not exist on the corresponding method or function. Consider the following example. The parameter `$italy` is not defined by the method `finale(...)`. /** * @param array $germany * @param array $island * @param array $italy */ function finale($germany, $island) { return "2:1"; } The most likely cause is that the parameter was removed, but the annotation was not. Loading history...
19			* @return MatchService
			0 ignored issues – show Comprehensibility Best Practice introduced 2016-01-06 18:35 UTC by Report Bug Copy Issue Report Show Similar Issues like this Adding a `@return` annotation to constructors is generally not recommended as a constructor does not have a meaningful return value. Adding a `@return` annotation to a constructor is not recommended, since a constructor does not have a meaningful return value. Please refer to the PHP core documentation on constructors. Loading history...
20			*/
21			public function __construct(MatchRoundRepository $matchRoundRepo, RoundRepository $roundRepo, MatchRepository $match)
22			{
23			$this->matchRoundRepo = $matchRoundRepo;
			0 ignored issues – show Bug introduced 2016-01-06 18:35 UTC by Report Bug Copy Issue Report Show Similar Issues like this The property `matchRoundRepo` 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...
24			$this->roundRepo = $roundRepo;
			0 ignored issues – show Bug introduced 2016-01-06 18:35 UTC by Report Bug Copy Issue Report Show Similar Issues like this The property `roundRepo` does not seem to exist. Did you mean `matchRoundRepo`? An attempt at access to an undefined property has been detected. This may either be a typographical error or the property has been renamed but there are still references to its old name. If you really want to allow access to undefined properties, you can define magic methods to allow access. See the php core documentation on Overloading. Loading history...
25			$this->match = $match;
			0 ignored issues – show Bug introduced 2016-01-06 18:35 UTC by Report Bug Copy Issue Report Show Similar Issues like this The property `match` 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...
26			}
27
28			public function all()
29			{
30			return $this->matchRoundRepo->all();
31			}
32			/**
33			* Method to get match data from input Match id
34			*
35			* @param mixed $matchdata
			0 ignored issues – show Bug introduced 2016-01-06 18:35 UTC by Report Bug Copy Issue Report Show Similar Issues like this There is no parameter named `$matchdata`. Was it maybe removed? This check looks for PHPDoc comments describing methods or function parameters that do not exist on the corresponding method or function. Consider the following example. The parameter `$italy` is not defined by the method `finale(...)`. /** * @param array $germany * @param array $island * @param array $italy */ function finale($germany, $island) { return "2:1"; } The most likely cause is that the parameter was removed, but the annotation was not. Loading history...
36			* @return JSON object
37			*/
38			public function getByMatch($matchId)
39			{
40			return $this->matchRoundRepo->getByMatch($matchId);
41			}
42
43			public function getByMatchAndGroup($matchdata)
44			{
45			//Retrieve players in group
46			$players = $this->matchRoundRepo->matchGroup($matchdata['match_id'], $matchdata['group']);
47			return $players;
48			}
49			}
50

BigBad / golfleague

Issues (272)

Security Analysis not enabled

app/library/Services/MatchRoundService.php (6 issues)

Labels

Severity

Introduced By

Upgrade to new PHP Analysis Engine

Duplication Side-by-Side

Filter issues like