Issues in BaseTestCaseMongo.php (master) - Issues in master - khepin/KhepinYamlFixturesBundle - Measure and Improve Code Quality continuously with Scrutinizer

Issues (80)

Security Analysis no request data

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.

tests/Khepin/Utils/BaseTestCaseMongo.php (17 issues)

Labels

Severity

Minor 17

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

<?php

namespace Khepin\Utils;

use Doctrine\ORM\EntityManager;
use \Mockery as m;
use Doctrine\ODM\MongoDB\Mapping\Driver\AnnotationDriver;

class BaseTestCaseMongo extends \PHPUnit_Framework_TestCase
{
    protected $doctrine;

    private function getMockAnnotatedConfig()
    {
        $mappingDriver = $this->getMetadataDriverImplementation();

        $config = m::mock('Doctrine\ODM\MongoDB\Configuration', array(
            'getProxyDir'                   => __DIR__.'/../temp',
            'getProxyNamespace'             => 'Proxy',
            'getAutoGenerateProxyClasses'   => true,
            'getClassMetadataFactoryName'   => 'Doctrine\\ODM\\MongoDB\\Mapping\\ClassMetadataFactory',
            'getMetadataDriverImpl'         => $mappingDriver,
            'getDefaultRepositoryClassName' => 'Doctrine\\ODM\\MongoDB\\DocumentRepository',
            'getMongoCmd'                   => '$',
            'getMetadataCacheImpl'          => null,
            'getHydratorDir'                => __DIR__.'/../temp',
            'getHydratorNamespace'          => 'Hydrator',
            'getAutoGenerateHydratorClasses'=> true,
            'getDefaultCommitOptions'       => array('safe' => true),
            'getDefaultDB'                  => 'khepinyamlfixturestest',
            'getRetryConnect'               => 2,
            'getRetryQuery'                 => 2,
            'getLoggerCallable'             => null,
            'getRepositoryFactory'          => new \Doctrine\ODM\MongoDB\Repository\DefaultRepositoryFactory(),
            'getPersistentCollectionFactory'=> new \Doctrine\ODM\MongoDB\PersistentCollection\DefaultPersistentCollectionFactory(),
        ));

        return $config;
    }

    /**
     * Creates default mapping driver
     *
     * @return \Doctrine\ORM\Mapping\Driver\Driver
     */
    protected function getMetadataDriverImplementation()
// Bad
class Router
{
    public function generate($path)
    {
        return $_SERVER['HOST'].$path;
    }
}

// Better
class Router
{
    private $host;

    public function __construct($host)
    {
        $this->host = $host;
    }

    public function generate($path)
    {
        return $this->host.$path;
    }
}

class Controller
{
    public function myAction(Request $request)
    {
        // Instead of
        $page = isset($_GET['page']) ? intval($_GET['page']) : 1;

        // Better (assuming you use the Symfony2 request)
        $page = $request->query->get('page', 1);
    }
}
    {
        return new AnnotationDriver(
            $_ENV['annotation_reader'],
            __DIR__.'/../Fixture/Document'
        );
    }

    /**
     * EntityManager mock object together with
     * annotation mapping driver and pdo_sqlite
     * database in memory
     *
     * @param  EventManager  $evm
/**
 * @param array $germany
 * @param array $island
 * @param array $italy
 */
function finale($germany, $island) {
    return "2:1";
}
     * @return EntityManager
     */
    protected function getDoctrine()
    {
        $config = $this->getMockAnnotatedConfig();
        $dm = \Doctrine\ODM\MongoDB\DocumentManager::create(null, $config);

        return $this->doctrine = m::mock(array(
            'getManager' => $dm,
            'getManagers' => array($dm),
            'getManagerForClass' => $dm
        ));

        // $conn = array(

        //     'driver' => 'pdo_sqlite',

        //     'memory' => true,

        //     // 'path' => __DIR__.'/../db.sqlite',
        // );

        // $config = $this->getMockAnnotatedConfig();

        // $em = EntityManager::create($conn, $config);


        // $entities = array(

        //     'Khepin\\Fixture\\Entity\\Car',
        //     'Khepin\\Fixture\\Entity\\Driver'
        // );

        // $schema = array_map(function($class) use ($em) {

        //             return $em->getClassMetadata($class);

        //         }, $entities);


        // $schemaTool = new SchemaTool($em);

        // $schemaTool->dropSchema(array());

        // $schemaTool->createSchema($schema);

        // return $this->doctrine = m::mock(array(

        //     'getEntityManager'  => $em,

        //     'getManager'        => $em,

        //     )
        // );
    }
}


1			<?php
2
3			namespace Khepin\Utils;
4
5			use Doctrine\ORM\EntityManager;
6			use \Mockery as m;
7			use Doctrine\ODM\MongoDB\Mapping\Driver\AnnotationDriver;
8
9			class BaseTestCaseMongo extends \PHPUnit_Framework_TestCase
10			{
11			protected $doctrine;
12
13			private function getMockAnnotatedConfig()
14			{
15			$mappingDriver = $this->getMetadataDriverImplementation();
16
17			$config = m::mock('Doctrine\ODM\MongoDB\Configuration', array(
18			'getProxyDir' => __DIR__.'/../temp',
19			'getProxyNamespace' => 'Proxy',
20			'getAutoGenerateProxyClasses' => true,
21			'getClassMetadataFactoryName' => 'Doctrine\\ODM\\MongoDB\\Mapping\\ClassMetadataFactory',
22			'getMetadataDriverImpl' => $mappingDriver,
23			'getDefaultRepositoryClassName' => 'Doctrine\\ODM\\MongoDB\\DocumentRepository',
24			'getMongoCmd' => '$',
25			'getMetadataCacheImpl' => null,
26			'getHydratorDir' => __DIR__.'/../temp',
27			'getHydratorNamespace' => 'Hydrator',
28			'getAutoGenerateHydratorClasses'=> true,
29			'getDefaultCommitOptions' => array('safe' => true),
30			'getDefaultDB' => 'khepinyamlfixturestest',
31			'getRetryConnect' => 2,
32			'getRetryQuery' => 2,
33			'getLoggerCallable' => null,
34			'getRepositoryFactory' => new \Doctrine\ODM\MongoDB\Repository\DefaultRepositoryFactory(),
35			'getPersistentCollectionFactory'=> new \Doctrine\ODM\MongoDB\PersistentCollection\DefaultPersistentCollectionFactory(),
36			));
37
38			return $config;
39			}
40
41			/**
42			* Creates default mapping driver
43			*
44			* @return \Doctrine\ORM\Mapping\Driver\Driver
45			*/
46			protected function getMetadataDriverImplementation()
			0 ignored issues – show Coding Style introduced 2015-12-05 21:47 UTC by Report Bug Copy Issue Report Show Similar Issues like this `getMetadataDriverImplementation` uses the super-global variable `$_ENV` which is generally not recommended. Instead of super-globals, we recommend to explicitly inject the dependencies of your class. This makes your code less dependent on global state and it becomes generally more testable: // Bad class Router { public function generate($path) { return $_SERVER['HOST'].$path; } } // Better class Router { private $host; public function __construct($host) { $this->host = $host; } public function generate($path) { return $this->host.$path; } } class Controller { public function myAction(Request $request) { // Instead of $page = isset($_GET['page']) ? intval($_GET['page']) : 1; // Better (assuming you use the Symfony2 request) $page = $request->query->get('page', 1); } } Loading history...
47			{
48			return new AnnotationDriver(
49			$_ENV['annotation_reader'],
50			__DIR__.'/../Fixture/Document'
51			);
52			}
53
54			/**
55			* EntityManager mock object together with
56			* annotation mapping driver and pdo_sqlite
57			* database in memory
58			*
59			* @param EventManager $evm
			0 ignored issues – show Bug introduced 2015-12-05 21:47 UTC by Report Bug Copy Issue Report Show Similar Issues like this There is no parameter named `$evm`. Was it maybe removed? This check looks for PHPDoc comments describing methods or function parameters that do not exist on the corresponding method or function. Consider the following example. The parameter `$italy` is not defined by the method `finale(...)`. /** * @param array $germany * @param array $island * @param array $italy */ function finale($germany, $island) { return "2:1"; } The most likely cause is that the parameter was removed, but the annotation was not. Loading history...
60			* @return EntityManager
61			*/
62			protected function getDoctrine()
63			{
64			$config = $this->getMockAnnotatedConfig();
65			$dm = \Doctrine\ODM\MongoDB\DocumentManager::create(null, $config);
66
67			return $this->doctrine = m::mock(array(
68			'getManager' => $dm,
69			'getManagers' => array($dm),
70			'getManagerForClass' => $dm
71			));
72
73			// $conn = array(
			0 ignored issues – show Unused Code Comprehensibility introduced 2017-01-11 22:38 UTC by Report Bug Copy Issue Report Show Similar Issues like this `43%` of this comment could be valid code. Did you maybe forget this after debugging? Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it. The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production. This check looks for comments that seem to be mostly valid code and reports them. Loading history...
74			// 'driver' => 'pdo_sqlite',
			0 ignored issues – show Unused Code Comprehensibility introduced 2017-01-11 22:38 UTC by Report Bug Copy Issue Report Show Similar Issues like this `58%` of this comment could be valid code. Did you maybe forget this after debugging? Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it. The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production. This check looks for comments that seem to be mostly valid code and reports them. Loading history...
75			// 'memory' => true,
			0 ignored issues – show Unused Code Comprehensibility introduced 2017-01-11 22:38 UTC by Report Bug Copy Issue Report Show Similar Issues like this `43%` of this comment could be valid code. Did you maybe forget this after debugging? Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it. The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production. This check looks for comments that seem to be mostly valid code and reports them. Loading history...
76			// // 'path' => __DIR__.'/../db.sqlite',
77			// );
78
79			// $config = $this->getMockAnnotatedConfig();
			0 ignored issues – show Unused Code Comprehensibility introduced 2017-01-11 22:38 UTC by Report Bug Copy Issue Report Show Similar Issues like this `55%` of this comment could be valid code. Did you maybe forget this after debugging? Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it. The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production. This check looks for comments that seem to be mostly valid code and reports them. Loading history...
80			// $em = EntityManager::create($conn, $config);
			0 ignored issues – show Unused Code Comprehensibility introduced 2017-01-11 22:38 UTC by Report Bug Copy Issue Report Show Similar Issues like this `54%` of this comment could be valid code. Did you maybe forget this after debugging? Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it. The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production. This check looks for comments that seem to be mostly valid code and reports them. Loading history...
81
82			// $entities = array(
			0 ignored issues – show Unused Code Comprehensibility introduced 2017-01-11 22:38 UTC by Report Bug Copy Issue Report Show Similar Issues like this `43%` of this comment could be valid code. Did you maybe forget this after debugging? Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it. The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production. This check looks for comments that seem to be mostly valid code and reports them. Loading history...
83			// 'Khepin\\Fixture\\Entity\\Car',
84			// 'Khepin\\Fixture\\Entity\\Driver'
85			// );
86
87			// $schema = array_map(function($class) use ($em) {
			0 ignored issues – show Unused Code Comprehensibility introduced 2017-01-11 22:38 UTC by Report Bug Copy Issue Report Show Similar Issues like this `58%` of this comment could be valid code. Did you maybe forget this after debugging? Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it. The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production. This check looks for comments that seem to be mostly valid code and reports them. Loading history...
88			// return $em->getClassMetadata($class);
			0 ignored issues – show Unused Code Comprehensibility introduced 2017-01-11 22:38 UTC by Report Bug Copy Issue Report Show Similar Issues like this `70%` of this comment could be valid code. Did you maybe forget this after debugging? Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it. The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production. This check looks for comments that seem to be mostly valid code and reports them. Loading history...
89			// }, $entities);
			0 ignored issues – show Unused Code Comprehensibility introduced 2017-01-11 22:38 UTC by Report Bug Copy Issue Report Show Similar Issues like this `72%` of this comment could be valid code. Did you maybe forget this after debugging? Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it. The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production. This check looks for comments that seem to be mostly valid code and reports them. Loading history...
90
91			// $schemaTool = new SchemaTool($em);
			0 ignored issues – show Unused Code Comprehensibility introduced 2017-01-11 22:38 UTC by Report Bug Copy Issue Report Show Similar Issues like this `50%` of this comment could be valid code. Did you maybe forget this after debugging? Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it. The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production. This check looks for comments that seem to be mostly valid code and reports them. Loading history...
92			// $schemaTool->dropSchema(array());
			0 ignored issues – show Unused Code Comprehensibility introduced 2017-01-11 22:38 UTC by Report Bug Copy Issue Report Show Similar Issues like this `80%` of this comment could be valid code. Did you maybe forget this after debugging? Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it. The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production. This check looks for comments that seem to be mostly valid code and reports them. Loading history...
93			// $schemaTool->createSchema($schema);
			0 ignored issues – show Unused Code Comprehensibility introduced 2017-01-11 22:38 UTC by Report Bug Copy Issue Report Show Similar Issues like this `75%` of this comment could be valid code. Did you maybe forget this after debugging? Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it. The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production. This check looks for comments that seem to be mostly valid code and reports them. Loading history...
94			// return $this->doctrine = m::mock(array(
			0 ignored issues – show Unused Code Comprehensibility introduced 2017-01-11 22:38 UTC by Report Bug Copy Issue Report Show Similar Issues like this `47%` of this comment could be valid code. Did you maybe forget this after debugging? Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it. The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production. This check looks for comments that seem to be mostly valid code and reports them. Loading history...
95			// 'getEntityManager' => $em,
			0 ignored issues – show Unused Code Comprehensibility introduced 2017-01-11 22:38 UTC by Report Bug Copy Issue Report Show Similar Issues like this `58%` of this comment could be valid code. Did you maybe forget this after debugging? Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it. The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production. This check looks for comments that seem to be mostly valid code and reports them. Loading history...
96			// 'getManager' => $em,
			0 ignored issues – show Unused Code Comprehensibility introduced 2017-01-11 22:38 UTC by Report Bug Copy Issue Report Show Similar Issues like this `58%` of this comment could be valid code. Did you maybe forget this after debugging? Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it. The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production. This check looks for comments that seem to be mostly valid code and reports them. Loading history...
97			// )
98			// );
99			}
100			}
101

khepin / KhepinYamlFixturesBundle

Issues (80)

Security Analysis no request data

tests/Khepin/Utils/BaseTestCaseMongo.php (17 issues)

Labels

Severity

Introduced By

Upgrade to new PHP Analysis Engine

Duplication Side-by-Side

Filter issues like