Issues (7)

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.

resources/config.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
 * Vault component configuration file. Attention, configs might include runtime code which
4
 * depended on environment values only.
5
 *
6
 * @see SecurityConfig
7
 */
8
9
return [
10
    /*
11
     * Every controller access will be checked under following permissions namespace. For example
12
     * access to TestController mounted under name "test" will be checked as "vault.test".
13
     */
14
    'guard'       => [
15
        'namespace' => 'vault'
16
    ],
17
18
    /*
19
     * List of controller classes associated with their alias to be available for vault. No other
20
     * controllers can be called.
21
     *
22
     * Vault checks access to controllers using high level permission "vault", make sure this
23
     * permissions is available for a needed user role.
24
     *
25
     * @see VaultCore
26
     */
27
    'controllers' => [
28
        'welcome' => \Spiral\Vault\Controllers\WelcomeController::class,
29
30
        /*{{controllers}}*/
31
    ],
32
33
    /*
34
     * Configuration for VaultRoute.
35
     */
36
    'route'       => [
37
        /*
38
        * Set of middleware classes to be applied for VaultRoute. Make sure to include AuthMiddleware
39
        * here!
40
        */
41
        'middlewares' => [
42
            /*{{middlewares}}*/
43
        ],
44
45
        /*
46
         * Simple replace vault with desired keyword (for example "admin") to specify vault url
47
         * namespace.
48
         */
49
        'pattern'     => 'vault[/<controller>[/<action>[/<id>[/<operation>[/<childID>]]]]]',
50
51
        /*
52
         * Default route values.
53
         */
54
        'defaults'    => [
55
            'controller' => 'welcome'
56
        ],
57
58
        /*
59
         * Set this value to true in cases when route based on sub domain patten, for example:
60
         * vault.website.com[/<controller>[/<action>[/<id>[/<operation>[/<childID>]]]]]
61
         */
62
        'matchHost'   => false
63
    ],
64
65
    /*
66
     * Structure of vault navigation including sections, section icons, links, link badges
67
     * and permissions needed to view link. Link labels will be translated using i18n domain
68
     * "vault".
69
     *
70
     * Note that all links are automatically checked with Guard based on associated controller name.
71
     */
72
    'navigation'  => [
73
        /*
74
         * Project overview and activity.
75
         */
76
        'vault' => [
77
            'title' => 'Vault',
78
            'icon'  => 'tab',
79
            'items' => [
80
                'welcome' => ['title' => 'Welcome to Vault'],
81
82
                /*{{navigation.activity}}*/
0 ignored issues
show
Unused Code Comprehensibility introduced by
58% of this comment could be valid code. Did you maybe forget this after debugging?

Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it.

The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production.

This check looks for comments that seem to be mostly valid code and reports them.

Loading history...
83
            ]
84
        ],
85
86
        /*{{navigation}}*/
87
    ],
88
];