Issues in PLTwig.php (master) - Issues in master - amarcinkowski/hospitalplugin - Measure and Improve Code Quality continuously with Scrutinizer

Issues (100)

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.

src/Twig/PLTwig.php (3 issues)

Labels

Severity

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 Hospitalplugin\Twig;

use Hospitalplugin\Twig\EscapePLCharsExtension;

class PLTwig {
	/**
	 * Loads Twig with polish settings.
	 * 
	 * @param string $viewsDir        	
	 * @return void|\Twig_Environment
	 */
	public static function load($viewsDir) {
		if (! class_exists ( 'Twig_Loader_Filesystem' )) {
			echo 'Twig not activated. Make sure you activate the plugin in
    <a href="/wp-admin/plugins.php#timber">/wp-admin/plugins.php</a>';
			return;
		}
		\Twig_Autoloader::register ();
		try {
			$loader = new \Twig_Loader_Filesystem ( $viewsDir );
			$twig = new \Twig_Environment ( $loader, array () );
			// 'debug' => true
			// 'cache' => '/tmp/'

			$twig->getExtension ( 'core' )->setTimezone ( 'Europe/Warsaw' ); //
interface User
{
    /** @return string */
    public function getPassword();
}

class MyUser implements User
{
    public function getPassword()
    {
        // return something
    }

    public function getDisplayName()
    {
        // return some name.
    }
}

class AuthSystem
{
    public function authenticate(User $user)
    {
        $this->logger->info(sprintf('Authenticating %s.', $user->getDisplayName()));
        // do something.
    }
}
			$twig->addExtension ( new EscapePLCharsExtension () );
			return $twig;
		} catch ( Exception $e ) {

			echo "ERR: " . $e;
		}
	}
}

Issues (100)

Security Analysis not enabled

src/Twig/PLTwig.php (3 issues)

Labels

Severity

Introduced By

Upgrade to new PHP Analysis Engine

Available Fixes

1			<?php
2
3			namespace Hospitalplugin\Twig;
4
5			use Hospitalplugin\Twig\EscapePLCharsExtension;
6
7			class PLTwig {
8			/**
9			* Loads Twig with polish settings.
10			*
11			* @param string $viewsDir
12			* @return void\|\Twig_Environment
13			*/
14			public static function load($viewsDir) {
15			if (! class_exists ( 'Twig_Loader_Filesystem' )) {
16			echo 'Twig not activated. Make sure you activate the plugin in
17			<a href="/wp-admin/plugins.php#timber">/wp-admin/plugins.php</a>';
18			return;
19			}
20			\Twig_Autoloader::register ();
21			try {
22			$loader = new \Twig_Loader_Filesystem ( $viewsDir );
23			$twig = new \Twig_Environment ( $loader, array () );
24			// 'debug' => true
25			// 'cache' => '/tmp/'
			0 ignored issues – show Unused Code Comprehensibility introduced 2016-02-10 21:14 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...
26			$twig->getExtension ( 'core' )->setTimezone ( 'Europe/Warsaw' ); //
			0 ignored issues – show Bug introduced 2015-11-23 17:00 UTC by Report Bug Copy Issue Report Show Similar Issues like this It seems like you code against a concrete implementation and not the interface `Twig_ExtensionInterface` as the method `setTimezone()` does only exist in the following implementations of said interface: `Twig_Extension_Core`. Let’s take a look at an example: interface User { /** @return string / public function getPassword(); } class MyUser implements User { public function getPassword() { // return something } public function getDisplayName() { // return some name. } } class AuthSystem { public function authenticate(User $user) { $this->logger->info(sprintf('Authenticating %s.', $user->getDisplayName())); // do something. } } In the above example, the authenticate() method works fine as long as you just pass instances of MyUser. However, if you now also want to pass a different implementation of User which does not have a getDisplayName() method, the code will break. Available Fixes Change the type-hint for the parameter: class AuthSystem { public function authenticate(MyUser $user) { / ... / } } Add an additional type-check: class AuthSystem { public function authenticate(User $user) { if ($user instanceof MyUser) { $this->logger->info(/* ... /); } // or alternatively if ( ! $user instanceof MyUser) { throw new \LogicException( '$user must be an instance of MyUser, ' .'other instances are not supported.' ); } } } Note:* PHP Analyzer uses reverse abstract interpretation to narrow down the types inside the if block in such a case. Add the method to the interface: interface User { /** @return string / public function getPassword(); /* @return string */ public function getDisplayName(); } Loading history...
27			$twig->addExtension ( new EscapePLCharsExtension () );
28			return $twig;
29			} catch ( Exception $e ) {
			0 ignored issues – show Bug introduced 2015-11-23 17:00 UTC by Report Bug Copy Issue Report Show Similar Issues like this The class `Hospitalplugin\Twig\Exception` does not exist. Did you forget a USE statement, or did you not list all dependencies? Scrutinizer analyzes your `composer.json`/`composer.lock` file if available to determine the classes, and functions that are defined by your dependencies. It seems like the listed class was neither found in your dependencies, nor was it found in the analyzed files in your repository. If you are using some other form of dependency management, you might want to disable this analysis. Loading history...
30			echo "ERR: " . $e;
31			}
32			}
33			}

amarcinkowski / hospitalplugin

Issues (100)

Security Analysis not enabled

src/Twig/PLTwig.php (3 issues)

Labels

Severity

Introduced By

Upgrade to new PHP Analysis Engine

Available Fixes

Duplication Side-by-Side

Filter issues like