Issues in ApplicationWrapperInterface.php (master) - Issues in master - limoncello-php-dist/testing - Measure and Improve Code Quality continuously with Scrutinizer

Issues (13)

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.

src/ApplicationWrapperInterface.php (4 issues)

Labels

Documentation 4

Severity

Informational 4

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 declare(strict_types=1);

namespace Limoncello\Testing;

/**
 * Copyright 2015-2020 [email protected]
 *
 * Licensed under the Apache License, Version 2.0 (the "License");
 * you may not use this file except in compliance with the License.
 * You may obtain a copy of the License at
 *
 * http://www.apache.org/licenses/LICENSE-2.0
 *
 * Unless required by applicable law or agreed to in writing, software
 * distributed under the License is distributed on an "AS IS" BASIS,
 * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 * See the License for the specific language governing permissions and
 * limitations under the License.
 */

use Closure;
use Limoncello\Contracts\Core\ApplicationInterface;

/**
 * @package Limoncello\Testing
 */
interface ApplicationWrapperInterface extends ApplicationInterface
{
    /** Called right before request will be passed through all middleware, controller and back */
    const EVENT_ON_HANDLE_REQUEST = 0;

    /** Called when response has passed back all middleware right before sending to client */
    const EVENT_ON_HANDLE_RESPONSE = self::EVENT_ON_HANDLE_REQUEST + 1;

    /** Called on empty container created (before it's set up) */
    const EVENT_ON_CONTAINER_CREATED = self::EVENT_ON_HANDLE_RESPONSE + 1;

    /** Called right before controller is called */
    const EVENT_ON_CONTAINER_LAST_CONFIGURATOR = self::EVENT_ON_CONTAINER_CREATED + 1;

    /**
     * @param Closure $handler
     *
     * @return self

     */
    public function addOnHandleRequest(Closure $handler): self;

    /**
     * @param Closure $handler
     *
     * @return self

     */
    public function addOnHandleResponse(Closure $handler): self;

    /**
     * @param Closure $handler
     *
     * @return self

     */
    public function addOnContainerCreated(Closure $handler): self;

    /**
     * @param Closure $handler
     *
     * @return self

     */
    public function addOnContainerLastConfigurator(Closure $handler): self;
}


1			<?php declare(strict_types=1);
2
3			namespace Limoncello\Testing;
4
5			/**
6			* Copyright 2015-2020 [email protected]
7			*
8			* Licensed under the Apache License, Version 2.0 (the "License");
9			* you may not use this file except in compliance with the License.
10			* You may obtain a copy of the License at
11			*
12			* http://www.apache.org/licenses/LICENSE-2.0
13			*
14			* Unless required by applicable law or agreed to in writing, software
15			* distributed under the License is distributed on an "AS IS" BASIS,
16			* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
17			* See the License for the specific language governing permissions and
18			* limitations under the License.
19			*/
20
21			use Closure;
22			use Limoncello\Contracts\Core\ApplicationInterface;
23
24			/**
25			* @package Limoncello\Testing
26			*/
27			interface ApplicationWrapperInterface extends ApplicationInterface
28			{
29			/** Called right before request will be passed through all middleware, controller and back */
30			const EVENT_ON_HANDLE_REQUEST = 0;
31
32			/** Called when response has passed back all middleware right before sending to client */
33			const EVENT_ON_HANDLE_RESPONSE = self::EVENT_ON_HANDLE_REQUEST + 1;
34
35			/** Called on empty container created (before it's set up) */
36			const EVENT_ON_CONTAINER_CREATED = self::EVENT_ON_HANDLE_RESPONSE + 1;
37
38			/** Called right before controller is called */
39			const EVENT_ON_CONTAINER_LAST_CONFIGURATOR = self::EVENT_ON_CONTAINER_CREATED + 1;
40
41			/**
42			* @param Closure $handler
43			*
44			* @return self
			0 ignored issues – show Documentation introduced 2017-05-24 04:24 UTC by Report Bug Copy Issue Report Show Similar Issues like this Should the return type not be `\self`? This check compares the return type specified in the `@return` annotation of a function or method doc comment with the types returned by the function and raises an issue if they mismatch. Loading history...
45			*/
46			public function addOnHandleRequest(Closure $handler): self;
47
48			/**
49			* @param Closure $handler
50			*
51			* @return self
			0 ignored issues – show Documentation introduced 2017-05-24 04:24 UTC by Report Bug Copy Issue Report Show Similar Issues like this Should the return type not be `\self`? This check compares the return type specified in the `@return` annotation of a function or method doc comment with the types returned by the function and raises an issue if they mismatch. Loading history...
52			*/
53			public function addOnHandleResponse(Closure $handler): self;
54
55			/**
56			* @param Closure $handler
57			*
58			* @return self
			0 ignored issues – show Documentation introduced 2017-05-24 04:24 UTC by Report Bug Copy Issue Report Show Similar Issues like this Should the return type not be `\self`? This check compares the return type specified in the `@return` annotation of a function or method doc comment with the types returned by the function and raises an issue if they mismatch. Loading history...
59			*/
60			public function addOnContainerCreated(Closure $handler): self;
61
62			/**
63			* @param Closure $handler
64			*
65			* @return self
			0 ignored issues – show Documentation introduced 2017-05-24 04:24 UTC by Report Bug Copy Issue Report Show Similar Issues like this Should the return type not be `\self`? This check compares the return type specified in the `@return` annotation of a function or method doc comment with the types returned by the function and raises an issue if they mismatch. Loading history...
66			*/
67			public function addOnContainerLastConfigurator(Closure $handler): self;
68			}
69

limoncello-php-dist / testing

Issues (13)

Security Analysis no request data

src/ApplicationWrapperInterface.php (4 issues)

Labels

Severity

Introduced By

Upgrade to new PHP Analysis Engine

Duplication Side-by-Side

Filter issues like