Issues in Alert.php (master) - Issues in master - sibds/yii2-enterprise - Measure and Improve Code Quality continuously with Scrutinizer

Issues (1237)

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.

frontend/widgets/Alert.php (1 issue)

Labels

Bug 1

Severity

Major 1

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
/**
 * @link http://www.yiiframework.com/
 * @copyright Copyright (c) 2008 Yii Software LLC
 * @license http://www.yiiframework.com/license/
 */

namespace frontend\widgets;

/**
 * Alert widget renders a message from session flash. All flash messages are displayed
 * in the sequence they were assigned using setFlash. You can set message as following:
 *
 * ```php
 * \Yii::$app->getSession()->setFlash('error', 'This is the message');
 * \Yii::$app->getSession()->setFlash('success', 'This is the message');
 * \Yii::$app->getSession()->setFlash('info', 'This is the message');
 * ```
 *
 * Multiple messages could be set as follows:
 *
 * ```php
 * \Yii::$app->getSession()->setFlash('error', ['Error 1', 'Error 2']);
 * ```
 *
 * @author Kartik Visweswaran <[email protected]>
 * @author Alexander Makarov <[email protected]>
 */
class Alert extends \yii\bootstrap\Widget
{
    /**
     * @var array the alert types configuration for the flash messages.
     * This array is setup as $key => $value, where:
     * - $key is the name of the session flash variable
     * - $value is the bootstrap alert type (i.e. danger, success, info, warning)
     */
    public $alertTypes = [
        'error'   => 'alert-danger',
        'danger'  => 'alert-danger',
        'success' => 'alert-success',
        'info'    => 'alert-info',
        'warning' => 'alert-warning'
    ];

    /**
     * @var array the options for rendering the close button tag.
     */
    public $closeButton = [];

    public function init()
    {
        parent::init();

        $session = \Yii::$app->getSession();
class A
{
    public function foo() { }
}

class B extends A
{
    public function bar() { }
}

/**
 * @param A|B $x
 */
function someFunction($x)
{
    $x->foo(); // This call is fine as the method exists in A and B.
    $x->bar(); // This method only exists in B and might cause an error.
}
        $flashes = $session->getAllFlashes();
        $appendCss = isset($this->options['class']) ? ' ' . $this->options['class'] : '';

        foreach ($flashes as $type => $data) {
            if (isset($this->alertTypes[$type])) {
                $data = (array) $data;
                foreach ($data as $i => $message) {
                    /* initialize css class for each alert box */
                    $this->options['class'] = $this->alertTypes[$type] . $appendCss;

                    /* assign unique id to each alert box */
                    $this->options['id'] = $this->getId() . '-' . $type . '-' . $i;

                    echo \yii\bootstrap\Alert::widget([
                        'body' => $message,
                        'closeButton' => $this->closeButton,
                        'options' => $this->options,
                    ]);
                }

                $session->removeFlash($type);
            }
        }
    }
}


1			<?php
2			/**
3			* @link http://www.yiiframework.com/
4			* @copyright Copyright (c) 2008 Yii Software LLC
5			* @license http://www.yiiframework.com/license/
6			*/
7
8			namespace frontend\widgets;
9
10			/**
11			* Alert widget renders a message from session flash. All flash messages are displayed
12			* in the sequence they were assigned using setFlash. You can set message as following:
13			*
14			* ```php
15			* \Yii::$app->getSession()->setFlash('error', 'This is the message');
16			* \Yii::$app->getSession()->setFlash('success', 'This is the message');
17			* \Yii::$app->getSession()->setFlash('info', 'This is the message');
18			* ```
19			*
20			* Multiple messages could be set as follows:
21			*
22			* ```php
23			* \Yii::$app->getSession()->setFlash('error', ['Error 1', 'Error 2']);
24			* ```
25			*
26			* @author Kartik Visweswaran <[email protected]>
27			* @author Alexander Makarov <[email protected]>
28			*/
29			class Alert extends \yii\bootstrap\Widget
30			{
31			/**
32			* @var array the alert types configuration for the flash messages.
33			* This array is setup as $key => $value, where:
34			* - $key is the name of the session flash variable
35			* - $value is the bootstrap alert type (i.e. danger, success, info, warning)
36			*/
37			public $alertTypes = [
38			'error' => 'alert-danger',
39			'danger' => 'alert-danger',
40			'success' => 'alert-success',
41			'info' => 'alert-info',
42			'warning' => 'alert-warning'
43			];
44
45			/**
46			* @var array the options for rendering the close button tag.
47			*/
48			public $closeButton = [];
49
50			public function init()
51			{
52			parent::init();
53
54			$session = \Yii::$app->getSession();
			0 ignored issues – show Bug introduced 2016-02-19 10:10 UTC by Report Bug Copy Issue Report Show Similar Issues like this The method `getSession` does only exist in `yii\web\Application`, but not in `yii\console\Application`. It seems like the method you are trying to call exists only in some of the possible types. Let’s take a look at an example: class A { public function foo() { } } class B extends A { public function bar() { } } /** * @param A\|B $x / function someFunction($x) { $x->foo(); // This call is fine as the method exists in A and B. $x->bar(); // This method only exists in B and might cause an error. } Available Fixes Add an additional type-check: /* * @param A\|B $x / function someFunction($x) { $x->foo(); if ($x instanceof B) { $x->bar(); } } Only allow a single type to be passed if the variable comes from a parameter: function someFunction(B $x) { /* ... */ } Loading history...
55			$flashes = $session->getAllFlashes();
56			$appendCss = isset($this->options['class']) ? ' ' . $this->options['class'] : '';
57
58			foreach ($flashes as $type => $data) {
59			if (isset($this->alertTypes[$type])) {
60			$data = (array) $data;
61			foreach ($data as $i => $message) {
62			/* initialize css class for each alert box */
63			$this->options['class'] = $this->alertTypes[$type] . $appendCss;
64
65			/* assign unique id to each alert box */
66			$this->options['id'] = $this->getId() . '-' . $type . '-' . $i;
67
68			echo \yii\bootstrap\Alert::widget([
69			'body' => $message,
70			'closeButton' => $this->closeButton,
71			'options' => $this->options,
72			]);
73			}
74
75			$session->removeFlash($type);
76			}
77			}
78			}
79			}
80

sibds / yii2-enterprise

Issues (1237)

Security Analysis not enabled

frontend/widgets/Alert.php (1 issue)

Labels

Severity

Introduced By

Upgrade to new PHP Analysis Engine

Available Fixes

Duplication Side-by-Side

Filter issues like