Issues in Kernel.php (master) - Issues in master - FloKnapp/faulancer - Measure and Improve Code Quality continuously with Scrutinizer

Issues (56)

Security Analysis not enabled

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/Kernel.php (1 issue)

Labels

Bug 1

Severity

Major 1

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 Faulancer;

use Faulancer\Controller\Dispatcher;
use Faulancer\Controller\ErrorController;
use Faulancer\Event\Observer;
use Faulancer\Event\Type\OnKernelError;
use Faulancer\Event\Type\OnKernelErrorException;
use Faulancer\Event\Type\OnKernelException;
use Faulancer\Event\Type\OnKernelStart;
use Faulancer\Exception\Exception;
use Faulancer\Http\Request;
use Faulancer\Service\Config;

/**
 * Class Kernel
 */
class Kernel
{

    /**
     * The current request object
     * @var Request
     */
    protected $request;

    /**
     * The configuration object
     * @var Config
     */
    protected $config;

    /**
     * Kernel constructor.
     *
     * @param Request $request
     * @param Config  $config
     */
    public function __construct(Request $request, Config $config)
    {
        $this->request = $request;
        $this->config  = $config;
    }

    /**
     * Initialize the application
     *
     * @return mixed
     * @codeCoverageIgnore
     */
    public function run()
    {
        Observer::instance()->trigger(new OnKernelStart($this));

        $dispatcher = new Dispatcher($this->request, $this->config);

        try {

            $this->registerErrorHandler();
            return $dispatcher->dispatch()->getContent();

        } catch (Exception $e) {
            Observer::instance()->trigger(new OnKernelException($this));
            return $this->showErrorPage($this->request, $e);
        } catch (\ErrorException $e) {

            Observer::instance()->trigger(new OnKernelErrorException($this));
            return $this->showErrorPage($this->request, $e);
        } catch (\Error $e) {
            Observer::instance()->trigger(new OnKernelError($this));
            return $this->showErrorPage($this->request, $e);
        }

    }

    /**
     * @param $request
     * @param $e
     * @return Http\Response
     * @codeCoverageIgnore
     */
    private function showErrorPage($request, $e)
    {
        $errorController = new ErrorController($request, $e);
        return $errorController->displayError();
    }

    /**
     * Register error handler
     */
    protected function registerErrorHandler()
    {
        set_error_handler([$this, 'errorHandler'], E_ALL);
    }

    /**
     * Custom error handler
     *
     * @param $errno
     * @param $errmsg
     * @param $errfile
     * @param $errline
     * @throws \ErrorException
     * @codeCoverageIgnore
     */
    public function errorHandler($errno, $errmsg, $errfile, $errline)
    {
        throw new \ErrorException($errmsg, $errno, 1, $errfile, $errline);
    }

}





1			<?php
2
3			namespace Faulancer;
4
5			use Faulancer\Controller\Dispatcher;
6			use Faulancer\Controller\ErrorController;
7			use Faulancer\Event\Observer;
8			use Faulancer\Event\Type\OnKernelError;
9			use Faulancer\Event\Type\OnKernelErrorException;
10			use Faulancer\Event\Type\OnKernelException;
11			use Faulancer\Event\Type\OnKernelStart;
12			use Faulancer\Exception\Exception;
13			use Faulancer\Http\Request;
14			use Faulancer\Service\Config;
15
16			/**
17			* Class Kernel
18			*/
19			class Kernel
20			{
21
22			/**
23			* The current request object
24			* @var Request
25			*/
26			protected $request;
27
28			/**
29			* The configuration object
30			* @var Config
31			*/
32			protected $config;
33
34			/**
35			* Kernel constructor.
36			*
37			* @param Request $request
38			* @param Config $config
39			*/
40			public function __construct(Request $request, Config $config)
41			{
42			$this->request = $request;
43			$this->config = $config;
44			}
45
46			/**
47			* Initialize the application
48			*
49			* @return mixed
50			* @codeCoverageIgnore
51			*/
52			public function run()
53			{
54			Observer::instance()->trigger(new OnKernelStart($this));
55
56			$dispatcher = new Dispatcher($this->request, $this->config);
57
58			try {
59
60			$this->registerErrorHandler();
61			return $dispatcher->dispatch()->getContent();
62
63			} catch (Exception $e) {
64			Observer::instance()->trigger(new OnKernelException($this));
65			return $this->showErrorPage($this->request, $e);
66			} catch (\ErrorException $e) {
			0 ignored issues – show Bug introduced 2017-10-24 23:02 UTC by Report Bug Copy Issue Report Show Similar Issues like this The class `ErrorException` does not exist. Did you forget a USE statement, or did you not list all dependencies? Scrutinizer analyzes your `composer.json`/`composer.lock` file if available to determine the classes, and functions that are defined by your dependencies. It seems like the listed class was neither found in your dependencies, nor was it found in the analyzed files in your repository. If you are using some other form of dependency management, you might want to disable this analysis. Loading history...
67			Observer::instance()->trigger(new OnKernelErrorException($this));
68			return $this->showErrorPage($this->request, $e);
69			} catch (\Error $e) {
70			Observer::instance()->trigger(new OnKernelError($this));
71			return $this->showErrorPage($this->request, $e);
72			}
73
74			}
75
76			/**
77			* @param $request
78			* @param $e
79			* @return Http\Response
80			* @codeCoverageIgnore
81			*/
82			private function showErrorPage($request, $e)
83			{
84			$errorController = new ErrorController($request, $e);
85			return $errorController->displayError();
86			}
87
88			/**
89			* Register error handler
90			*/
91			protected function registerErrorHandler()
92			{
93			set_error_handler([$this, 'errorHandler'], E_ALL);
94			}
95
96			/**
97			* Custom error handler
98			*
99			* @param $errno
100			* @param $errmsg
101			* @param $errfile
102			* @param $errline
103			* @throws \ErrorException
104			* @codeCoverageIgnore
105			*/
106			public function errorHandler($errno, $errmsg, $errfile, $errline)
107			{
108			throw new \ErrorException($errmsg, $errno, 1, $errfile, $errline);
109			}
110
111			}
112
113
114
115

FloKnapp / faulancer

Issues (56)

Security Analysis not enabled

src/Kernel.php (1 issue)

Labels

Severity

Introduced By

Upgrade to new PHP Analysis Engine

Duplication Side-by-Side

Filter issues like