Issues in Php.php (master) - Issues in master - unyx/utils - Measure and Improve Code Quality continuously with Scrutinizer

Issues (94)

Security Analysis no request data

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.

platform/Php.php (7 issues)

Labels

Bug 7

Severity

Major 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 namespace nyx\utils\platform;

// Internal dependencies
use nyx\utils;

/**
 * PHP
 *
 * Utils for introspecting information about PHP itself.
 *
 * @package     Nyx\Utils\Platform
 * @version     0.0.1
 * @author      Michal Chojnacki <[email protected]>
 * @copyright   2012-2016 Nyx Dev Team
 * @link        http://docs.muyo.io/nyx/utils/platform.html
 * @todo        Bitwise checks for combined phpinfo() sections when parsing information.
 */
class Php
{
    /**
     * The traits of the Php class.
     */
    use utils\traits\StaticallyExtendable;

    /**
     * @var bool    Whether PHP has been compiled with the "--enable-sigchild" flag.
     */
    private static $flags = [];

    /**
     * @var array   An array containing the output of phpinfo() calls, grouped together by the INFO_ constants
     *              used to retrieve them.
     */
    private static $info = [];

    /**
     * Checks whether PHP has been compiled with the given flag.
     *
     * @param   string  $flag   The name of the flag to check. The two initial hyphens can be omitted.
     * @return  bool            True when PHP has been compiled with the given flag, false otherwise.
     */
    public static function hasFlag(string $flag) : bool
    {
        // Standardize the flag name - remove starting hyphens.
        $flag = ltrim($flag, '-');

        // Return the check right away if it's already cached.
        if (isset(static::$flags[$flag])) {
class YourClass
{
    private static $someVariable;

    public static function getSomeVariable()
    {
        return static::$someVariable;
    }
}
            return static::$flags[$flag];
class YourClass
{
    private static $someVariable;

    public static function getSomeVariable()
    {
        return static::$someVariable;
    }
}
        }

        // Grab the output of phpinfo(). If INFO_ALL is already available, we will just parse it instead of
        // fetching INFO_GENERAL specifically for our case. Then we are simply going to check if the --string
        // appears in the info.
        $result = strpos(static::$info[INFO_ALL] ?? static::getInfo(INFO_GENERAL), '--'.$flag);
class YourClass
{
    private static $someVariable;

    public static function getSomeVariable()
    {
        return static::$someVariable;
    }
}

        // Cache the result and return it.
        return static::$flags[$flag] = false !== $result;
class YourClass
{
    private static $someVariable;

    public static function getSomeVariable()
    {
        return static::$someVariable;
    }
}
    }

    /**
     * Fetches, caches and returns the output of phpinfo().
     *
     * @param   int     $for    One of the INFO_* constants {@see http://php.net/manual/en/function.phpinfo.php}.
     * @return  string          The raw output of phpinfo.
     */
    public static function getInfo(int $for = INFO_ALL) : string
    {
        // Return the data right away if we've already cached the given section.
        if (isset(static::$info[$for])) {
class YourClass
{
    private static $someVariable;

    public static function getSomeVariable()
    {
        return static::$someVariable;
    }
}
            return static::$info[$for];
class YourClass
{
    private static $someVariable;

    public static function getSomeVariable()
    {
        return static::$someVariable;
    }
}
        }

        ob_start();
        phpinfo($for);

        return static::$info[$for] = ob_get_clean();
class YourClass
{
    private static $someVariable;

    public static function getSomeVariable()
    {
        return static::$someVariable;
    }
}
    }
}


1			<?php namespace nyx\utils\platform;
2
3			// Internal dependencies
4			use nyx\utils;
5
6			/**
7			* PHP
8			*
9			* Utils for introspecting information about PHP itself.
10			*
11			* @package Nyx\Utils\Platform
12			* @version 0.0.1
13			* @author Michal Chojnacki <[email protected]>
14			* @copyright 2012-2016 Nyx Dev Team
15			* @link http://docs.muyo.io/nyx/utils/platform.html
16			* @todo Bitwise checks for combined phpinfo() sections when parsing information.
17			*/
18			class Php
19			{
20			/**
21			* The traits of the Php class.
22			*/
23			use utils\traits\StaticallyExtendable;
24
25			/**
26			* @var bool Whether PHP has been compiled with the "--enable-sigchild" flag.
27			*/
28			private static $flags = [];
29
30			/**
31			* @var array An array containing the output of phpinfo() calls, grouped together by the INFO_ constants
32			* used to retrieve them.
33			*/
34			private static $info = [];
35
36			/**
37			* Checks whether PHP has been compiled with the given flag.
38			*
39			* @param string $flag The name of the flag to check. The two initial hyphens can be omitted.
40			* @return bool True when PHP has been compiled with the given flag, false otherwise.
41			*/
42			public static function hasFlag(string $flag) : bool
43			{
44			// Standardize the flag name - remove starting hyphens.
45			$flag = ltrim($flag, '-');
46
47			// Return the check right away if it's already cached.
48			if (isset(static::$flags[$flag])) {
			0 ignored issues – show Bug introduced 2017-02-06 17:58 UTC by Report Bug Copy Issue Report Show Similar Issues like this Since `$flags` is declared private, accessing it with `static` will lead to errors in possible sub-classes; consider using `self`, or increasing the visibility of `$flags` to at least protected. Let’s assume you have a class which uses late-static binding: class YourClass { private static $someVariable; public static function getSomeVariable() { return static::$someVariable; } } The code above will run fine in your PHP runtime. However, if you now create a sub-class and call the `getSomeVariable()` on that sub-class, you will receive a runtime error: class YourSubClass extends YourClass { } YourSubClass::getSomeVariable(); // Will cause an access error. In the case above, it makes sense to update `SomeClass` to use `self` instead: class SomeClass { private static $someVariable; public static function getSomeVariable() { return self::$someVariable; // self works fine with private. } } Loading history...
49			return static::$flags[$flag];
			0 ignored issues – show Bug introduced 2017-02-06 17:58 UTC by Report Bug Copy Issue Report Show Similar Issues like this Since `$flags` is declared private, accessing it with `static` will lead to errors in possible sub-classes; consider using `self`, or increasing the visibility of `$flags` to at least protected. Let’s assume you have a class which uses late-static binding: class YourClass { private static $someVariable; public static function getSomeVariable() { return static::$someVariable; } } The code above will run fine in your PHP runtime. However, if you now create a sub-class and call the `getSomeVariable()` on that sub-class, you will receive a runtime error: class YourSubClass extends YourClass { } YourSubClass::getSomeVariable(); // Will cause an access error. In the case above, it makes sense to update `SomeClass` to use `self` instead: class SomeClass { private static $someVariable; public static function getSomeVariable() { return self::$someVariable; // self works fine with private. } } Loading history...
50			}
51
52			// Grab the output of phpinfo(). If INFO_ALL is already available, we will just parse it instead of
53			// fetching INFO_GENERAL specifically for our case. Then we are simply going to check if the --string
54			// appears in the info.
55			$result = strpos(static::$info[INFO_ALL] ?? static::getInfo(INFO_GENERAL), '--'.$flag);
			0 ignored issues – show Bug introduced 2017-02-06 17:58 UTC by Report Bug Copy Issue Report Show Similar Issues like this Since `$info` is declared private, accessing it with `static` will lead to errors in possible sub-classes; consider using `self`, or increasing the visibility of `$info` to at least protected. Let’s assume you have a class which uses late-static binding: class YourClass { private static $someVariable; public static function getSomeVariable() { return static::$someVariable; } } The code above will run fine in your PHP runtime. However, if you now create a sub-class and call the `getSomeVariable()` on that sub-class, you will receive a runtime error: class YourSubClass extends YourClass { } YourSubClass::getSomeVariable(); // Will cause an access error. In the case above, it makes sense to update `SomeClass` to use `self` instead: class SomeClass { private static $someVariable; public static function getSomeVariable() { return self::$someVariable; // self works fine with private. } } Loading history...
56
57			// Cache the result and return it.
58			return static::$flags[$flag] = false !== $result;
			0 ignored issues – show Bug introduced 2017-02-06 17:58 UTC by Report Bug Copy Issue Report Show Similar Issues like this Since `$flags` is declared private, accessing it with `static` will lead to errors in possible sub-classes; consider using `self`, or increasing the visibility of `$flags` to at least protected. Let’s assume you have a class which uses late-static binding: class YourClass { private static $someVariable; public static function getSomeVariable() { return static::$someVariable; } } The code above will run fine in your PHP runtime. However, if you now create a sub-class and call the `getSomeVariable()` on that sub-class, you will receive a runtime error: class YourSubClass extends YourClass { } YourSubClass::getSomeVariable(); // Will cause an access error. In the case above, it makes sense to update `SomeClass` to use `self` instead: class SomeClass { private static $someVariable; public static function getSomeVariable() { return self::$someVariable; // self works fine with private. } } Loading history...
59			}
60
61			/**
62			* Fetches, caches and returns the output of phpinfo().
63			*
64			* @param int $for One of the INFO_* constants {@see http://php.net/manual/en/function.phpinfo.php}.
65			* @return string The raw output of phpinfo.
66			*/
67			public static function getInfo(int $for = INFO_ALL) : string
68			{
69			// Return the data right away if we've already cached the given section.
70			if (isset(static::$info[$for])) {
			0 ignored issues – show Bug introduced 2017-02-06 17:58 UTC by Report Bug Copy Issue Report Show Similar Issues like this Since `$info` is declared private, accessing it with `static` will lead to errors in possible sub-classes; consider using `self`, or increasing the visibility of `$info` to at least protected. Let’s assume you have a class which uses late-static binding: class YourClass { private static $someVariable; public static function getSomeVariable() { return static::$someVariable; } } The code above will run fine in your PHP runtime. However, if you now create a sub-class and call the `getSomeVariable()` on that sub-class, you will receive a runtime error: class YourSubClass extends YourClass { } YourSubClass::getSomeVariable(); // Will cause an access error. In the case above, it makes sense to update `SomeClass` to use `self` instead: class SomeClass { private static $someVariable; public static function getSomeVariable() { return self::$someVariable; // self works fine with private. } } Loading history...
71			return static::$info[$for];
			0 ignored issues – show Bug introduced 2017-02-06 17:58 UTC by Report Bug Copy Issue Report Show Similar Issues like this Since `$info` is declared private, accessing it with `static` will lead to errors in possible sub-classes; consider using `self`, or increasing the visibility of `$info` to at least protected. Let’s assume you have a class which uses late-static binding: class YourClass { private static $someVariable; public static function getSomeVariable() { return static::$someVariable; } } The code above will run fine in your PHP runtime. However, if you now create a sub-class and call the `getSomeVariable()` on that sub-class, you will receive a runtime error: class YourSubClass extends YourClass { } YourSubClass::getSomeVariable(); // Will cause an access error. In the case above, it makes sense to update `SomeClass` to use `self` instead: class SomeClass { private static $someVariable; public static function getSomeVariable() { return self::$someVariable; // self works fine with private. } } Loading history...
72			}
73
74			ob_start();
75			phpinfo($for);
76
77			return static::$info[$for] = ob_get_clean();
			0 ignored issues – show Bug introduced 2017-02-06 17:58 UTC by Report Bug Copy Issue Report Show Similar Issues like this Since `$info` is declared private, accessing it with `static` will lead to errors in possible sub-classes; consider using `self`, or increasing the visibility of `$info` to at least protected. Let’s assume you have a class which uses late-static binding: class YourClass { private static $someVariable; public static function getSomeVariable() { return static::$someVariable; } } The code above will run fine in your PHP runtime. However, if you now create a sub-class and call the `getSomeVariable()` on that sub-class, you will receive a runtime error: class YourSubClass extends YourClass { } YourSubClass::getSomeVariable(); // Will cause an access error. In the case above, it makes sense to update `SomeClass` to use `self` instead: class SomeClass { private static $someVariable; public static function getSomeVariable() { return self::$someVariable; // self works fine with private. } } Loading history...
78			}
79			}
80

unyx / utils

Issues (94)

Security Analysis no request data

platform/Php.php (7 issues)

Labels

Severity

Introduced By

Upgrade to new PHP Analysis Engine

Duplication Side-by-Side

Filter issues like