Issues in BehatCommand.php (master) - Issues in master - richdynamix/magestead - Measure and Improve Code Quality continuously with Scrutinizer

Issues (66)

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.

src/Magestead/Command/BehatCommand.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 Magestead\Command;

use Magestead\Helper\Config;
use Symfony\Component\Console\Input\InputArgument;
use Symfony\Component\Console\Command\Command;
use Symfony\Component\Console\Input\InputInterface;
use Symfony\Component\Console\Output\OutputInterface;

/**
 * Class BehatCommand
 * @package Magestead\Command
 */
class BehatCommand extends Command

{
    protected $_projectPath;

    protected function configure()
    {
        $this->_projectPath = getcwd();

        $this->setName("behat");
        $this->setDescription("Run Behat against your project");
        $this->addArgument('option', InputArgument::OPTIONAL, 'Add options to run');
    }

    /**
     * @param InputInterface $input
     * @param OutputInterface $output
     * @return mixed
     */
    protected function execute(InputInterface $input, OutputInterface $output)
    {
        $option  = $input->getArgument('option');
        $command = $this->getCommand(new Config($output), $option);
        if (!$command) {
            return $output->writeln('<error>Command not available for this application</error>');
        }

        $output->writeln('<info>Running Behat</info>');
        $passedCommand = "vagrant ssh -c '". $command ."'";
        passthru($passedCommand);
    }

    /**
     * @param Config $config
     * @param $option
     * @return bool|string
     */
    protected function getCommand(Config $config, $option)
    {
        $type = $config->type;

        switch ($type) {
            case 'magento':
                return "cd /var/www;bin/behat $option";
                break;
switch ($x) {
    case 1:
        return 'foo';
        break; // This break is not necessary and can be left off.
}
            case 'magento2':
                return "cd /var/www/public;bin/behat $option";
                break;
switch ($x) {
    case 1:
        return 'foo';
        break; // This break is not necessary and can be left off.
}
        }

        return false;
    }
}


1		<?php namespace Magestead\Command;
2
3		use Magestead\Helper\Config;
4		use Symfony\Component\Console\Input\InputArgument;
5		use Symfony\Component\Console\Command\Command;
6		use Symfony\Component\Console\Input\InputInterface;
7		use Symfony\Component\Console\Output\OutputInterface;
8
9		/**
10		* Class BehatCommand
11		* @package Magestead\Command
12		*/
13	View Code Duplication	class BehatCommand extends Command
		0 ignored issues – show Duplication introduced 2016-04-18 21:10 UTC by Report Bug Copy Issue Report Show Similar Issues like this This class seems to be duplicated in your project. Duplicated code is one of the most pungent code smells. If you need to duplicate the same code in three or more different places, we strongly encourage you to look into extracting the code into a single class or operation. You can also find more detailed suggestions in the “Code” section of your repository. Loading history...
14		{
15		protected $_projectPath;
16
17		protected function configure()
18		{
19		$this->_projectPath = getcwd();
20
21		$this->setName("behat");
22		$this->setDescription("Run Behat against your project");
23		$this->addArgument('option', InputArgument::OPTIONAL, 'Add options to run');
24		}
25
26		/**
27		* @param InputInterface $input
28		* @param OutputInterface $output
29		* @return mixed
30		*/
31		protected function execute(InputInterface $input, OutputInterface $output)
32		{
33		$option = $input->getArgument('option');
34		$command = $this->getCommand(new Config($output), $option);
35		if (!$command) {
36		return $output->writeln('<error>Command not available for this application</error>');
37		}
38
39		$output->writeln('<info>Running Behat</info>');
40		$passedCommand = "vagrant ssh -c '". $command ."'";
41		passthru($passedCommand);
42		}
43
44		/**
45		* @param Config $config
46		* @param $option
47		* @return bool\|string
48		*/
49		protected function getCommand(Config $config, $option)
50		{
51		$type = $config->type;
		0 ignored issues – show Bug introduced 2016-04-17 22:02 UTC by Report Bug Copy Issue Report Show Similar Issues like this The property `type` does not seem to exist in `Magestead\Helper\Config`. 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...
52		switch ($type) {
53		case 'magento':
54		return "cd /var/www;bin/behat $option";
55		break;
		0 ignored issues – show Unused Code introduced 2016-04-17 22:02 UTC by Report Bug Copy Issue Report Show Similar Issues like this `break` is not strictly necessary here and could be removed. The `break` statement is not necessary if it is preceded for example by a `return` statement: switch ($x) { case 1: return 'foo'; break; // This break is not necessary and can be left off. } If you would like to keep this construct to be consistent with other `case` statements, you can safely mark this issue as a false-positive. Loading history...
56		case 'magento2':
57		return "cd /var/www/public;bin/behat $option";
58		break;
		0 ignored issues – show Unused Code introduced 2016-04-18 21:10 UTC by Report Bug Copy Issue Report Show Similar Issues like this `break` is not strictly necessary here and could be removed. The `break` statement is not necessary if it is preceded for example by a `return` statement: switch ($x) { case 1: return 'foo'; break; // This break is not necessary and can be left off. } If you would like to keep this construct to be consistent with other `case` statements, you can safely mark this issue as a false-positive. Loading history...
59		}
60
61		return false;
62		}
63		}
64

richdynamix / magestead

Issues (66)

Security Analysis not enabled

src/Magestead/Command/BehatCommand.php (4 issues)

Labels

Severity

Introduced By

Upgrade to new PHP Analysis Engine

Duplication Side-by-Side

Filter issues like