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/ABS/Channel/SubscribableChannel.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
3
namespace PEIP\ABS\Channel;
4
5
namespace PEIP\ABS\Channel;
6
7
/*
8
 * This file is part of the PEIP package.
9
 * (c) 2009-2016 Timo Michna <timomichna/yahoo.de>
10
 *
11
 * For the full copyright and license information, please view the LICENSE
12
 * file that was distributed with this source code.
13
 */
14
15
/*
16
 * PEIP\ABS\Channel\SubscribableChannel
17
 * Abstract base class for subscribable channels
18
 *
19
 * @author Timo Michna <timomichna/yahoo.de>
20
 * @package PEIP
21
 * @subpackage channel
22
 * @extends \PEIP\ABS\Channel\Channel
23
 * @implements \PEIP\INF\Event\Connectable, \PEIP\INF\Channel\Channel, \PEIP\INF\Channel\SubscribableChannel
24
 */
25
26
27
use PEIP\Dispatcher\Dispatcher;
28
use PEIP\Util\Test;
29
30
abstract class SubscribableChannel extends \PEIP\ABS\Channel\Channel implements \PEIP\INF\Channel\SubscribableChannel
31
{
32
    protected $messageDispatcher;
33
34
    /**
35
     * Subscribes a given listener to the channel.
36
     *
37
     * @event subscribe
38
     *
39
     * @param callable|PEIP\INF\Handler\Handler $handler the listener to subscribe
40
     *
41
     * @return
42
     */
43
    public function subscribe($handler)
44
    {
45
        Test::ensureHandler($handler);
46
        $this->getMessageDispatcher()->connect($handler);
47
        $this->doFireEvent('subscribe', ['SUBSCRIBER' => $handler]);
48
    }
49
50
    /**
51
     * Unsubscribes a given listener from the channel.
52
     *
53
     * @event unsubscribe
54
     *
55
     * @param callable|PEIP\INF\Handler\Handler $handler the listener to unsubscribe
56
     *
57
     * @return
58
     */
59
    public function unsubscribe($handler)
60
    {
61
        Test::ensureHandler($handler);
62
        $this->getMessageDispatcher()->disconnect($handler);
63
        $this->doFireEvent('unsubscribe', ['SUBSCRIBER' => $handler]);
64
    }
65
66
    /**
67
     * Sets the message dispatcher resposible for notifying all subscribers about new messages.
68
     *
69
     * @param \PEIP\INF\Dispatcher\Dispatcher $dispatcher        instance of \PEIP\INF\Dispatcher\Dispatcher
70
     * @param bool                            $transferListeners wether to transfer listeners of old dispatcher (if set) to new one. default: true
71
     *
72
     * @return
73
     */
74
    public function setMessageDispatcher(\PEIP\INF\Dispatcher\Dispatcher $dispatcher, $transferListeners = true)
75
    {
76 View Code Duplication
        if (isset($this->dispatcher) && $transferListeners) {
0 ignored issues
show
This code seems to be duplicated across 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...
77
            foreach ($this->dispatcher->getListeners() as $listener) {
0 ignored issues
show
The property dispatcher does not seem to exist. Did you mean messageDispatcher?

An attempt at access to an undefined property has been detected. This may either be a typographical error or the property has been renamed but there are still references to its old name.

If you really want to allow access to undefined properties, you can define magic methods to allow access. See the php core documentation on Overloading.

Loading history...
78
                $dispatcher->connect($listener);
79
                $this->dispatcher->disconnect($listener);
0 ignored issues
show
The property dispatcher does not seem to exist. Did you mean messageDispatcher?

An attempt at access to an undefined property has been detected. This may either be a typographical error or the property has been renamed but there are still references to its old name.

If you really want to allow access to undefined properties, you can define magic methods to allow access. See the php core documentation on Overloading.

Loading history...
80
            }
81
        }
82
        $this->dispatcher = $dispatcher;
0 ignored issues
show
The property dispatcher does not seem to exist. Did you mean messageDispatcher?

An attempt at access to an undefined property has been detected. This may either be a typographical error or the property has been renamed but there are still references to its old name.

If you really want to allow access to undefined properties, you can define magic methods to allow access. See the php core documentation on Overloading.

Loading history...
83
    }
84
85
    /**
86
     * Returns the message dispatcher resposible for notifying all subscribers about new messages.
87
     *
88
     * @return
89
     */
90
    public function getMessageDispatcher()
91
    {
92
        return isset($this->dispatcher) ? $this->dispatcher : $this->dispatcher = new Dispatcher();
0 ignored issues
show
The property dispatcher does not seem to exist. Did you mean messageDispatcher?

An attempt at access to an undefined property has been detected. This may either be a typographical error or the property has been renamed but there are still references to its old name.

If you really want to allow access to undefined properties, you can define magic methods to allow access. See the php core documentation on Overloading.

Loading history...
93
    }
94
}
95