Issues (8)

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.

src/ContainerInterface.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
 * easyProperty.com
4
 *
5
 * @link      www.easyproperty.com
6
 * @copyright Copyright (c) 2016 easyproperty.com
7
 * @license   Proprietary
8
 */
9
namespace Fuel\Config;
10
11
/**
12
 * Holds configuration data
13
 */
14
interface ContainerInterface
15
{
16
	/**
17
	 * Returns the environment
18
	 *
19
	 * @return string
20
	 */
21
	public function getEnvironment();
22
23
	/**
24
	 * Sets the environment
25
	 *
26
	 * @param string $enviroment
0 ignored issues
show
There is no parameter named $enviroment. Did you maybe mean $environment?

This check looks for PHPDoc comments describing methods or function parameters that do not exist on the corresponding method or function. It has, however, found a similar but not annotated parameter which might be a good fit.

Consider the following example. The parameter $ireland is not defined by the method finale(...).

/**
 * @param array $germany
 * @param array $ireland
 */
function finale($germany, $island) {
    return "2:1";
}

The most likely cause is that the parameter was changed, but the annotation was not.

Loading history...
27
	 */
28
	public function setEnvironment($environment);
29
30
	/**
31
	 * Unloads a config group
32
	 *
33
	 * @param string $group
34
	 */
35
	public function unload($group);
36
37
	/**
38
	 * Reloads a group
39
	 *
40
	 * @param string         $name
41
	 * @param string|boolean $group
42
	 *
43
	 * @return array|null
44
	 */
45
	public function reload($name, $group = true);
46
47
	/**
48
	 * Loads a config file
49
	 *
50
	 * @param string              $name
51
	 * @param null|string|boolean $group
52
	 *
53
	 * @return array|null
54
	 */
55
	public function load($name, $group = null);
56
57
	/**
58
	 * Stores a config file
59
	 *
60
	 * @param string      $group
61
	 * @param string|null $destination
62
	 *
63
	 * @throws \RuntimeException
64
	 */
65
	public function save($group, $destination = null);
66
67
	/**
68
	 * Adds a path
69
	 *
70
	 * @param string $path
71
	 *
72
	 * @return $this
73
	 */
74
	public function addPath($path);
75
76
	/**
77
	 * Adds paths to look in
78
	 *
79
	 * @param array $paths
80
	 */
81
	public function addPaths(array $paths);
82
83
	/**
84
	 * Removes a path
85
	 *
86
	 * @param string $path
87
	 */
88
	public function removePath($path);
89
90
	/**
91
	 * Removes paths
92
	 *
93
	 * @param  array $paths
94
	 */
95
	public function removePaths(array $paths);
96
97
	/**
98
	 * Delete data from the container
99
	 *
100
	 * @param   string $key key to delete
101
	 *
102
	 * @return  boolean  delete success boolean
103
	 * @since   2.0.0
104
	 */
105
	public function delete($key);
106
}
107