Issues (2)

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/Rules/ContextProhibited.php (2 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
namespace Swatty007\LaravelContextProhibitedRule\Rules;
4
5
use Illuminate\Contracts\Validation\Rule;
6
use Illuminate\Support\Str;
7
8
class ContextProhibited implements Rule
9
{
10
    /**
11
     * Dataset of context specific words we want to validate against
12
     *
13
     * @var array|false|string[]
14
     */
15
    protected $prohibitedWords = [];
16
17
    /**
18
     * Create a new rule instance.
19
     *
20
     */
21 14
    public function __construct()
22
    {
23
        // Assemble our set of context specific words
24 14
        if (!config('context-prohibited-rule.allow_application_name')) {
25 14
            array_push($this->prohibitedWords, Str::lower(Str::camel(config('app.name'))));
26
        }
27
28 14
        if (!config('context-prohibited-rule.allow_hostname')) {
29 14
            $hostname = Str::beforeLast(parse_url(config('app.url'), PHP_URL_HOST), '.');
0 ignored issues
show
It seems like parse_url(config('app.url'), PHP_URL_HOST) targeting parse_url() can also be of type false; however, Illuminate\Support\Str::beforeLast() does only seem to accept string, did you maybe forget to handle an error condition?
Loading history...
30 14
            array_push($this->prohibitedWords, Str::lower($hostname));
31
        }
32
33 14
        $this->prohibitedWords = array_merge($this->prohibitedWords, config('context-prohibited-rule.prohibited_words'));
34
35
        // Remove and word, which is less then 3 chars from our list again
36
        // Otherwise this rule will be quite impossible to match...
37 14
        foreach ($this->prohibitedWords as $key => $word) {
38 14
            if (strlen($word) < config('context-prohibited-rule.min_length')) {
39 2
                unset($this->prohibitedWords[$key]);
40
            }
41
        }
42 14
    }
43
44
    /**
45
     * Determine if the validation rule passes.
46
     *
47
     * @param string $attribute
48
     * @param mixed $value
49
     * @return bool
50
     */
51 14
    public function passes($attribute, $value): bool
52
    {
53 14
        $value = strtolower($value);
54
55 14
        foreach ($this->prohibitedWords as $word) {
0 ignored issues
show
The expression $this->prohibitedWords of type array|false is not guaranteed to be traversable. How about adding an additional type check?

There are different options of fixing this problem.

  1. If you want to be on the safe side, you can add an additional type-check:

    $collection = json_decode($data, true);
    if ( ! is_array($collection)) {
        throw new \RuntimeException('$collection must be an array.');
    }
    
    foreach ($collection as $item) { /** ... */ }
    
  2. If you are sure that the expression is traversable, you might want to add a doc comment cast to improve IDE auto-completion and static analysis:

    /** @var array $collection */
    $collection = json_decode($data, true);
    
    foreach ($collection as $item) { /** .. */ }
    
  3. Mark the issue as a false-positive: Just hover the remove button, in the top-right corner of this issue for more options.

Loading history...
56 14
            if (stripos($value, $word) !== false) {
57 12
                return false;
58
            }
59
        }
60
61 10
        return true;
62
    }
63
64 12
    public function message()
65
    {
66 12
        return __(
67 12
            'validation.context_prohibited',
68
            [
69 12
                'prohibited' => implode(',', $this->prohibitedWords)
70
            ]
71
        );
72
    }
73
}
74