Issues (201)

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/Conflict/ModuleConflictDetector.php (1 issue)

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
/*
4
 * This file is part of the puli/manager package.
5
 *
6
 * (c) Bernhard Schussek <[email protected]>
7
 *
8
 * For the full copyright and license information, please view the LICENSE
9
 * file that was distributed with this source code.
10
 */
11
12
namespace Puli\Manager\Conflict;
13
14
/**
15
 * Detects configuration conflicts between modules.
16
 *
17
 * Modules may claim "tokens" for themselves. A token, in that sense, can be
18
 * any integer or string. If modules claim the same token, a conflict is
19
 * raised:
20
 *
21
 * ```php
22
 * use Puli\Manager\Conflict\ModuleConflictDetector;
23
 *
24
 * $detector = new ModuleConflictDetector();
25
 * $detector->claim('/app/config', 'module1');
26
 * $detector->claim('/app/views', 'module2');
27
 *
28
 * $conflicts = $detector->detectConflicts(array('/app/config', '/app/views'));
29
 * // => array()
30
 *
31
 * $detector->claim('/app/config', 'module2');
32
 *
33
 * $conflicts = $detector->detectConflicts(array('/app/config', '/app/views'));
34
 * // => array(ModuleConflict)
35
 * ```
36
 *
37
 * You can resolve conflicts by passing an {@link OverrideGraph} to the
38
 * detector. The override graph has module names as nodes. When the conflict
39
 * graph contains an edge from module A to module B, then module A is
40
 * considered to be overridden by module B. Claims for the same resources will
41
 * not result in conflicts for these modules:
42
 *
43
 * ```php
44
 * use Puli\Manager\Conflict\OverrideGraph;
45
 * use Puli\Manager\Conflict\ModuleConflictDetector;
46
 *
47
 * $graph = new OverrideGraph();
48
 * $graph->addModuleName('module1');
49
 * $graph->addModuleName('module2');
50
 *
51
 * // module1 is overridden by module2
52
 * $graph->addEdge('module1', 'module2');
53
 *
54
 * $detector = new ModuleConflictDetector($graph);
55
 * $detector->claim('/app/config', 'module1');
56
 * $detector->claim('/app/config', 'module2');
57
 *
58
 * // The conflict has been resolved
59
 * $conflict s= $detector->detectConflict(array('/app/config'));
60
 * // => array()
61
 * ```
62
 *
63
 * @since  1.0
64
 *
65
 * @author Bernhard Schussek <[email protected]>
66
 */
67
class ModuleConflictDetector
68
{
69
    /**
70
     * @var DependencyGraph
71
     */
72
    private $dependencyGraph;
73
74
    /**
75
     * @var bool[][]
76
     */
77
    private $tokens = array();
78
79
    /**
80
     * Creates a new conflict detector.
81
     *
82
     * @param DependencyGraph|null $dependencyGraph The graph indicating which
83
     *                                              module depends on which
84
     *                                              other module.
85
     */
86 73
    public function __construct(DependencyGraph $dependencyGraph = null)
87
    {
88 73
        $this->dependencyGraph = $dependencyGraph ?: new DependencyGraph();
89 73
    }
90
91
    /**
92
     * Claims a token for a module.
93
     *
94
     * @param int|string $token      The claimed token. Can be any integer or
95
     *                               string.
96
     * @param string     $moduleName The module name.
97
     */
98 64
    public function claim($token, $moduleName)
99
    {
100 64
        if (!isset($this->tokens[$token])) {
101 64
            $this->tokens[$token] = array();
102
        }
103
104 64
        $this->tokens[$token][$moduleName] = true;
105 64
    }
106
107
    /**
108
     * Releases a module's claim for a token.
109
     *
110
     * @param int|string $token      The claimed token. Can be any integer or
111
     *                               string.
112
     * @param string     $moduleName The module name.
113
     */
114 16
    public function release($token, $moduleName)
115
    {
116 16
        unset($this->tokens[$token][$moduleName]);
117 16
    }
118
119
    /**
120
     * Checks the passed tokens for conflicts.
121
     *
122
     * If no tokens are passed, all tokens are checked.
123
     *
124
     * A conflict is returned for every token that is claimed by two modules
125
     * that are not connected by an edge in the override graph. In other words,
126
     * if two modules A and B claim the same token, an edge must exist from A
127
     * to B (A is overridden by B) or from B to A (B is overridden by A).
128
     * Otherwise a conflict is returned.
129
     *
130
     * @param int[]|string[]|null $tokens The tokens to check. If `null`, all
0 ignored issues
show
Consider making the type for parameter $tokens a bit more specific; maybe use null|integer[].
Loading history...
131
     *                                    claimed tokens are checked for
132
     *                                    conflicts. You are advised to pass
133
     *                                    tokens if possible to improve the
134
     *                                    performance of the conflict detection.
135
     *
136
     * @return ModuleConflict[] The detected conflicts.
137
     */
138 73
    public function detectConflicts(array $tokens = null)
139
    {
140 73
        $tokens = null === $tokens ? array_keys($this->tokens) : $tokens;
141 73
        $conflicts = array();
142
143 73
        foreach ($tokens as $token) {
144
            // Claim was released
145 64
            if (!isset($this->tokens[$token])) {
146
                continue;
147
            }
148
149 64
            $moduleNames = array_keys($this->tokens[$token]);
150
151
            // Token claimed by only one module
152 64
            if (1 === count($moduleNames)) {
153 58
                continue;
154
            }
155
156 38
            $sortedNames = $this->dependencyGraph->getSortedModuleNames($moduleNames);
157 38
            $conflictingNames = array();
158
159
            // An edge must exist between each module pair in the sorted set,
160
            // otherwise the dependencies are not sufficiently defined
161 38
            for ($i = 1, $l = count($sortedNames); $i < $l; ++$i) {
162
                // Exclude recursive dependencies
163 38
                if (!$this->dependencyGraph->hasDependency($sortedNames[$i], $sortedNames[$i - 1], false)) {
164 26
                    $conflictingNames[$sortedNames[$i - 1]] = true;
165 26
                    $conflictingNames[$sortedNames[$i]] = true;
166
                }
167
            }
168
169 38
            if (count($conflictingNames) > 0) {
170 38
                $conflicts[] = new ModuleConflict($token, array_keys($conflictingNames));
171
            }
172
        }
173
174 73
        return $conflicts;
175
    }
176
}
177