Issues in RedirectListener.php (master) - Issues in master - ahilles107/web-publisher - Measure and Improve Code Quality continuously with Scrutinizer

Issues (541)

Security Analysis 8 potential 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.

Cross-Site Scripting (6)

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 (1)

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 (1)

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.

EventListener/RedirectListener.php (1 issue)

Labels

Security 1

Severity

Critical 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

declare(strict_types=1);

/*
 * This file is part of the Superdesk Web Publisher Core Bundle.
 *
 * Copyright 2018 Sourcefabric z.ú. and contributors.
 *
 * For the full copyright and license information, please see the
 * AUTHORS and LICENSE files distributed with this source code.
 *
 * @copyright 2018 Sourcefabric z.ú
 * @license http://www.superdesk.org/license
 */

namespace SWP\Bundle\TemplatesSystemBundle\EventListener;

use Symfony\Component\HttpFoundation\RedirectResponse;
use Symfony\Component\HttpKernel\Exception\NotFoundHttpException;
use Symfony\Component\HttpKernel\Event\FilterResponseEvent;

/**
 * Class RedirectListener.
 */
class RedirectListener
{
    /**
     * Check if request have attribute for redirection.
     * if it exists - perform redirect.
     *
     * @param FilterResponseEvent $event
     */
    public function onKernelResponse(FilterResponseEvent $event)
    {
        $request = $event->getRequest();
        // Redirect request to url set in template
        if ($request->attributes->has('_swp_redirect')) {
            $redirectData = $request->attributes->get('_swp_redirect');
            $request->attributes->remove('_swp_redirect');
            if ($request->getUri() === $redirectData['url']) {
                // Prevent redirect loops
                return;
            }

            $event->setResponse(new RedirectResponse($redirectData['url'], $redirectData['code']));
// for HTML
$sanitized = htmlentities($tainted, ENT_QUOTES);

// for URLs
$sanitized = urlencode($tainted);
        }

        // Redirect request to 404 error page
        if ($request->attributes->has('_swp_not_found')) {
            $message = $request->attributes->get('_swp_not_found');
            $request->attributes->remove('_swp_not_found');

            throw new NotFoundHttpException($message);
        }
    }
}


Issues (541)

Security Analysis 8 potential vulnerabilities

EventListener/RedirectListener.php (1 issue)

Labels

Severity

Introduced By

Upgrade to new PHP Analysis Engine

2 paths for user data to reach this point

Used in output context

Preventing Cross-Site-Scripting Attacks

General Strategies to prevent injection

1			<?php
2
3			declare(strict_types=1);
4
5			/*
6			* This file is part of the Superdesk Web Publisher Core Bundle.
7			*
8			* Copyright 2018 Sourcefabric z.ú. and contributors.
9			*
10			* For the full copyright and license information, please see the
11			* AUTHORS and LICENSE files distributed with this source code.
12			*
13			* @copyright 2018 Sourcefabric z.ú
14			* @license http://www.superdesk.org/license
15			*/
16
17			namespace SWP\Bundle\TemplatesSystemBundle\EventListener;
18
19			use Symfony\Component\HttpFoundation\RedirectResponse;
20			use Symfony\Component\HttpKernel\Exception\NotFoundHttpException;
21			use Symfony\Component\HttpKernel\Event\FilterResponseEvent;
22
23			/**
24			* Class RedirectListener.
25			*/
26			class RedirectListener
27			{
28			/**
29			* Check if request have attribute for redirection.
30			* if it exists - perform redirect.
31			*
32			* @param FilterResponseEvent $event
33			*/
34			public function onKernelResponse(FilterResponseEvent $event)
35			{
36			$request = $event->getRequest();
37			// Redirect request to url set in template
38			if ($request->attributes->has('_swp_redirect')) {
39			$redirectData = $request->attributes->get('_swp_redirect');
40			$request->attributes->remove('_swp_redirect');
41			if ($request->getUri() === $redirectData['url']) {
42			// Prevent redirect loops
43			return;
44			}
45
46			$event->setResponse(new RedirectResponse($redirectData['url'], $redirectData['code']));
			0 ignored issues – show Security Cross-Site Scripting introduced 2019-03-13 12:36 UTC by Report Bug Copy Issue Report Show Similar Issues like this `$redirectData['url']` can contain request data and is used in output context(s) leading to a potential security vulnerability. 2 paths for user data to reach this point 1. Path: `$this->parameters['HTTP_AUTHORIZATION']` seems to return tainted data, and `$authorizationHeader` is assigned in ServerBag.php on line 59 `$this->parameters['HTTP_AUTHORIZATION']` seems to return tainted data, and `$authorizationHeader` is assigned in vendor/ServerBag.php on line 59 ParameterBag::$parameters is assigned in vendor/ServerBag.php on line 74 Tainted property ParameterBag::$parameters is read in vendor/ParameterBag.php on line 77 ParameterBag::get() returns tainted data, and `$redirectData` is assigned in src/SWP/Bundle/TemplatesSystemBundle/EventListener/RedirectListener.php on line 39 2. Path: Read from `$_POST,` and `$_POST` is passed to Request::createRequestFromFactory() in Request.php on line 285 Read from `$_POST,` and `$_POST` is passed to Request::createRequestFromFactory() in vendor/Request.php on line 285 `$request` is passed to Request::__construct() in vendor/Request.php on line 1981 `$request` is passed to Request::initialize() in vendor/Request.php on line 239 `$request` is passed to ParameterBag::__construct() in vendor/Request.php on line 257 ParameterBag::$parameters is assigned in vendor/ParameterBag.php on line 28 Tainted property ParameterBag::$parameters is read in vendor/ParameterBag.php on line 77 ParameterBag::get() returns tainted data, and `$redirectData` is assigned in src/SWP/Bundle/TemplatesSystemBundle/EventListener/RedirectListener.php on line 39 Used in output context RedirectResponse::__construct() uses RedirectResponse::setTargetUrl() ($url) in vendor/RedirectResponse.php on line 39 RedirectResponse::setTargetUrl() uses Response::setContent() ($content) in vendor/RedirectResponse.php on line 92 Response::setContent() uses property Response::$content for writing in vendor/Response.php on line 404 Property Response::$content is used in echo in vendor/Response.php on line 363 Preventing Cross-Site-Scripting Attacks Cross-Site-Scripting allows an attacker to inject malicious code into your website - in particular Javascript code, and have that code executed with the privileges of a visiting user. This can be used to obtain data, or perform actions on behalf of that visiting user. In order to prevent this, make sure to escape all user-provided data: // for HTML $sanitized = htmlentities($tainted, ENT_QUOTES); // for URLs $sanitized = urlencode($tainted); General Strategies to prevent injection In general, it is advisable to prevent any user-data to reach this point. This can be done by white-listing certain values: if ( ! in_array($value, array('this-is-allowed', 'and-this-too'), true)) { throw new \InvalidArgumentException('This input is not allowed.'); } For numeric data, we recommend to explicitly cast the data: $sanitized = (integer) $tainted; Loading history...
47			}
48
49			// Redirect request to 404 error page
50			if ($request->attributes->has('_swp_not_found')) {
51			$message = $request->attributes->get('_swp_not_found');
52			$request->attributes->remove('_swp_not_found');
53
54			throw new NotFoundHttpException($message);
55			}
56			}
57			}
58

ahilles107 / web-publisher

Issues (541)

Security Analysis 8 potential vulnerabilities

EventListener/RedirectListener.php (1 issue)

Labels

Severity

Introduced By

Upgrade to new PHP Analysis Engine

2 paths for user data to reach this point

Used in output context

Preventing Cross-Site-Scripting Attacks

General Strategies to prevent injection

Duplication Side-by-Side

Filter issues like