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/ManagerRegistry/ArrayManagerRegistry.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\ManagerRegistry;
3
4
use Doctrine\Common\Persistence\AbstractManagerRegistry;
5
6
/**
7
 * A basic implementation of Doctrine\Common\Persistence\AbstractManagerRegistry that uses an associative array as a container.
8
 * This class is so that we can use a more generic ManagerRegistry, but usually frameworks provide the implementation.
9
 * Only use this if your codebase doesn't have something more complete.
10
 * Class ArrayManagerRegistry
11
 * @package LunixRESTBasics\ManagerRegistry
12
 */
13
class ArrayManagerRegistry extends AbstractManagerRegistry
14
{
15
    /**
16
     * @var array
17
     */
18
    protected $container;
19
20
    /**
21
     * ArrayManagerRegistry constructor.
22
     * @param string $name
23
     * @param array $connections
24
     * @param array $managers
25
     * @param string $defaultConnection
26
     * @param string $defaultManager
27
     */
28 10
    public function __construct(
29
        $name,
30
        array $connections,
31
        array $managers,
32
        $defaultConnection,
33
        $defaultManager
34
    ) {
35 10
        $i = 0;
36 10
        foreach($connections as $name => $connection) {
37 6
            $this->container[$i] = $connection;
38 6
            $connections[$name] = $i;
39 6
            $i++;
40
        }
41 10
        foreach($managers as $name => $manager) {
42 6
            $this->container[$i] = $manager;
43 6
            $managers[$name] = $i;
44 6
            $i++;
45
        }
46
47 10
        parent::__construct($name, $connections, $managers, $defaultConnection, $defaultManager, null);
48 10
    }
49
50
    /**
51
     * @param string $name
52
     * @return mixed
53
     */
54 10
    protected function getService($name)
55
    {
56 10
        return $this->container[$name];
57
    }
58
59
    /**
60
     * @param string $name
61
     */
62
    protected function resetService($name)
63
    {
64
        $this->container[$name] = null;
65
        //TODO: This should recreate an object manager, however the abstract this is based off of doesn't really hint on how
66
    }
67
68
    /**
69
     * @param string $alias
70
     * @return mixed
71
     * @throws \Exception
72
     * Note that this probably should use ORMException, but that so far this class doesn't know about ORM (just persistence)
73
     */
74
    public function getAliasNamespace($alias)
75
    {
76
        foreach (array_keys($this->getManagers()) as $name) {
77
            try {
78
                return $this->getManager($name)->getConfiguration()->getEntityNamespace($alias);
0 ignored issues
show
The method getConfiguration() does not seem to exist on object<Doctrine\Common\Persistence\ObjectManager>.

This check looks for calls to methods that do not seem to exist on a given type. It looks for the method on the type itself as well as in inherited classes or implemented interfaces.

This is most likely a typographical error or the method has been renamed.

Loading history...
79
            } catch (\Exception $e) {
0 ignored issues
show
Coding Style Comprehensibility introduced by
Consider adding a comment why this CATCH block is empty.
Loading history...
80
            }
81
        }
82
        throw new \Exception("Unknown alias: $alias");
83
    }
84
}
85