Issues (37)

Security Analysis    no request data  

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.

src/Traits/Introspection.php (1 issue)

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

1
<?php
2
3
/**
4
 *  #     #               ######   #####   #####
5
 *  #  #  # ###### #####  #     # #     # #     #
6
 *  #  #  # #      #    # #     # #       #
7
 *  #  #  # #####  #####  #     # #       #  ####
8
 *  #  #  # #      #    # #     # #       #     #
9
 *  #  #  # #      #    # #     # #     # #     #
10
 *   ## ##  ###### #####  ######   #####   #####
11
 */
12
13
namespace Webdcg\Redis\Traits;
14
15
trait Introspection
16
{
17
    /**
18
     * A method to determine if a phpredis object thinks it's connected to a
19
     * server.
20
     *
21
     * @return boolean      Returns TRUE if phpredis thinks it's connected
22
     *                      and FALSE if not.
23
     */
24
    public function isConnected(): bool
25
    {
26
        return $this->redis->isConnected();
0 ignored issues
show
The property redis does not exist. Did you maybe forget to declare it?

In PHP it is possible to write to properties without declaring them. For example, the following is perfectly valid PHP code:

class MyClass { }

$x = new MyClass();
$x->foo = true;

Generally, it is a good practice to explictly declare properties to avoid accidental typos and provide IDE auto-completion:

class MyClass {
    public $foo;
}

$x = new MyClass();
$x->foo = true;
Loading history...
27
    }
28
29
30
    /**
31
     * Retrieve our host or unix socket that we're connected to
32
     *
33
     * @return mixed|string|bool    The host or unix socket we're connected to
34
     *                              or FALSE if we're not connected.
35
     */
36
    public function getHost()
37
    {
38
        return $this->redis->getHost();
39
    }
40
41
42
    /**
43
     * Get the port we're connected to
44
     *
45
     * @return mixed|int|bool       Returns the port we're connected to or
46
     *                              FALSE if we're not connected.
47
     */
48
    public function getPort()
49
    {
50
        return $this->redis->getPort();
51
    }
52
53
54
    /**
55
     * Get the database number phpredis is pointed to
56
     *
57
     * @return mixed|int|bool          Returns the database number (LONG)
58
     *                                 phpredis thinks it's pointing to or
59
     *                                 FALSE if we're not connected.
60
     */
61
    public function getDbNum()
62
    {
63
        return $this->redis->getDbNum();
64
    }
65
66
67
    /**
68
     * Get the (write) timeout in use for phpredis
69
     *
70
     * @return mixed|float|bool     The timeout (DOUBLE) specified in our
71
     *                              connect call or FALSE if we're not
72
     *                              connected.
73
     */
74
    public function getTimeout()
75
    {
76
        return $this->redis->getTimeout();
77
    }
78
79
80
    /**
81
     * Get the read timeout specified to phpredis or FALSE if we're not connected
82
     *
83
     * @return mixed|int|bool       Returns the read timeout (which can be set
84
     *                              using setOption and Redis::OPT_READ_TIMEOUT)
85
     *                              or FALSE if we're not connected.
86
     */
87
    public function getReadTimeout()
88
    {
89
        return $this->redis->getReadTimeout();
90
    }
91
92
93
    /**
94
     * Gets the persistent ID that phpredis is using.
95
     *
96
     * @return mixed|int|null|bool  Returns the persistent id phpredis is using
97
     *                              (which will only be set if connected with
98
     *                              pconnect), NULL if we're not using a
99
     *                              persistent ID, and FALSE if we're not
100
     *                              connected.
101
     */
102
    public function getPersistentID()
103
    {
104
        return $this->redis->getPersistentID();
105
    }
106
107
108
    /**
109
     * Get the password used to authenticate the phpredis connection.
110
     *
111
     * @return mixed|string|null|bool   Returns the password used to authenticate
112
     *                                  a phpredis session or NULL if none was
113
     *                                  used, and FALSE if we're not connected.
114
     */
115
    public function getAuth()
116
    {
117
        return $this->redis->getAuth();
118
    }
119
}
120