Issues in Tester.php (master) - Issues in master - brianium/paratest - Measure and Improve Code Quality continuously with Scrutinizer

Issues (76)

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/Console/Testers/Tester.php (2 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

declare(strict_types=1);

namespace ParaTest\Console\Testers;

use Symfony\Component\Console\Command\Command;
use Symfony\Component\Console\Input\ArrayInput;
use Symfony\Component\Console\Input\InputInterface;
use Symfony\Component\Console\Output\OutputInterface;

/**
 * Class Tester.
 *
 * A base for Testers. A Tester is a specialized console
 * command for controlling a given tool - i.e PHPUnit
 */
abstract class Tester
{
    /**
     * Configures the ParaTestCommand with Tester specific
     * definitions.
     *
     * @param Command $command
     *
     * @return mixed
     */
    abstract public function configure(Command $command);

    /**
     * @param InputInterface  $input
     * @param OutputInterface $output
     *
     * @return mixed
     */
    abstract public function execute(InputInterface $input, OutputInterface $output);

    /**
     * Returns non-empty options.
     *
     * @param InputInterface $input
     *
     * @return array
     */
    protected function getOptions(InputInterface $input): array
    {
        $options = $input->getOptions();
        foreach ($options as $key => $value) {
            if (empty($options[$key])) {
                unset($options[$key]);
            }
        }

        return $options;
    }

    /**
     * Displays help for the ParaTestCommand.
     *
     * @param InputInterface  $input
     * @param OutputInterface $output
     */
    protected function displayHelp(InputInterface $input, OutputInterface $output)

    {
        $help = $this->command->getApplication()->find('help');
class MyClass { }

$x = new MyClass();
$x->foo = true;
        $input = new ArrayInput(['command_name' => 'paratest']);
        $help->run($input, $output);
        exit(0);
    }
}


1		<?php
2
3		declare(strict_types=1);
4
5		namespace ParaTest\Console\Testers;
6
7		use Symfony\Component\Console\Command\Command;
8		use Symfony\Component\Console\Input\ArrayInput;
9		use Symfony\Component\Console\Input\InputInterface;
10		use Symfony\Component\Console\Output\OutputInterface;
11
12		/**
13		* Class Tester.
14		*
15		* A base for Testers. A Tester is a specialized console
16		* command for controlling a given tool - i.e PHPUnit
17		*/
18		abstract class Tester
19		{
20		/**
21		* Configures the ParaTestCommand with Tester specific
22		* definitions.
23		*
24		* @param Command $command
25		*
26		* @return mixed
27		*/
28		abstract public function configure(Command $command);
29
30		/**
31		* @param InputInterface $input
32		* @param OutputInterface $output
33		*
34		* @return mixed
35		*/
36		abstract public function execute(InputInterface $input, OutputInterface $output);
37
38		/**
39		* Returns non-empty options.
40		*
41		* @param InputInterface $input
42		*
43		* @return array
44		*/
45	4	protected function getOptions(InputInterface $input): array
46		{
47	4	$options = $input->getOptions();
48	4	foreach ($options as $key => $value) {
49	4	if (empty($options[$key])) {
50	4	unset($options[$key]);
51		}
52		}
53
54	4	return $options;
55		}
56
57		/**
58		* Displays help for the ParaTestCommand.
59		*
60		* @param InputInterface $input
61		* @param OutputInterface $output
62		*/
63		protected function displayHelp(InputInterface $input, OutputInterface $output)
		0 ignored issues – show Unused Code introduced 2017-08-25 13:22 UTC by Report Bug Copy Issue Report Show Similar Issues like this The parameter `$input` 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...
64		{
65		$help = $this->command->getApplication()->find('help');
		0 ignored issues – show Bug introduced 2015-12-02 18:19 UTC by Report Bug Copy Issue Report Show Similar Issues like this The property `command` 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...
66		$input = new ArrayInput(['command_name' => 'paratest']);
67		$help->run($input, $output);
68		exit(0);
69		}
70		}
71

brianium / paratest

Issues (76)

Security Analysis no request data

src/Console/Testers/Tester.php (2 issues)

Labels

Severity

Introduced By

Upgrade to new PHP Analysis Engine

Duplication Side-by-Side

Filter issues like