Issues (22)

Security Analysis    not enabled

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.

src/Psecio/Invoke/MatchInstance.php (4 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 Psecio\Invoke;
4
5
abstract class MatchInstance
6
{
7
	/**
8
	 * Current configuration details
9
	 * @var array
10
	 */
11
	protected $config = array();
12
13
	/**
14
	 * Flag to negate the check
15
	 * @var boolean
16
	 */
17
	protected $negate = false;
18
19
	/**
20
	 * Init the object with the given confgiuration and negation flag
21
	 *
22
	 * @param array $config Configuration information
23
	 * @param boolean $negate Negation flag, default false [optional]
24
	 */
25
	public function __construct(array $config = array(), $negate = false)
0 ignored issues
show
The parameter $negate 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...
26
	{
27
		$this->setConfig($config);
28
	}
29
30
	/**
31
	 * Set the current configuration values
32
	 *
33
	 * @param array $config Configuration information
34
	 */
35
	public function setConfig(array $config)
36
	{
37
		$this->config = $config;
38
	}
39
40
	/**
41
	 * Get the current configuration, or if a key is provided
42
	 * 	try to locate that one value
43
	 *
44
	 * @param string $key Key to locate [optional]
45
	 * @return mixed Either entire config or key is found
46
	 */
47 View Code Duplication
	public function getConfig($key = null)
0 ignored issues
show
This method 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...
48
	{
49
		if ($key !== null) {
50
			return (isset($this->config[$key])) ? $this->config[$key] : null;
51
		} else {
52
			return $this->config;
53
		}
54
	}
55
56
	/**
57
	 * Get the current formatted error message
58
	 *
59
	 * @return string Error message contents
60
	 */
61
	public function getError()
62
	{
63
		$config = $this->getConfig()['data'];
64
		$message = (isset($this->error)) ? $this->error : 'There was an error on match for '.__CLASS__;
0 ignored issues
show
The property error 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...
65
		if (strpos($message, ':data') !== false) {
66
			$data = '';
0 ignored issues
show
$data is not used, you could remove the assignment.

This check looks for variable assignements that are either overwritten by other assignments or where the variable is not used subsequently.

$myVar = 'Value';
$higher = false;

if (rand(1, 6) > 3) {
    $higher = true;
} else {
    $higher = false;
}

Both the $myVar assignment in line 1 and the $higher assignment in line 2 are dead. The first because $myVar is never used and the second because $higher is always overwritten for every possible time line.

Loading history...
67
			$data = (is_array($config)) ? '['.implode(',', array_values($config)).']' : $config;
68
			$message = str_replace(':data', $data, $message);
69
		}
70
		return $message;
71
	}
72
73
	/**
74
	 * Evaluate the match
75
	 *
76
	 * @param \Psecio\Invoke\Data $data Object instance
77
	 * @return boolean Result of evaluation
78
	 */
79
	abstract public function evaluate($data);
80
}