Issues (443)

Security Analysis    no request data  

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

  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.

Hooks/PageRendererRender/PreProcessHook.php (1 issue)

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

1
<?php
2
namespace DCNGmbH\MooxCore\Hooks\PageRendererRender;
3
4
/***************************************************************
5
 *
6
 *  The MIT License (MIT)
7
 *
8
 *  Copyright (c) 2014 Benjamin Kott, http://www.bk2k.info
9
 *
10
 *  Permission is hereby granted, free of charge, to any person obtaining a copy
11
 *  of this software and associated documentation files (the "Software"), to deal
12
 *  in the Software without restriction, including without limitation the rights
13
 *  to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
14
 *  copies of the Software, and to permit persons to whom the Software is
15
 *  furnished to do so, subject to the following conditions:
16
 *
17
 *  The above copyright notice and this permission notice shall be included in
18
 *  all copies or substantial portions of the Software.
19
 *
20
 *  THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
21
 *  IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
22
 *  FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
23
 *  AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
24
 *  LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
25
 *  OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
26
 *  THE SOFTWARE.
27
 *
28
 ***************************************************************/
29
30
use DCNGmbH\MooxCore\Service\CompileService;
31
32
/**
33
 * @author Benjamin Kott <[email protected]>
34
 */
35
class PreProcessHook {
36
37
	/**
38
	 * @param array $params
39
	 * @param \TYPO3\CMS\Core\Page\PageRenderer $pagerenderer
40
	 */
41
	public function execute(&$params, &$pagerenderer) {
42
43
		if (TYPO3_MODE !== 'FE' || !is_array($params['cssFiles'])) {
44
			return;
45
		}
46
		$files = array();
47
		foreach ($params['cssFiles'] as $file => $settings) {
48
			$compiledFile = CompileService::getCompiledFile($file);
49
			if ($compiledFile) {
0 ignored issues
show
Bug Best Practice introduced by
The expression $compiledFile of type string|false is loosely compared to true; this is ambiguous if the string can be empty. You might want to explicitly use !== false instead.

In PHP, under loose comparison (like ==, or !=, or switch conditions), values of different types might be equal.

For string values, the empty string '' is a special case, in particular the following results might be unexpected:

''   == false // true
''   == null  // true
'ab' == false // false
'ab' == null  // false

// It is often better to use strict comparison
'' === false // false
'' === null  // false
Loading history...
50
				$settings['file'] = $compiledFile;
51
				$files[$compiledFile] = $settings;
52
			} else {
53
				$files[$file] = $settings;
54
			}
55
		}
56
		$params['cssFiles'] = $files;
57
	}
58
59
}