Issues (4)

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/Cache/NullCache.php (1 issue)

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
namespace Chadicus\Marvel\Api\Cache;
4
5
use Psr\SimpleCache\CacheInterface;
6
7
/**
8
 * A PSR-16 implementation which does not save or store any data.
9
 */
10
final class NullCache implements CacheInterface
11
{
12
    /**
13
     * Fetches a value from the cache.
14
     *
15
     * @param string $key     The unique key of this item in the cache.
16
     * @param mixed  $default Default value to return if the key does not exist.
17
     *
18
     * @return mixed The value of the item from the cache, or $default in case of cache miss.
19
     */
20
    public function get($key, $default = null)//@codingStandardsIgnoreLine  Interface does not define type-hints
21
    {
22
        return $default;
23
    }
24
25
    /**
26
     * Persists data in the cache, uniquely referenced by a key with an optional expiration TTL time.
27
     *
28
     * @param string                    $key   The key of the item to store.
29
     * @param mixed                     $value The value of the item to store, must be serializable.
30
     * @param null|integer|DateInterval $ttl   Optional. The TTL value of this item. If no value is sent and
31
     *                                         the driver supports TTL then the library may set a default value
32
     *                                         for it or let the driver take care of that.
33
     *
34
     * @return boolean True on success and false on failure.
35
     */
36
    public function set($key, $value, $ttl = null)//@codingStandardsIgnoreLine  Interface does not define type-hints
37
    {
38
        return true;
39
    }
40
41
    /**
42
     * Delete an item from the cache by its unique key.
43
     *
44
     * @param string $key The unique cache key of the item to delete.
45
     *
46
     * @return boolean True if the item was successfully removed. False if there was an error.
47
     */
48
    public function delete($key)//@codingStandardsIgnoreLine  Interface does not define type-hints
49
    {
50
        return true;
51
    }
52
53
    /**
54
     * Wipes clean the entire cache's keys.
55
     *
56
     * @return boolean True on success and false on failure.
57
     */
58
    public function clear()
59
    {
60
        return true;
61
    }
62
63
    /**
64
     * Obtains multiple cache items by their unique keys.
65
     *
66
     * @param iterable $keys    A list of keys that can obtained in a single operation.
67
     * @param mixed    $default Default value to return for keys that do not exist.
68
     *
69
     * @return array A list of key => value pairs. Keys that do not exist or are stale will have $default as value.
70
     */
71
    public function getMultiple($keys, $default = null)//@codingStandardsIgnoreLine  Interface does not define type-hints
72
    {
73
        $items = [];
74
        foreach ($keys as $key) {
75
            $items[$key] = $default;
76
        }
77
78
        return $items;
0 ignored issues
show
Bug Best Practice introduced by
The return type of return $items; (array) is incompatible with the return type declared by the interface Psr\SimpleCache\CacheInterface::getMultiple of type Psr\SimpleCache\iterable.

If you return a value from a function or method, it should be a sub-type of the type that is given by the parent type f.e. an interface, or abstract method. This is more formally defined by the Lizkov substitution principle, and guarantees that classes that depend on the parent type can use any instance of a child type interchangably. This principle also belongs to the SOLID principles for object oriented design.

Let’s take a look at an example:

class Author {
    private $name;

    public function __construct($name) {
        $this->name = $name;
    }

    public function getName() {
        return $this->name;
    }
}

abstract class Post {
    public function getAuthor() {
        return 'Johannes';
    }
}

class BlogPost extends Post {
    public function getAuthor() {
        return new Author('Johannes');
    }
}

class ForumPost extends Post { /* ... */ }

function my_function(Post $post) {
    echo strtoupper($post->getAuthor());
}

Our function my_function expects a Post object, and outputs the author of the post. The base class Post returns a simple string and outputting a simple string will work just fine. However, the child class BlogPost which is a sub-type of Post instead decided to return an object, and is therefore violating the SOLID principles. If a BlogPost were passed to my_function, PHP would not complain, but ultimately fail when executing the strtoupper call in its body.

Loading history...
79
    }
80
81
    /**
82
     * Persists a set of key => value pairs in the cache, with an optional TTL.
83
     *
84
     * @param iterable                  $values A list of key => value pairs for a multiple-set operation.
85
     * @param null|integer|DateInterval $ttl    Optional. The TTL value of this item. If no value is sent and
86
     *                                          the driver supports TTL then the library may set a default value
87
     *                                          for it or let the driver take care of that.
88
     *
89
     * @return boolean True on success and false on failure.
90
     */
91
    public function setMultiple($values, $ttl = null)//@codingStandardsIgnoreLine  Interface does not define type-hints
92
    {
93
        return true;
94
    }
95
96
    /**
97
     * Deletes multiple cache items in a single operation.
98
     *
99
     * @param iterable $keys A list of string-based keys to be deleted.
100
     *
101
     * @return boolean True if the items were successfully removed. False if there was an error.
102
     */
103
    public function deleteMultiple($keys)//@codingStandardsIgnoreLine  Interface does not define type-hints
104
    {
105
        return true;
106
    }
107
108
    /**
109
     * Determines whether an item is present in the cache.
110
     *
111
     * NOTE: It is recommended that has() is only to be used for cache warming type purposes
112
     * and not to be used within your live applications operations for get/set, as this method
113
     * is subject to a race condition where your has() will return true and immediately after,
114
     * another script can remove it making the state of your app out of date.
115
     *
116
     * @param string $key The cache item key.
117
     *
118
     * @return boolean
119
     */
120
    public function has($key)//@codingStandardsIgnoreLine  Interface does not define type-hints
121
    {
122
        return false;
123
    }
124
}
125