Issues (310)

Security Analysis    no vulnerabilities found

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.

install/tester.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
0 ignored issues
show
Coding Style Compatibility introduced by
For compatibility and reusability of your code, PSR1 recommends that a file should introduce either new symbols (like classes, functions, etc.) or have side-effects (like outputting something, or including other files), but not both at the same time. The first symbol is defined on line 14 and the first side effect is on line 6.

The PSR-1: Basic Coding Standard recommends that a file should either introduce new symbols, that is classes, functions, constants or similar, or have side effects. Side effects are anything that executes logic, like for example printing output, changing ini settings or writing to a file.

The idea behind this recommendation is that merely auto-loading a class should not change the state of an application. It also promotes a cleaner style of programming and makes your code less prone to errors, because the logic is not spread out all over the place.

To learn more about the PSR-1, please see the PHP-FIG site on the PSR-1.

Loading history...
2
3
// Load Query Manager
4
// ###################
5
6
include_once __DIR__.'/../core/process/queries/QueryManager.php';
7
8
//#######################################################################
9
// Test function
10
// This happend once to be sure database is still full of datas
11
// to avoid errors on website
12
//#######################################################################
13
14
function php_test()
15
{
16
    $lock_msg = '';
17
18
    if (version_compare(phpversion(), '5.4', '<')) {
19
        $lock_msg .= "Error: Sorry, your PHP version isn't supported. Please upgrade to PHP >= 5.4<br>";
20
    }
21
22
    return $lock_msg;
23
}
24
25
function db_test()
26
{
27
    $manager = \Worldopole\QueryManager::current();
28
29
    $lock_msg = '';
30
31
    // Pokemon Test
32
    $result = $manager->testTotalPokemon();
33
34
    if (1 === $result) {
35
        $lock_msg .= 'Error: No Pokémon database found<br>';
36
    } elseif (2 === $result) {
37
        $lock_msg .= 'Error: No Pokémon found is your database<br>';
38
    }
39
40
    // Gym Test
41
    $result = $manager->testTotalGyms();
42
43
    if (1 === $result) {
44
        $lock_msg .= 'Error: No Gym database found<br>';
45
    } elseif (2 === $result) {
46
        $lock_msg .= 'Error: No Gym found is your database<br>';
47
    }
48
49
    // Pokéstop Test
50
    $result = $manager->testTotalPokestops();
51
52
    if (1 === $result) {
53
        $lock_msg .= 'Error: No Pokestop database found<br>';
54
    } elseif (2 === $result) {
55
        $lock_msg .= 'Error: No Pokestop found in your database<br>';
56
    }
57
58
    return $lock_msg;
59
}
60
61
function permission_test()
62
{
63
    $lock_msg = '';
64
65
    // Can we write on install and core/json folder?
66
    if (!is_writable(SYS_PATH.'/install/') || !is_writeable(SYS_PATH.'/core/json/')) {
67
        $lock_msg .= 'Error: Install can not be completed!<br>
68
                              Please fix install/ and core/json/ directory rights.<br>
69
                              Apache needs write access to both directories.<br>';
70
        // This is really bad exit immediately
71
        echo $lock_msg;
72
        exit();
73
    }
74
75
    return $lock_msg;
76
}
77
78
function run_tests()
79
{
80
    // Execute tests
81
    $errors = '';
82
    $errors .= php_test();
83
    $errors .= db_test();
84
    $errors .= permission_test();
85
86
    // Write lockfile on error
87
    $lock_file = SYS_PATH.'/install/website.lock';
88
    if (file_exists($lock_file)) {
89
        // delete old lockfile
90
        unlink($lock_file);
91
    }
92
93
    // create new file if there is an error
94
    if ('' != $errors) {
95
        file_put_contents($lock_file, $errors);
96
    }
97
}
98