Issues in getMysql.php (master) - Issues in master - XoopsModules25x/adminer - Measure and Improve Code Quality continuously with Scrutinizer

Issues (895)

Security Analysis not enabled

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.

admin/getMysql.php (7 issues)

Labels

Severity

mambax7 7

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

<?php
/**
 * Adminer Module based on Ghost Module
 *
 * You may not change or alter any portion of this comment or credits
 * of supporting developers from this source code or any supporting source code
 * which is considered copyrighted (c) material of the original comment or credit authors.
 * This program is distributed in the hope that it will be useful,
 * but WITHOUT ANY WARRANTY; without even the implied warranty of
 * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
 *
 * @copyright            The XOOPS Project http://sourceforge.net/projects/xoops/
 * @license              http://www.fsf.org/copyleft/gpl.html GNU public license
 * @package              Adminer Module
 * @since                2.3.0
 * @author               Kris <http://www.xoofoo.org>
 * @version              $Id $
 **/
// connect xoops database 
include_once __DIR__ . '/admin_header.php';

if (!is_object($xoopsUser) || !is_object($xoopsModule) || !$xoopsUser->isAdmin($xoopsModule->mid())) {

    exit(_NOPERM);
}

/**
 * @return AdminerCustomization
 */
function adminer_object()
/**
 * @ignore
 */
function getUser() {

}

function getUser($id, $realm) {

}
{
    // required to run any plugin
    include_once dirname(__DIR__) . '/include/plugins/plugin.php';
    //    include_once dirname(__DIR__) . "/include/plugins/plugin.php";

    include_once dirname(__DIR__) . '/include/plugins/frames.php';

    // autoloader
    //    foreach (glob("plugins/*.php") as $filename) {

    //        include_once "./$filename";
    //    }

    $plugins = array(
        // specify enabled plugins here
        //        new AdminerDumpXml,
        //        new AdminerTinymce,
        //        new AdminerFileUpload("data/"),

        //        new AdminerSlugify,
        //        new AdminerTranslation,
        //        new AdminerForeignSystem,
        new AdminerFrames
    );

    //    It is possible to combine customization and plugins:
    /**
     * Class AdminerCustomization
     */
    class AdminerCustomization extends AdminerPlugin

    {
    }

    return new AdminerCustomization($plugins);

    //    return new AdminerPlugin($plugins);

}

// include original Adminer or Adminer Editor
include_once dirname(__DIR__) . '/include/adminer.php';


1		<?php
2		/**
3		* Adminer Module based on Ghost Module
4		*
5		* You may not change or alter any portion of this comment or credits
6		* of supporting developers from this source code or any supporting source code
7		* which is considered copyrighted (c) material of the original comment or credit authors.
8		* This program is distributed in the hope that it will be useful,
9		* but WITHOUT ANY WARRANTY; without even the implied warranty of
10		* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
11		*
12		* @copyright The XOOPS Project http://sourceforge.net/projects/xoops/
13		* @license http://www.fsf.org/copyleft/gpl.html GNU public license
14		* @package Adminer Module
15		* @since 2.3.0
16		* @author Kris <http://www.xoofoo.org>
17		* @version $Id $
18		**/
19		// connect xoops database
20		include_once __DIR__ . '/admin_header.php';
21
22	View Code Duplication	if (!is_object($xoopsUser) \|\| !is_object($xoopsModule) \|\| !$xoopsUser->isAdmin($xoopsModule->mid())) {
		0 ignored issues – show Duplication introduced 2016-07-19 20:27 UTC by Report Bug Copy Issue Report Show Similar Issues like this This code seems to be duplicated across your project. Duplicated code is one of the most pungent code smells. If you need to duplicate the same code in three or more different places, we strongly encourage you to look into extracting the code into a single class or operation. You can also find more detailed suggestions in the “Code” section of your repository. Loading history...
23		exit(_NOPERM);
24		}
25
26		/**
27		* @return AdminerCustomization
28		*/
29		function adminer_object()
		0 ignored issues – show Best Practice introduced 2016-07-19 20:27 UTC by Report Bug Copy Issue Report Show Similar Issues like this The function `adminer_object()` has been defined more than once; this definition is ignored, only the first definition in `admin/getEditor.php` (L26-74) is considered. This check looks for functions that have already been defined in other files. Some Codebases, like WordPress, make a practice of defining functions multiple times. This may lead to problems with the detection of function parameters and types. If you really need to do this, you can mark the duplicate definition with the `@ignore` annotation. /** * @ignore */ function getUser() { } function getUser($id, $realm) { } See also the PhpDoc documentation for @ignore. Loading history...
30		{
31		// required to run any plugin
32		include_once dirname(__DIR__) . '/include/plugins/plugin.php';
33		// include_once dirname(__DIR__) . "/include/plugins/plugin.php";
		0 ignored issues – show Unused Code Comprehensibility introduced 2016-07-19 20:27 UTC by Report Bug Copy Issue Report Show Similar Issues like this `50%` 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...
34		include_once dirname(__DIR__) . '/include/plugins/frames.php';
35
36		// autoloader
37		// foreach (glob("plugins/*.php") as $filename) {
		0 ignored issues – show Unused Code Comprehensibility introduced 2016-07-19 20:27 UTC by Report Bug Copy Issue Report Show Similar Issues like this `60%` 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...
38		// include_once "./$filename";
39		// }
40
41		$plugins = array(
42		// specify enabled plugins here
43		// new AdminerDumpXml,
44		// new AdminerTinymce,
45		// new AdminerFileUpload("data/"),
		0 ignored issues – show Unused Code Comprehensibility introduced 2016-07-19 20:27 UTC by Report Bug Copy Issue Report Show Similar Issues like this `63%` 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...
46		// new AdminerSlugify,
47		// new AdminerTranslation,
48		// new AdminerForeignSystem,
49		new AdminerFrames
50		);
51
52		// It is possible to combine customization and plugins:
53		/**
54		* Class AdminerCustomization
55		*/
56		class AdminerCustomization extends AdminerPlugin
		0 ignored issues – show Comprehensibility Best Practice introduced 2016-07-19 20:27 UTC by Report Bug Copy Issue Report Show Similar Issues like this The type `AdminerCustomization` has been defined more than once; this definition is ignored, only the first definition in `admin/getEditor.php` (L50-71) is considered. This check looks for classes that have been defined more than once. If you can, we would recommend to use standard object-oriented programming techniques. For example, to avoid multiple types, it might make sense to create a common interface, and then multiple, different implementations for that interface. This also has the side-effect of providing you with better IDE auto-completion, static analysis and also better OPCode caching from PHP. Loading history...
57		{
58		}
59
60		return new AdminerCustomization($plugins);
61
62		// return new AdminerPlugin($plugins);
		0 ignored issues – show Unused Code Comprehensibility introduced 2016-07-19 20:27 UTC by Report Bug Copy Issue Report Show Similar Issues like this `60%` 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...
63		}
64
65		// include original Adminer or Adminer Editor
66		include_once dirname(__DIR__) . '/include/adminer.php';
67

XoopsModules25x / adminer

Issues (895)

Security Analysis not enabled

admin/getMysql.php (7 issues)

Labels

Severity

Introduced By

Upgrade to new PHP Analysis Engine

Duplication Side-by-Side

Filter issues like