Issues (62)

Security Analysis    not enabled

This project does not seem to handle request data directly as such no vulnerable execution paths were found.

  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.
  Regex Injection
Regex Injection enables an attacker to execute arbitrary code in your PHP process.
  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.
  Response Splitting
Response Splitting can be used to send arbitrary responses.
  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.
  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.
  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.
  Code Injection
Code Injection enables an attacker to execute arbitrary code on the server.
  Variable Injection
Variable Injection enables an attacker to overwrite program variables with custom data, and can lead to further vulnerabilities.
  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.
  Other Vulnerability
This category comprises other attack vectors such as manipulating the PHP runtime, loading custom extensions, freezing the runtime, or similar.
  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.
  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.
  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.
  Header Injection
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.

class/Helper.php (1 issue)

Severity
1
<?php
2
3
namespace XoopsModules\Xhttperror;
4
5
/*
6
 * You may not change or alter any portion of this comment or credits
7
 * of supporting developers from this source code or any supporting source code
8
 * which is considered copyrighted (c) material of the original comment or credit authors.
9
 *
10
 * This program is distributed in the hope that it will be useful,
11
 * but WITHOUT ANY WARRANTY; without even the implied warranty of
12
 * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
13
 */
14
15
/**
16
 * @copyright    XOOPS Project (https://xoops.org)
17
 * @license      GNU GPL 2 or later (https://www.gnu.org/licenses/gpl-2.0.html)
18
 * @author       XOOPS Development Team
19
 */
20
21
/**
22
 * Class Helper
23
 */
24
class Helper extends \Xmf\Module\Helper
25
{
26
    public $debug;
27
28
    /**
29
     * @param bool $debug
30
     */
31
    public function __construct($debug = false)
32
    {
33
        $this->debug   = $debug;
34
        $moduleDirName = \basename(\dirname(__DIR__));
35
        parent::__construct($moduleDirName);
36
    }
37
38
    /**
39
     * @param bool $debug
40
     *
41
     * @return \XoopsModules\Xhttperror\Helper
42
     */
43
    public static function getInstance($debug = false)
44
    {
45
        static $instance;
46
        if (null === $instance) {
47
            $instance = new static($debug);
48
        }
49
50
        return $instance;
51
    }
52
53
    /**
54
     * @return string
55
     */
56
    public function getDirname()
57
    {
58
        return $this->dirname;
59
    }
60
61
    /**
62
     * Get an Object Handler
63
     *
64
     * @param string $name name of handler to load
65
     *
66
     * @return bool|\XoopsObjectHandler|\XoopsPersistableObjectHandler
67
     */
68
    public function getHandler($name)
69
    {
70
        $ret = false;
0 ignored issues
show
The assignment to $ret is dead and can be removed.
Loading history...
71
72
        $class = __NAMESPACE__ . '\\' . \ucfirst($name) . 'Handler';
73
        if (!\class_exists($class)) {
74
            throw new \RuntimeException("Class '$class' not found");
75
        }
76
        /** @var \XoopsMySQLDatabase $db */
77
        $db     = \XoopsDatabaseFactory::getDatabaseConnection();
78
        $helper = self::getInstance();
79
        $ret    = new $class($db, $helper);
80
        $this->addLog("Getting handler '{$name}'");
81
        return $ret;
82
    }
83
}
84