Issues (150)

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/Dispatcher/EventClassDispatcher.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 PEIP\Dispatcher;
4
5
/*
6
 * To change this template, choose Tools | Templates
7
 * and open the template in the editor.
8
 */
9
10
/*
11
 * Description of EventClassDispatcher
12
 *
13
 * @author timo
14
 */
15
use PEIP\Event\EventBuilder;
16
use PEIP\Util\ReflectionPool;
17
18
class EventClassDispatcher extends \PEIP\Dispatcher\ObjectMapDispatcher
19
{
20
    /**
21
     * Notifies all listeners of a given event-object.
22
     *
23
     * @param string                $name   name of the event
24
     * @param \PEIP\INF\Event\Event $object an event object
25
     *
26
     * @return bool|null
27
     */
28 View Code Duplication
    public function notify($name, $object)
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...
29
    {
30
        if ($object instanceof \PEIP\INF\Event\Event) {
31
            if (is_object($object->getContent())) {
32
                return self::doNotify(
33
                    $this->getListeners(
34
                        $name,
35
                        $object
36
                        ),
37
                        $object->getContent()
38
                    );
39
            } else {
40
                throw new \InvalidArgumentException('instance of \PEIP\INF\Event\Event must contain subject');
41
            }
42
        } else {
43
            throw new \InvalidArgumentException('object must be instance of \PEIP\INF\Event\Event');
44
        }
45
    }
46
47
       //put your code here
48
49
    /**
50
     * Creates an event-object with given object as content/subject and notifies
51
     * all registers listeners of the event.
52
     *
53
     * @param string $name       name of the event
54
     * @param object $object     the subject of the event
55
     * @param array  $headers    headers of the event-object as key/value pairs
56
     * @param string $eventClass event-class to create instances from
57
     *
58
     * @return
59
     */
60 View Code Duplication
    public function buildAndNotify($name, $object, array $headers = [], $eventClass = false, $type = false)
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...
61
    {
62
        if (!$this->hasListeners($name, ($object))) {
63
            return false;
64
        }
65
66
        return $this->notify(
67
                $name,
68
                EventBuilder::getInstance($eventClass)->build(
0 ignored issues
show
It seems like $eventClass defined by parameter $eventClass on line 60 can also be of type false; however, PEIP\Event\EventBuilder::getInstance() does only seem to accept string, maybe add an additional type check?

This check looks at variables that have been passed in as parameters and are passed out again to other methods.

If the outgoing method call has stricter type requirements than the method itself, an issue is raised.

An additional type check may prevent trouble.

Loading history...
69
                    $object,
70
                    $name,
71
                    $headers,
72
                    (string) $type
0 ignored issues
show
The call to EventBuilder::build() has too many arguments starting with (string) $type.

This check compares calls to functions or methods with their respective definitions. If the call has more arguments than are defined, it raises an issue.

If a function is defined several times with a different number of parameters, the check may pick up the wrong definition and report false positives. One codebase where this has been known to happen is Wordpress.

In this case you can add the @ignore PhpDoc annotation to the duplicate definition and it will be ignored.

Loading history...
73
                )
74
        );
75
    }
76
77
    /**
78
     * Checks wether an object has a listener for an event.
79
     *
80
     * @param string $name   the event-name
81
     * @param object $object object to check for listeners
82
     *
83
     * @return bool
84
     */
85
    public function hasListeners($name, $object)
86
    {
87
        return parent::hasListeners(
88
            $name,
89
            ReflectionPool::getInstance($object)
90
        );
91
    }
92
}
93