Issues in CountRule.php (master) - Issues in master - phmLabs/Smoke - Measure and Improve Code Quality continuously with Scrutinizer

Issues (77)

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/Rules/Cookies/CountRule.php (1 issue)

Labels

Bug 1

Severity

Minor 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 whm\Smoke\Rules\Cookies;

use phm\HttpWebdriverClient\Http\Response\CookieAwareResponse;
use phm\HttpWebdriverClient\Http\Response\TimeoutAwareResponse;
use Psr\Http\Message\ResponseInterface;
use whm\Smoke\Rules\Attribute;
use whm\Smoke\Rules\CheckResult;
use whm\Smoke\Rules\Rule;

/**
 * This rule can validate if a http request takes longer than a given max duration.
 * A website that is slower than one second is considered as slow.
 */
class CountRule implements Rule
{
    private $maxCookies;

    /**
     * @param int $maxDuration The maximum duration a http call is allowed to take (time to first byte)
/**
 * @param array $germany
 * @param array $island
 * @param array $italy
 */
function finale($germany, $island) {
    return "2:1";
}
     */
    public function init($maxElements = 20)
    {
        $this->maxCookies = $maxElements;
    }

    public function validate(ResponseInterface $response)
    {
        if ($response instanceof CookieAwareResponse) {

            if (!$response instanceof TimeoutAwareResponse || !$response->isTimeout()) {

                $cookieCount = $response->getCookieCount();

                if ($cookieCount > $this->maxCookies) {
                    $result = new CheckResult(
                        CheckResult::STATUS_FAILURE,
                        $cookieCount . ' cookies were stored (limit was ' . $this->maxCookies . ').',
                        $cookieCount);
                } else {
                    $result = new CheckResult(
                        CheckResult::STATUS_SUCCESS,
                        $cookieCount . ' cookies were stored (limit was ' . $this->maxCookies . ').',
                        $cookieCount);
                }

                $cookies = $response->getCookies();

                $result->addAttribute(new Attribute('cookies', json_encode($cookies), true));

                return $result;
            } else {
                $result = new CheckResult(
                    CheckResult::STATUS_SKIPPED,
                    'Skipped: Request timed out. Cannot read cookies.',
                    0);

                return $result;
            }
        }
    }
}


1			<?php
2
3			namespace whm\Smoke\Rules\Cookies;
4
5			use phm\HttpWebdriverClient\Http\Response\CookieAwareResponse;
6			use phm\HttpWebdriverClient\Http\Response\TimeoutAwareResponse;
7			use Psr\Http\Message\ResponseInterface;
8			use whm\Smoke\Rules\Attribute;
9			use whm\Smoke\Rules\CheckResult;
10			use whm\Smoke\Rules\Rule;
11
12			/**
13			* This rule can validate if a http request takes longer than a given max duration.
14			* A website that is slower than one second is considered as slow.
15			*/
16			class CountRule implements Rule
17			{
18			private $maxCookies;
19
20			/**
21			* @param int $maxDuration The maximum duration a http call is allowed to take (time to first byte)
			0 ignored issues – show Bug introduced 2017-12-06 15:41 UTC by Report Bug Copy Issue Report Show Similar Issues like this There is no parameter named `$maxDuration`. 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...
22			*/
23			public function init($maxElements = 20)
24			{
25			$this->maxCookies = $maxElements;
26			}
27
28			public function validate(ResponseInterface $response)
29			{
30			if ($response instanceof CookieAwareResponse) {
31
32			if (!$response instanceof TimeoutAwareResponse \|\| !$response->isTimeout()) {
33
34			$cookieCount = $response->getCookieCount();
35
36			if ($cookieCount > $this->maxCookies) {
37			$result = new CheckResult(
38			CheckResult::STATUS_FAILURE,
39			$cookieCount . ' cookies were stored (limit was ' . $this->maxCookies . ').',
40			$cookieCount);
41			} else {
42			$result = new CheckResult(
43			CheckResult::STATUS_SUCCESS,
44			$cookieCount . ' cookies were stored (limit was ' . $this->maxCookies . ').',
45			$cookieCount);
46			}
47
48			$cookies = $response->getCookies();
49
50			$result->addAttribute(new Attribute('cookies', json_encode($cookies), true));
51
52			return $result;
53			} else {
54			$result = new CheckResult(
55			CheckResult::STATUS_SKIPPED,
56			'Skipped: Request timed out. Cannot read cookies.',
57			0);
58
59			return $result;
60			}
61			}
62			}
63			}
64

phmLabs / Smoke

Issues (77)

Security Analysis not enabled

src/Rules/Cookies/CountRule.php (1 issue)

Labels

Severity

Introduced By

Upgrade to new PHP Analysis Engine

Duplication Side-by-Side

Filter issues like