Issues in Transactions.php (master) - Issues in master - webdcg/redis - Measure and Improve Code Quality continuously with Scrutinizer

Issues (37)

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/Traits/Transactions.php (1 issue)

Labels

Bug 1

Severity

Major 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 Webdcg\Redis\Traits;

trait Transactions
{
    /**
     * Marks the start of a transaction block. Subsequent commands will be
     * queued for atomic execution using EXEC.
     * See: https://redis.io/commands/multi.
     *
     * @return transaction context
     */
    public function multi()
    {
        return $this->redis->multi();
class MyClass { }

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


    /**
     * Executes all previously queued commands in a transaction and restores
     * the connection state to normal.
     *
     * See: https://redis.io/commands/exec.
     *
     * @return array    each element being the reply to each of the commands
     *                  in the atomic transaction.
     */
    public function exec($multi): array
    {
        return $multi->exec();
    }


    /**
     * Flushes all previously queued commands in a transaction and restores the
     * connection state to normal.
     *
     * See: https://redis.io/commands/discard.
     *
     * @param   $multi
     *
     * @return bool
     */
    public function discard(\Redis $multi): bool
    {
        return $multi->discard();
    }


    /**
     * Marks the given keys to be watched for conditional execution of a
     * transaction.
     *
     * See: https://redis.io/commands/watch.
     *
     * @param  splat $keys
     *
     * @return bool
     */
    public function watch(...$keys): bool
    {
        return $this->redis->watch(...$keys);
    }


    /**
     * Flushes all the previously watched keys for a transaction.
     * If you call EXEC or DISCARD, there's no need to manually call UNWATCH.
     *
     * See: https://redis.io/commands/unwatch.
     *
     * @param  splat $keys
     *
     * @return bool
     */
    public function unwatch(...$keys): bool
    {
        return $this->redis->unwatch(...$keys);
    }
}


1			<?php
2
3			namespace Webdcg\Redis\Traits;
4
5			trait Transactions
6			{
7			/**
8			* Marks the start of a transaction block. Subsequent commands will be
9			* queued for atomic execution using EXEC.
10			* See: https://redis.io/commands/multi.
11			*
12			* @return transaction context
13			*/
14			public function multi()
15			{
16			return $this->redis->multi();
			0 ignored issues – show Bug introduced 2020-01-28 18:23 UTC by Report Bug Copy Issue Report Show Similar Issues like this 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...
17			}
18
19
20			/**
21			* Executes all previously queued commands in a transaction and restores
22			* the connection state to normal.
23			*
24			* See: https://redis.io/commands/exec.
25			*
26			* @return array each element being the reply to each of the commands
27			* in the atomic transaction.
28			*/
29			public function exec($multi): array
30			{
31			return $multi->exec();
32			}
33
34
35			/**
36			* Flushes all previously queued commands in a transaction and restores the
37			* connection state to normal.
38			*
39			* See: https://redis.io/commands/discard.
40			*
41			* @param $multi
42			*
43			* @return bool
44			*/
45			public function discard(\Redis $multi): bool
46			{
47			return $multi->discard();
48			}
49
50
51			/**
52			* Marks the given keys to be watched for conditional execution of a
53			* transaction.
54			*
55			* See: https://redis.io/commands/watch.
56			*
57			* @param splat $keys
58			*
59			* @return bool
60			*/
61			public function watch(...$keys): bool
62			{
63			return $this->redis->watch(...$keys);
64			}
65
66
67			/**
68			* Flushes all the previously watched keys for a transaction.
69			* If you call EXEC or DISCARD, there's no need to manually call UNWATCH.
70			*
71			* See: https://redis.io/commands/unwatch.
72			*
73			* @param splat $keys
74			*
75			* @return bool
76			*/
77			public function unwatch(...$keys): bool
78			{
79			return $this->redis->unwatch(...$keys);
80			}
81			}
82

webdcg / redis

Issues (37)

Security Analysis no request data

src/Traits/Transactions.php (1 issue)

Labels

Severity

Introduced By

Upgrade to new PHP Analysis Engine

Duplication Side-by-Side

Filter issues like