Issues (14)

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.

code/DevTaskRunnerCronTask.php (3 issues)

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
namespace Webtorque\DevTaskRunner;
4
5
use SilverStripe\CronTask\Interfaces\CronTask;
6
use SilverStripe\Core\Config\Config;
7
use Webtorque\DevTaskRunner\Model\DevTaskRun;
8
use SilverStripe\Core\Injector\Injector;
9
use SilverStripe\Control\HTTPRequest;
10
use SilverStripe\ORM\FieldType\DBDatetime;
11
12
class DevTaskRunnerCronTask implements CronTask
13
{
14
    private static $schedule = '*/2 * * * *';
0 ignored issues
show
The property $schedule is not used and could be removed.

This check marks private properties in classes that are never used. Those properties can be removed.

Loading history...
15
16
    public function getSchedule()
0 ignored issues
show
The return type could not be reliably inferred; please add a @return annotation.

Our type inference engine in quite powerful, but sometimes the code does not provide enough clues to go by. In these cases we request you to add a @return annotation as described here.

Loading history...
17
    {
18
        return Config::inst()->get('DevTaskRunnerCronTask', 'schedule');
19
    }
20
21
    public function process()
22
    {
23
        $nextTask = DevTaskRun::get_next_task();
24
        if ($nextTask) {
25
            //create task instance
26
            $task = Injector::inst()->create($nextTask->Task);
27
28
            //get params
29
            $params = explode(' ', $nextTask->Params);
30
            $paramList = array();
31
            if ($params) {
0 ignored issues
show
Bug Best Practice introduced by
The expression $params of type array is implicitly converted to a boolean; are you sure this is intended? If so, consider using ! empty($expr) instead to make it clear that you intend to check for an array without elements.

This check marks implicit conversions of arrays to boolean values in a comparison. While in PHP an empty array is considered to be equal (but not identical) to false, this is not always apparent.

Consider making the comparison explicit by using empty(..) or ! empty(...) instead.

Loading history...
32
                foreach ($params as $param) {
33
                    $parts = explode('=', $param);
34
                    if (count($parts) === 2) {
35
                        $paramList[$parts[0]] = $parts[1];
36
                    }
37
                }
38
            }
39
40
            //set starting flag
41
            $nextTask->Status = 'Running';
42
            $nextTask->write();
43
            echo 'Starting task ' . $task->getTitle() . "\n";
44
45
            //execute task
46
            $request = new HTTPRequest('GET', 'dev/tasks/' . $nextTask->Task, $paramList);
47
            $task->run($request);
48
49
            //set finished flag
50
            $nextTask->Status = 'Finished';
51
            $nextTask->FinishDate = DBDatetime::now()->getValue();
52
            $nextTask->write();
53
            echo 'Finished task ' . $task->getTitle() . "\n";
54
        }
55
    }
56
}