Issues in ExampleWithPostgreSQL.php (master) - Issues in master - kakserpom/phpdaemon - Measure and Improve Code Quality continuously with Scrutinizer

Issues (1507)

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.

PHPDaemon/Examples/ExampleWithPostgreSQL.php (6 issues)

Labels

Severity

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 PHPDaemon\Examples;

use PHPDaemon\HTTPRequest\Generic;

/**
 * @package    Examples
 * @subpackage PostgreSQL
 *
 * @author     Vasily Zorin <[email protected]>
 */
class ExampleWithPostgreSQL extends \PHPDaemon\Core\AppInstance
{

    public $pgsql;

    /**
     * Constructor.
     * @return void
     */
    public function init()
    {
        $this->pgsql = \PHPDaemon\Clients\PostgreSQL\Pool::getInstance();
    }

    /**
     * Creates Request.
     * @param object Request.
     * @param object Upstream application instance.
     * @return ExampleWithPostgreSQLRequest Request.
     */
    public function beginRequest($req, $upstream)
    {
        return new ExampleWithPostgreSQLRequest($this, $upstream, $req);
    }
}

class ExampleWithPostgreSQLRequest extends Generic
{

    public $stime;
    public $queryResult;
    public $sql;
    public $runstate = 0;

    /**
     * Constructor.
     * @return void
     */
    public function init()
    {
        $this->appInstance->pgsql->getConnection(function ($sql) {

            if (!$sql->connected) { // failed to connect
                $this->wakeup(); // wake up the request immediately
                $sql->release();
                return;
            }
            $sql->query('SELECT 123 as integer, NULL as nul, \'test\' as string', function ($sql, $success) {

                $this->queryResult = $sql->resultRows; // save the result
                $this->wakeup(); // wake up the request immediately
                $sql->release();
            });
        });
        $this->sleep(5);
    }

    /**
     * Called when request iterated.
     * @return integer Status.

     */
    public function run()

    {
        try {
            $this->header('Content-Type: text/html');
        } catch (\Exception $e) {

        }
        ?>
        <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
            "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
        <html xmlns="http://www.w3.org/1999/xhtml">
        <head>
            <meta http-equiv="Content-Type" content="text/html; charset=utf-8"/>
            <title>Example with PostgreSQL</title>
        </head>
        <body>
        <?php

        if ($this->queryResult) {
            echo '<h1>It works! Be happy! ;-)</h1>Result of `SELECT 123 as integer, NULL as nul, \'test\' as string`: <pre>';
            var_dump($this->queryResult);

            echo '</pre>';
        } else {
            echo '<h1>Something went wrong! We have no result.</h1>';
        }

        echo '<br />Request (http) took: ' . round(microtime(true) - $_SERVER['REQUEST_TIME_FLOAT'], 6);

        ?>
        </body>
        </html>
        <?php

    }
}


1		<?php
2		namespace PHPDaemon\Examples;
3
4		use PHPDaemon\HTTPRequest\Generic;
5
6		/**
7		* @package Examples
8		* @subpackage PostgreSQL
9		*
10		* @author Vasily Zorin <[email protected]>
11		*/
12		class ExampleWithPostgreSQL extends \PHPDaemon\Core\AppInstance
13		{
14
15		public $pgsql;
16
17		/**
18		* Constructor.
19		* @return void
20		*/
21		public function init()
22		{
23		$this->pgsql = \PHPDaemon\Clients\PostgreSQL\Pool::getInstance();
24		}
25
26		/**
27		* Creates Request.
28		* @param object Request.
29		* @param object Upstream application instance.
30		* @return ExampleWithPostgreSQLRequest Request.
31		*/
32		public function beginRequest($req, $upstream)
33		{
34		return new ExampleWithPostgreSQLRequest($this, $upstream, $req);
35		}
36		}
37
38		class ExampleWithPostgreSQLRequest extends Generic
39		{
40
41		public $stime;
42		public $queryResult;
43		public $sql;
44		public $runstate = 0;
45
46		/**
47		* Constructor.
48		* @return void
49		*/
50		public function init()
51		{
52		$this->appInstance->pgsql->getConnection(function ($sql) {
		0 ignored issues – show Bug introduced 2015-12-06 14:42 UTC by Report Bug Copy Issue Report Show Similar Issues like this The property `pgsql` does not seem to exist in `PHPDaemon\Core\AppInstance`. An attempt at access to an undefined property has been detected. This may either be a typographical error or the property has been renamed but there are still references to its old name. If you really want to allow access to undefined properties, you can define magic methods to allow access. See the php core documentation on Overloading. Loading history...
53		if (!$sql->connected) { // failed to connect
54		$this->wakeup(); // wake up the request immediately
55		$sql->release();
56		return;
57		}
58		$sql->query('SELECT 123 as integer, NULL as nul, \'test\' as string', function ($sql, $success) {
		0 ignored issues – show Unused Code introduced 2015-12-06 14:42 UTC by Report Bug Copy Issue Report Show Similar Issues like this The parameter `$success` is not used and could be removed. This check looks from parameters that have been defined for a function or method, but which are not used in the method body. Loading history...
59		$this->queryResult = $sql->resultRows; // save the result
60		$this->wakeup(); // wake up the request immediately
61		$sql->release();
62		});
63		});
64		$this->sleep(5);
65		}
66
67		/**
68		* Called when request iterated.
69		* @return integer Status.
		0 ignored issues – show Documentation introduced 2015-12-06 14:42 UTC by Report Bug Copy Issue Report Show Similar Issues like this Should the return type not be `integer\|null`? 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...
70		*/
71	View Code Duplication	public function run()
		0 ignored issues – show Duplication introduced 2018-01-16 22:41 UTC by Report Bug Copy Issue Report Show Similar Issues like this This method seems to be duplicated in your project. Duplicated code is one of the most pungent code smells. If you need to duplicate the same code in three or more different places, we strongly encourage you to look into extracting the code into a single class or operation. You can also find more detailed suggestions in the “Code” section of your repository. Loading history...
72		{
73		try {
74		$this->header('Content-Type: text/html');
75		} catch (\Exception $e) {
		0 ignored issues – show Coding Style Comprehensibility introduced 2015-12-06 14:42 UTC by Report Bug Copy Issue Report Show Similar Issues like this Consider adding a comment why this CATCH block is empty. Loading history...
76		}
77		?>
78		<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
79		"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
80		<html xmlns="http://www.w3.org/1999/xhtml">
81		<head>
82		<meta http-equiv="Content-Type" content="text/html; charset=utf-8"/>
83		<title>Example with PostgreSQL</title>
84		</head>
85		<body>
86		<?php
87
88		if ($this->queryResult) {
89		echo '<h1>It works! Be happy! ;-)</h1>Result of `SELECT 123 as integer, NULL as nul, \'test\' as string`: <pre>';
90		var_dump($this->queryResult);
		0 ignored issues – show Security Debugging Code introduced 2015-12-06 14:42 UTC by Report Bug Copy Issue Report Show Similar Issues like this `var_dump($this->queryResult);` looks like debug code. Are you sure you do not want to remove it? This might expose sensitive data. Loading history...
91		echo '</pre>';
92		} else {
93		echo '<h1>Something went wrong! We have no result.</h1>';
94		}
95
96		echo '<br />Request (http) took: ' . round(microtime(true) - $_SERVER['REQUEST_TIME_FLOAT'], 6);
97
98		?>
99		</body>
100		</html>
101		<?php
102
103		}
104		}
105

kakserpom / phpdaemon

Issues (1507)

Security Analysis not enabled

PHPDaemon/Examples/ExampleWithPostgreSQL.php (6 issues)

Labels

Severity

Introduced By

Upgrade to new PHP Analysis Engine

Duplication Side-by-Side

Filter issues like