Issues in EnsuranceInterface.php (master) - Issues in master - Dgame/php-ensurance - Measure and Improve Code Quality continuously with Scrutinizer

Issues (16)

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/EnsuranceInterface.php (2 issues)

Labels

Documentation 2

Severity

Informational 2

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 Dgame\Ensurance;

use Throwable;

/**
 * Interface EnsuranceInterface
 * @package Dgame\Ensurance
 */
interface EnsuranceInterface
{
    /**
     * @param mixed $value
     *
     * @return mixed
     */
    public function then($value);

    /**
     * @param mixed $value
     *
     * @return mixed
     */
    public function else($value);

    /**
     * @param mixed $default
     *
     * @return mixed
     */
    public function get($default = null);

    /**
     * @return bool
     */
    public function isEnsured(): bool;

    /**
     * @param string $message
     * @param mixed  ...$args
     *
     * @return mixed
     */

    public function orThrow(string $message, ...$args);

    /**
     * @return bool
     */
    public function hasThrowable(): bool;

    /**
     * @param Throwable $throwable
     *
     * @return mixed
     */
    public function setThrowable(Throwable $throwable);

    /**
     * @return Throwable|null
     */
    public function getThrowable(): ?Throwable;

    /**
     * @return mixed
     */
    public function disregardThrowable();

    /**
     * @return Throwable|null
     */
    public function releaseThrowable(): ?Throwable;

    /**
     * @param self $ensurance

     *
     * @return mixed
     */
    public function transferEnsurance(self $ensurance);
}


1			<?php
2
3			namespace Dgame\Ensurance;
4
5			use Throwable;
6
7			/**
8			* Interface EnsuranceInterface
9			* @package Dgame\Ensurance
10			*/
11			interface EnsuranceInterface
12			{
13			/**
14			* @param mixed $value
15			*
16			* @return mixed
17			*/
18			public function then($value);
19
20			/**
21			* @param mixed $value
22			*
23			* @return mixed
24			*/
25			public function else($value);
26
27			/**
28			* @param mixed $default
29			*
30			* @return mixed
31			*/
32			public function get($default = null);
33
34			/**
35			* @return bool
36			*/
37			public function isEnsured(): bool;
38
39			/**
40			* @param string $message
41			* @param mixed ...$args
42			*
43			* @return mixed
44			*/
			0 ignored issues – show Documentation introduced 2018-03-30 15:48 UTC by Report Bug Copy Issue Report Show Similar Issues like this Consider making the type for parameter `$args` a bit more specific; maybe use `array`. Loading history...
45			public function orThrow(string $message, ...$args);
46
47			/**
48			* @return bool
49			*/
50			public function hasThrowable(): bool;
51
52			/**
53			* @param Throwable $throwable
54			*
55			* @return mixed
56			*/
57			public function setThrowable(Throwable $throwable);
58
59			/**
60			* @return Throwable\|null
61			*/
62			public function getThrowable(): ?Throwable;
63
64			/**
65			* @return mixed
66			*/
67			public function disregardThrowable();
68
69			/**
70			* @return Throwable\|null
71			*/
72			public function releaseThrowable(): ?Throwable;
73
74			/**
75			* @param self $ensurance
			0 ignored issues – show Documentation introduced 2018-03-30 15:48 UTC by Report Bug Copy Issue Report Show Similar Issues like this Should the type for parameter `$ensurance` not be `\self`? This check looks for `@param` annotations where the type inferred by our type inference engine differs from the declared type. It makes a suggestion as to what type it considers more descriptive. Most often this is a case of a parameter that can be null in addition to its declared types. Loading history...
76			*
77			* @return mixed
78			*/
79			public function transferEnsurance(self $ensurance);
80			}
81

Dgame / php-ensurance

Issues (16)

Security Analysis no request data

src/EnsuranceInterface.php (2 issues)

Labels

Severity

Introduced By

Upgrade to new PHP Analysis Engine

Duplication Side-by-Side

Filter issues like