Issues (62)

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.

Replay/ReplayService.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
/*
4
 * THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
5
 * "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
6
 * LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
7
 * A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
8
 * OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
9
 * SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
10
 * LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
11
 * DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
12
 * THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
13
 * (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
14
 * OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
15
 *
16
 * The software is based on the Axon Framework project which is
17
 * licensed under the Apache 2.0 license. For more information on the Axon Framework
18
 * see <http://www.axonframework.org/>.
19
 *
20
 * This software consists of voluntary contributions made by many individuals
21
 * and is licensed under the MIT license. For more information, see
22
 * <http://www.governor-framework.org/>.
23
 */
24
25
namespace Governor\Bundle\GovernorBundle\Replay;
26
27
use Governor\Framework\EventHandling\Amqp\AmqpTerminal;
28
use Governor\Framework\EventHandling\Replay\DiscardingIncomingMessageHandler;
29
use Governor\Framework\EventHandling\InMemoryEventListenerRegistry;
30
use Governor\Framework\EventHandling\Replay\ReplayingEventBus;
31
use Governor\Framework\EventHandling\SimpleEventBus;
32
use Psr\Log\LoggerInterface;
33
use Psr\Log\LoggerAwareInterface;
34
use PhpAmqpLib\Connection\AMQPConnection;
35
use Governor\Framework\EventStore\Management\EventStoreManagementInterface;
36
use Governor\Framework\UnitOfWork\DefaultUnitOfWork;
37
use Governor\Framework\Serializer\SerializerInterface;
38
use Governor\Framework\EventHandling\Amqp\RoutingKeyResolverInterface;
39
use Governor\Framework\EventHandling\Amqp\DefaultAmqpMessageConverter;
40
41
/**
42
 * Description of PosInitialSynchronizationService
43
 *
44
 * @author david
45
 */
46
class ReplayService implements LoggerAwareInterface
47
{
48
49
    /**
50
     * @var EventStoreManagementInterface
51
     */
52
    private $eventStore;
53
54
    /**
55
     * @var LoggerInterface
56
     */
57
    private $logger;
58
59
    /**
60
     * @var AMQPConnection
61
     */
62
    private $connection;
63
64
    /**
65
     * @var SerializerInterface
66
     */
67
    private $serializer;
68
69
    /**
70
     * @var RoutingKeyResolverInterface
71
     */
72
    private $routingKeyResolver;
73
74
    /**
75
     * @param AMQPConnection $connection
76
     * @param EventStoreManagementInterface $eventStore
77
     * @param SerializerInterface $serializer
78
     * @param RoutingKeyResolverInterface $routingKeyResolver
79
     */
80
    function __construct(
0 ignored issues
show
It is generally recommended to explicitly declare the visibility for methods.

Adding explicit visibility (private, protected, or public) is generally recommend to communicate to other developers how, and from where this method is intended to be used.

Loading history...
81
        AMQPConnection $connection,
82
        EventStoreManagementInterface $eventStore,
83
        SerializerInterface $serializer,
84
        RoutingKeyResolverInterface $routingKeyResolver
85
    ) {
86
        $this->eventStore = $eventStore;
87
        $this->connection = $connection;
88
        $this->serializer = $serializer;
89
        $this->routingKeyResolver = $routingKeyResolver;
90
    }
91
92
    public function replay($exchange)
93
    {
94
        $channel = $this->connection->channel();
95
        $channel->tx_select();
96
97
        $uow = DefaultUnitOfWork::startAndGet();
98
99
        $eventBus = new SimpleEventBus(new InMemoryEventListenerRegistry());
100
        $terminal = new AmqpTerminal(
101
            $this->serializer,
102
            new DefaultAmqpMessageConverter($this->serializer, $this->routingKeyResolver)
103
        );
104
        $terminal->setConnection($this->connection);
105
        $terminal->setExchangeName($exchange);
106
        $eventBus->setTerminals([$terminal]);
107
108
        $replayingEventBus = new ReplayingEventBus(
109
            $eventBus, $this->eventStore,
110
            new DiscardingIncomingMessageHandler()
111
        );
112
113
        $replayingEventBus->setLogger($this->logger);
114
115
        try {
116
            $replayingEventBus->startReplay();
117
            $uow->commit();
118
            $channel->tx_commit();
119
        } catch (\Exception $ex) {
120
            $channel->tx_rollback();
121
            $uow->rollback($ex);
122
        }
123
    }
124
125
    /**
126
     * @param LoggerInterface $logger
127
     * @return null
128
     */
129
    public function setLogger(LoggerInterface $logger)
130
    {
131
        $this->logger = $logger;
132
    }
133
134
}
135