Issues in ht-img-module.global.php (master) - Issues in master - hrevert/HtImgModule - Measure and Improve Code Quality continuously with Scrutinizer

Issues (115)

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.

config/ht-img-module.global.php (8 issues)

Labels

Severity

Minor 8

Ujjwal Ojha 8

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

/**
 * HtImgModule Configuration
 *
 * If you have a ./config/autoload/ directory set up for your project, you can
 * drop this config file in it and change the values as you wish.
 */

$options = [
    /**
     * Enable Cache
     *
     * Whether or not to cache image in public path,
     * so that Apache(or whatever) can directly get image
     * This can improve a lot of performance
     *
     * Default: true
     * Accepted values: boolean
     */
    // 'enable_cache' => true,


    /**
     * Image Source Path Stack
     *
     * Folders where to look for the requested file (similiar to Zend Framework 2 template path stack)
     *
     * Default: Empty array|array()
     * Accepted values: array containing folders or directories
     */
    //'img_source_path_stack' => ['data/images/'],


    /**
     * Image Source Map
     *
     * Exact path to image (similiar to Zend Framework 2 template map)
     *
     * Default: Empty array|array()
     * Accepted values: array containing key as image relative path and value as image real path
     */
    //'img_source_map' => array('hello/world.png' => 'data/img/hello/world.png'),


    /**
     * Imagine Driver
     *
     * Default: gd
     * Accepted values: one of gd, imagick or gmagick
     * It is registered as service which you can obtain throught ServiceLocator aware classes with:
     * $imagine = $this->getServiceLocator()->get('HtImg\Imagine');
     */
    //'driver' => 'gd',


     /**
      * Filters which can be accessed through view helper, 'imgUrl' easily
      */
    //'filters' => [],


     /**
      * Web Root
      *
      * Default: public (For Zend Skeleton Application)
      */
    //'web_root' => 'public_html',


     /**
      * Cache Path(Relative to web root)
      *
      * Default: htimg
      */
    //'cache_path' => 'htimg'

    /**
     * Filter Loaders
     */
    //'filter_loaders' => [],


    /**
     * Cache Expiry
     *
     * Interval in seconds after which a cached image will expire and new cache is to be created
     *
     * Default: 86400   (1 day)
     * Accepted value: Integer
     */
    //'cache_expiry' => 86400

    /**
     * Default Image Loader
     *
     * Image Loader determines how to load a image for a "filter"
     * This option means the default image loader(for all filters)
     * Please see the docs for creating a custom image loader
     */
    // 'default_image_loader' => 'FileSystem',

];

/**
 * You do not need to edit below this line
 */
return [
    'htimg' => $options
];


1			<?php
2
3			/**
4			* HtImgModule Configuration
5			*
6			* If you have a ./config/autoload/ directory set up for your project, you can
7			* drop this config file in it and change the values as you wish.
8			*/
9
10			$options = [
11			/**
12			* Enable Cache
13			*
14			* Whether or not to cache image in public path,
15			* so that Apache(or whatever) can directly get image
16			* This can improve a lot of performance
17			*
18			* Default: true
19			* Accepted values: boolean
20			*/
21			// 'enable_cache' => true,
			0 ignored issues – show Unused Code Comprehensibility introduced 2018-04-27 18:36 UTC by Report Bug Copy Issue Report Show Similar Issues like this `43%` 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...
22
23			/**
24			* Image Source Path Stack
25			*
26			* Folders where to look for the requested file (similiar to Zend Framework 2 template path stack)
27			*
28			* Default: Empty array\|array()
29			* Accepted values: array containing folders or directories
30			*/
31			//'img_source_path_stack' => ['data/images/'],
			0 ignored issues – show Unused Code Comprehensibility introduced 2018-04-27 18:36 UTC by Report Bug Copy Issue Report Show Similar Issues like this `75%` 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...
32
33			/**
34			* Image Source Map
35			*
36			* Exact path to image (similiar to Zend Framework 2 template map)
37			*
38			* Default: Empty array\|array()
39			* Accepted values: array containing key as image relative path and value as image real path
40			*/
41			//'img_source_map' => array('hello/world.png' => 'data/img/hello/world.png'),
			0 ignored issues – show Unused Code Comprehensibility introduced 2018-04-27 18:36 UTC by Report Bug Copy Issue Report Show Similar Issues like this `62%` 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...
42
43			/**
44			* Imagine Driver
45			*
46			* Default: gd
47			* Accepted values: one of gd, imagick or gmagick
48			* It is registered as service which you can obtain throught ServiceLocator aware classes with:
49			* $imagine = $this->getServiceLocator()->get('HtImg\Imagine');
50			*/
51			//'driver' => 'gd',
			0 ignored issues – show Unused Code Comprehensibility introduced 2018-04-27 18:36 UTC by Report Bug Copy Issue Report Show Similar Issues like this `67%` 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...
52
53			/**
54			* Filters which can be accessed through view helper, 'imgUrl' easily
55			*/
56			//'filters' => [],
			0 ignored issues – show Unused Code Comprehensibility introduced 2018-04-27 18:36 UTC by Report Bug Copy Issue Report Show Similar Issues like this `72%` 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...
57
58			/**
59			* Web Root
60			*
61			* Default: public (For Zend Skeleton Application)
62			*/
63			//'web_root' => 'public_html',
			0 ignored issues – show Unused Code Comprehensibility introduced 2018-04-27 18:36 UTC by Report Bug Copy Issue Report Show Similar Issues like this `67%` 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...
64
65			/**
66			* Cache Path(Relative to web root)
67			*
68			* Default: htimg
69			*/
70			//'cache_path' => 'htimg'
71
72			/**
73			* Filter Loaders
74			*/
75			//'filter_loaders' => [],
			0 ignored issues – show Unused Code Comprehensibility introduced 2018-04-27 18:36 UTC by Report Bug Copy Issue Report Show Similar Issues like this `72%` 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...
76
77			/**
78			* Cache Expiry
79			*
80			* Interval in seconds after which a cached image will expire and new cache is to be created
81			*
82			* Default: 86400 (1 day)
83			* Accepted value: Integer
84			*/
85			//'cache_expiry' => 86400
86
87			/**
88			* Default Image Loader
89			*
90			* Image Loader determines how to load a image for a "filter"
91			* This option means the default image loader(for all filters)
92			* Please see the docs for creating a custom image loader
93			*/
94			// 'default_image_loader' => 'FileSystem',
			0 ignored issues – show Unused Code Comprehensibility introduced 2018-04-27 18:36 UTC by Report Bug Copy Issue Report Show Similar Issues like this `58%` 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...
95			];
96
97			/**
98			* You do not need to edit below this line
99			*/
100			return [
101			'htimg' => $options
102			];
103

GitHub Access Token became invalid

Issues (115)

Security Analysis no request data

config/ht-img-module.global.php (8 issues)

Labels

Severity

Introduced By

Upgrade to new PHP Analysis Engine

hrevert / HtImgModule

GitHub Access Token became invalid

Issues (115)

Security Analysis no request data

config/ht-img-module.global.php (8 issues)

Labels

Severity

Introduced By

Upgrade to new PHP Analysis Engine

Duplication Side-by-Side

Filter issues like