GitHub Access Token became invalid

It seems like the GitHub access token used for retrieving details about this repository from GitHub became invalid. This might prevent certain types of inspections from being run (in particular, everything related to pull requests).
Please ask an admin of your repository to re-new the access token on this website.

Issues (41)

Security Analysis    no request data  

This project does not seem to handle request data directly as such no vulnerable execution paths were found.

  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.

Command/ExecuteActionCommand.php (1 issue)

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

1
<?php
2
/**
3
 * This file is part of the Global Trading Technologies Ltd workflow-extension-bundle package.
4
 *
5
 * For the full copyright and license information, please view the LICENSE
6
 * file that was distributed with this source code.
7
 *
8
 * (c) fduch <[email protected]>
9
 * @date 28.07.16
10
 */
11
12
namespace Gtt\Bundle\WorkflowExtensionsBundle\Command;
13
14
use Gtt\Bundle\WorkflowExtensionsBundle\Action\Executor as ActionExecutor;
15
use Gtt\Bundle\WorkflowExtensionsBundle\WorkflowSubject\SubjectManipulator;
16
use Symfony\Component\Workflow\Registry as WorkflowRegistry;
17
use Gtt\Bundle\WorkflowExtensionsBundle\WorkflowContext;
18
use Symfony\Component\Console\Command\Command;
19
use Symfony\Component\Console\Input\InputInterface;
20
use Symfony\Component\Console\Input\InputOption;
21
use Symfony\Component\Console\Output\OutputInterface;
22
23
/**
24
 * Console command executes action
25
 *
26
 * Useful for scheduled execution
27
 */
28
class ExecuteActionCommand extends Command
29
{
30
    /**
31
     * Command name
32
     */
33
    const COMMAND_NAME = 'workflow:action:execute';
34
35
    /**
36
     * Action executor
37
     *
38
     * @var ActionExecutor
39
     */
40
    private $actionExecutor;
41
42
    /**
43
     * Workflow registry
44
     *
45
     * @var WorkflowRegistry
46
     */
47
    private $workflowRegistry;
48
49
    /**
50
     * Subject manipulator
51
     *
52
     * @var SubjectManipulator
53
     */
54
    private $subjectManipulator;
55
56
    /**
57
     * ExecuteActionCommand constructor.
58
     *
59
     * @param ActionExecutor     $actionExecutor
60
     * @param WorkflowRegistry   $workflowRegistry
61
     * @param SubjectManipulator $subjectManipulator
62
     */
63
    public function __construct(ActionExecutor $actionExecutor, WorkflowRegistry $workflowRegistry, SubjectManipulator $subjectManipulator)
64
    {
65
        $this->actionExecutor     = $actionExecutor;
66
        $this->workflowRegistry   = $workflowRegistry;
67
        $this->subjectManipulator = $subjectManipulator;
68
69
        parent::__construct();
70
    }
71
72
73
    /**
74
     * {@inheritdoc}
75
     */
76
    protected function configure()
77
    {
78
        $this
79
            ->setDefinition(array(
80
                new InputOption(
81
                    'action',
82
                    null,
83
                    InputOption::VALUE_REQUIRED,
84
                    'Action name should be executed'
85
                ),
86
                new InputOption(
87
                    'arguments',
88
                    null,
89
                    InputOption::VALUE_REQUIRED,
90
                    'Json-encoded list of action parameters'
91
                ),
92
                new InputOption(
93
                    'workflow',
94
                    'w',
95
                    InputOption::VALUE_REQUIRED,
96
                    'Name of the current workflow'
97
                ),
98
                new InputOption(
99
                    'subjectId',
100
                    'sid',
101
                    InputOption::VALUE_REQUIRED,
102
                    'Id of the workflow subject'
103
                ),
104
                new InputOption(
105
                    'subjectClass',
106
                    null,
107
                    InputOption::VALUE_REQUIRED,
108
                    'FQCN of the workflow subject'
109
                )
110
            ))
111
            ->setName(static::COMMAND_NAME)
112
            ->setDescription('Execute action command')
113
            ->setHelp(<<<EOT
114
This <info>%command.name%</info> executes action by name with parameters specified
115
EOT
116
            );
117
    }
118
119
    /**
120
     * Tries to execute action specified
121
     *
122
     * {@inheritdoc}
123
     */
124
    protected function execute(InputInterface $input, OutputInterface $output)
125
    {
126
        $actionName        = $input->getOption('action');
127
        $encodedParameters = $input->getOption('arguments');
128
        $parameters        = json_decode($encodedParameters);
129
130
        $workflowName = $input->getOption('workflow');
131
        $subjectClass = $input->getOption('subjectClass');
132
        $subjectId    = $input->getOption('subjectId');
133
134
        $subject  = $this->subjectManipulator->getSubjectFromDomain($subjectClass, $subjectId);
135
        $workflowContext = new WorkflowContext($this->workflowRegistry->get($subject, $workflowName), $subject, $subjectId);
0 ignored issues
show
$subject is of type array, but the function expects a object.

It seems like the type of the argument is not accepted by the function/method which you are calling.

In some cases, in particular if PHP’s automatic type-juggling kicks in this might be fine. In other cases, however this might be a bug.

We suggest to add an explicit type cast like in the following example:

function acceptsInteger($int) { }

$x = '123'; // string "123"

// Instead of
acceptsInteger($x);

// we recommend to use
acceptsInteger((integer) $x);
Loading history...
136
137
        $this->actionExecutor->execute($workflowContext, $actionName, $parameters);
138
    }
139
}