Issues (9)

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/Endpoint/ManagerRegistryEndpointFactory.php (2 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 LunixRESTBasics\Endpoint;
3
4
use Doctrine\Common\Persistence\ManagerRegistry;
5
use LunixREST\Server\Router\Endpoint\LoggingEndpoint;
6
use LunixREST\Server\Router\EndpointFactory\LoggingEndpointFactory;
7
use Psr\Log\LoggerInterface;
8
9
/**
10
 * Class ManagerRegistryEndpointFactory
11
 * @package LunixRESTBasics\Endpoint
12
 * @deprecated in favor of the actual EndpointFactory injecting the ManagerRegistry.
13
 */
14
abstract class ManagerRegistryEndpointFactory extends LoggingEndpointFactory
0 ignored issues
show
Deprecated Code introduced by
The class LunixREST\Server\Router\...\LoggingEndpointFactory has been deprecated with message: in favor of injecting the LoggerInterface manually in EndpointFactories. This adds no additional value.

This class, trait or interface has been deprecated. The supplier of the file has supplied an explanatory message.

The explanatory message should give you some clue as to whether and when the type will be removed from the class and what other constant to use instead.

Loading history...
15
{
16
    /**
17
     * @var ManagerRegistry
18
     */
19
    protected $managerRegistry;
20
21
    /**
22
     * ManagerRegistryEndpointFactory constructor.
23
     * @param ManagerRegistry $managerRegistry
24
     * @param LoggerInterface $logger
25
     */
26 1
    public function __construct(ManagerRegistry $managerRegistry, LoggerInterface $logger)
27
    {
28 1
        $this->managerRegistry = $managerRegistry;
29 1
        parent::__construct($logger);
30 1
    }
31
32
    /**
33
     * @param string $name
34
     * @param string $version
35
     * @return LoggingEndpoint
36
     */
37 1
    protected function getLoggingEndpoint(string $name, string $version): LoggingEndpoint
38
    {
39 1
        $endpoint = $this->getManagerRegistryEndpoint($name, $version);
40 1
        $endpoint->setManagerRegistry($this->managerRegistry);
41 1
        return $endpoint;
42
    }
43
44
    /**
45
     * @param string $name
46
     * @param string $version
47
     * @return ManagerRegistryEndpoint
48
     */
49
    protected abstract function getManagerRegistryEndpoint(string $name, string $version): ManagerRegistryEndpoint;
0 ignored issues
show
The abstract declaration must precede the visibility declaration
Loading history...
50
}
51