Issues (1507)

Security Analysis    not enabled

This project does not seem to handle request data directly as such no vulnerable execution paths were found.

  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/ExampleWithMySQL.php (6 issues)

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

1
<?php
2
/*
3
Database credentials: add to phpd.conf:
4
Pool:\PHPDaemon\Clients\MySQL\Pool{
5
    enable 1;
6
    server 'tcp://user:[email protected]/dbname';
7
    privileged;
8
}
9
*/
10
11
namespace PHPDaemon\Examples;
12
13
use PHPDaemon\HTTPRequest\Generic;
14
15
/**
16
 * @package    Examples
17
 * @subpackage MySQL
18
 *
19
 * @author     Vasily Zorin <[email protected]>
20
 */
21
class ExampleWithMySQL extends \PHPDaemon\Core\AppInstance
22
{
23
    public $sql;
24
25
    /**
26
     * Called when the worker is ready to go.
27
     * @return void
28
     */
29
30
    public function onReady()
31
    {
32
        $this->sql = \PHPDaemon\Clients\MySQL\Pool::getInstance();
33
    }
34
35
    /**
36
     * Creates Request.
37
     * @param object Request.
38
     * @param object Upstream application instance.
39
     * @return ExampleWithMySQLRequest Request.
40
     */
41
    public function beginRequest($req, $upstream)
42
    {
43
        return new ExampleWithMySQLRequest($this, $upstream, $req);
44
    }
45
}
46
47
class ExampleWithMySQLRequest extends Generic
48
{
49
50
protected $job;
51
52
/**
53
 * Constructor.
54
 * @return void
55
 */
56
public function init()
57
{
58
    $job = $this->job = new \PHPDaemon\Core\ComplexJob(function ($job) { // called when job is done
59
60
        $job->keep();
61
        $this->wakeup(); // wake up the request immediately
62
63
    });
64
65
    $job('select', function ($name, $job) { // registering job named 'select'
66
67
        $this->appInstance->sql->getConnection(function ($sql) use ($name, $job) {
0 ignored issues
show
The property sql 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...
68
            if (!$sql->isConnected()) {
69
                $job->setResult($name, null);
70
                return null;
71
            }
72
            $sql->query('SELECT 123, "string"', function ($sql, $success) use ($job, $name) {
0 ignored issues
show
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...
73
74
                $job('showdbs', function ($name, $job) use ($sql) { // registering job named 'showdbs'
75
                    $sql->query('SHOW DATABASES', function ($sql, $t) use ($job, $name) {
0 ignored issues
show
The parameter $t 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...
76
                        $job->setResult($name, $sql->resultRows);
77
                    });
78
                });
79
                $job->setResult($name, $sql->resultRows);
80
            });
81
            return null;
82
        });
83
    });
84
85
    $job(); // let the fun begin
86
87
    $this->sleep(5, true); // setting timeout
88
}
89
90
/**
91
 * Called when request iterated.
92
 * @return integer Status.
0 ignored issues
show
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...
93
 */
94
public function run()
95
{
96
try {
97
    $this->header('Content-Type: text/html');
98
} catch (\Exception $e) {
0 ignored issues
show
Coding Style Comprehensibility introduced by
Consider adding a comment why this CATCH block is empty.
Loading history...
99
}
100
101
?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
102
    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
103
<html xmlns="http://www.w3.org/1999/xhtml">
104
<head>
105
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8"/>
106
    <title>Example with MySQL</title>
107
</head>
108
<body>
109
<?php
110
if ($r = $this->job->getResult('select')) {
111
    echo '<h1>It works! Be happy! ;-)</h1>Result of SELECT 123, "string": <pre>';
112
    var_dump($r);
0 ignored issues
show
Security Debugging Code introduced by
var_dump($r); looks like debug code. Are you sure you do not want to remove it? This might expose sensitive data.
Loading history...
113
    echo '</pre>';
114
115
    echo '<br />Result of SHOW DATABASES: <pre>';
116
    var_dump($this->job->getResult('showdbs'));
117
    echo '</pre>';
118
} else {
119
    echo '<h1>Something went wrong! We have no result.</h1>';
120
}
121
echo '<br />Request (http) took: ' . round(microtime(true) - $this->attrs->server['REQUEST_TIME_FLOAT'], 6);
122
?>
123
</body>
124
</html>
125
<?php
126
127
}
128
}
129