Issues (1131)

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/routing/RoutingCallback.class.php (5 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
namespace Agavi\Routing;
3
4
// +---------------------------------------------------------------------------+
5
// | This file is part of the Agavi package.                                   |
6
// | Copyright (c) 2005-2011 the Agavi Project.                                |
7
// |                                                                           |
8
// | For the full copyright and license information, please view the LICENSE   |
9
// | file that was distributed with this source code. You can also view the    |
10
// | LICENSE file online at http://www.agavi.org/LICENSE.txt                   |
11
// |   vi: set noexpandtab:                                                    |
12
// |   Local Variables:                                                        |
13
// |   indent-tabs-mode: t                                                     |
14
// |   End:                                                                    |
15
// +---------------------------------------------------------------------------+
16
use Agavi\Core\Context;
17
use Agavi\Dispatcher\ExecutionContainer;
18
use Agavi\Util\ParameterHolder;
19
20
/**
21
 * RoutingCallback allows you to provide callbacks into the routing
22
 *
23
 * @package    agavi
24
 * @subpackage routing
25
 *
26
 * @author     Dominik del Bondio <[email protected]>
27
 * @copyright  Authors
28
 * @copyright  The Agavi Project
29
 *
30
 * @since      0.11.0
31
 *
32
 * @version    $Id$
33
 */
34
abstract class RoutingCallback extends ParameterHolder
35
{
36
    /**
37
     * @var        Context An Context instance.
38
     */
39
    protected $context = null;
40
41
    /**
42
     * @var        array An array with information about the route.
43
     */
44
    protected $route = null;
45
46
    /**
47
     * Initialize the callback instance.
48
     *
49
     * @param      Context $context A Context instance.
50
     * @param      array   $route An array with information about the route.
51
     *
52
     * @author     Dominik del Bondio <[email protected]>
53
     * @since      0.11.0
54
     */
55
    public function initialize(Context $context, array &$route)
56
    {
57
        $this->context = $context;
58
        $this->route =& $route;
59
    }
60
61
    /**
62
     * Retrieve the current application context.
63
     *
64
     * @return     Context An Context instance.
65
     *
66
     * @author     Dominik del Bondio <[email protected]>
67
     * @since      0.11.0
68
     */
69
    final public function getContext()
70
    {
71
        return $this->context;
72
    }
73
74
    /**
75
     * Gets executed when the route of this callback route matched.
76
     *
77
     * @param      array              $parameters The parameters generated by this route.
78
     * @param      ExecutionContainer $container The original execution container.
79
     *
80
     * @return     bool Whether the routing should handle the route as matched.
81
     *
82
     * @author     Dominik del Bondio <[email protected]>
83
     * @since      0.11.0
84
     */
85
    public function onMatched(array &$parameters, ExecutionContainer $container)
0 ignored issues
show
The parameter $container 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...
86
    {
87
        return true;
88
    }
89
90
    /**
91
     * Gets executed when the route of this callback route did not match.
92
     *
93
     * @param      ExecutionContainer $container The original execution container.
94
     *
95
     * @author     Dominik del Bondio <[email protected]>
96
     * @since      0.11.0
97
     */
98
    public function onNotMatched(ExecutionContainer $container)
0 ignored issues
show
The parameter $container 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...
99
    {
100
        return;
101
    }
102
103
    /**
104
     * Gets executed when the route of this callback is about to be reverse
105
     * generated into an URL.
106
     *
107
     * @param      array $defaultParameters The default parameters stored in the route.
108
     * @param      array $userParameters The parameters the user supplied to AgaviRouting::gen().
109
     * @param      array $userOptions The options the user supplied to AgaviRouting::gen().
110
     *
111
     * @return     bool  Whether this route part should be generated.
112
     *
113
     * @author     Dominik del Bondio <[email protected]>
114
     * @since      0.11.0
115
     */
116
    public function onGenerate(array $defaultParameters, array &$userParameters, array &$userOptions)
0 ignored issues
show
The parameter $defaultParameters 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...
The parameter $userParameters 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...
The parameter $userOptions 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...
117
    {
118
        return true;
119
    }
120
}
121