Issues in LoggerLayout.class.php (master) - Issues in master - horros/agavi2 - Measure and Improve Code Quality continuously with Scrutinizer

Issues (1131)

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/logging/LoggerLayout.class.php (2 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 Agavi\Logging;

// +---------------------------------------------------------------------------+
// | This file is part of the Agavi package.                                   |
// | Copyright (c) 2005-2011 the Agavi Project.                                |
// |                                                                           |
// | For the full copyright and license information, please view the LICENSE   |
// | file that was distributed with this source code. You can also view the    |
// | LICENSE file online at http://www.agavi.org/LICENSE.txt                   |
// |   vi: set noexpandtab:                                                    |
// |   Local Variables:                                                        |
// |   indent-tabs-mode: t                                                     |
// |   End:                                                                    |
// +---------------------------------------------------------------------------+

use Agavi\Core\Context;
use Agavi\Util\ParameterHolder;

/**
 * AgaviLoggerLayout allows you to specify a message layout for log messages.
 *
 * @package    agavi
 * @subpackage logging
 *
 * @author     Sean Kerr <[email protected]>
 * @copyright  Authors
 * @copyright  The Agavi Project
 *
 * @since      0.9.0
 *
 * @version    $Id$
 */
abstract class LoggerLayout extends ParameterHolder

{
    /**
     * @var        Context A Context instance.
     */
    protected $context = null;

    /**
     * @var        string A message layout.
     */
    protected $layout = null;

    /**
     * Initialize the Layout.
     *
     * @param      Context $context    A Context instance.
     * @param      array   $parameters An associative array of initialization parameters.
     *
     * @author     Veikko Mäkinen <[email protected]>
     * @since      0.10.0
     */
    public function initialize(Context $context, array $parameters = array())
    {
        $this->context = $context;
        $this->parameters = $parameters;
    }

    /**
     * Retrieve the current application context.
     *
     * @return     Context A Context instance.
     *
     * @author     Sean Kerr <[email protected]>
     * @since      0.10.0
     */
    final public function getContext()
    {
        return $this->context;
    }

    /**
     * Format a message.
     *
     * @param      LoggerMessage $message A Message instance.
     *
     * @return     string A formatted message.
     *
     * @author     Sean Kerr <[email protected]>
     * @since      0.9.0
     */
    abstract function format(LoggerMessage $message);


    /**
     * Retrieve the message layout.
     *
     * @return     string A message layout.
     *
     * @author     Sean Kerr <[email protected]>
     * @since      0.9.0
     */
    public function getLayout()
    {
        return $this->layout;
    }

    /**
     * Set the message layout.
     *
     * @param      string A message layout.
     *
     *
     * @author     Sean Kerr <[email protected]>
     * @since      0.9.0
     */
    public function setLayout($layout)
    {
        $this->layout = $layout;
    }
}


1		<?php
2		namespace Agavi\Logging;
3
4		// +---------------------------------------------------------------------------+
5		// \| This file is part of the Agavi package. \|
6		// \| Copyright (c) 2005-2011 the Agavi Project. \|
7		// \| \|
8		// \| For the full copyright and license information, please view the LICENSE \|
9		// \| file that was distributed with this source code. You can also view the \|
10		// \| LICENSE file online at http://www.agavi.org/LICENSE.txt \|
11		// \| vi: set noexpandtab: \|
12		// \| Local Variables: \|
13		// \| indent-tabs-mode: t \|
14		// \| End: \|
15		// +---------------------------------------------------------------------------+
16
17		use Agavi\Core\Context;
18		use Agavi\Util\ParameterHolder;
19
20		/**
21		* AgaviLoggerLayout allows you to specify a message layout for log messages.
22		*
23		* @package agavi
24		* @subpackage logging
25		*
26		* @author Sean Kerr <[email protected]>
27		* @copyright Authors
28		* @copyright The Agavi Project
29		*
30		* @since 0.9.0
31		*
32		* @version $Id$
33		*/
34	View Code Duplication	abstract class LoggerLayout extends ParameterHolder
		0 ignored issues – show Duplication introduced 2016-11-27 20:51 UTC by Report Bug Copy Issue Report Show Similar Issues like this This class seems to be duplicated in your project. Duplicated code is one of the most pungent code smells. If you need to duplicate the same code in three or more different places, we strongly encourage you to look into extracting the code into a single class or operation. You can also find more detailed suggestions in the “Code” section of your repository. Loading history...
35		{
36		/**
37		* @var Context A Context instance.
38		*/
39		protected $context = null;
40
41		/**
42		* @var string A message layout.
43		*/
44		protected $layout = null;
45
46		/**
47		* Initialize the Layout.
48		*
49		* @param Context $context A Context instance.
50		* @param array $parameters An associative array of initialization parameters.
51		*
52		* @author Veikko Mäkinen <[email protected]>
53		* @since 0.10.0
54		*/
55		public function initialize(Context $context, array $parameters = array())
56		{
57		$this->context = $context;
58		$this->parameters = $parameters;
59		}
60
61		/**
62		* Retrieve the current application context.
63		*
64		* @return Context A Context instance.
65		*
66		* @author Sean Kerr <[email protected]>
67		* @since 0.10.0
68		*/
69		final public function getContext()
70		{
71		return $this->context;
72		}
73
74		/**
75		* Format a message.
76		*
77		* @param LoggerMessage $message A Message instance.
78		*
79		* @return string A formatted message.
80		*
81		* @author Sean Kerr <[email protected]>
82		* @since 0.9.0
83		*/
84		abstract function format(LoggerMessage $message);
		0 ignored issues – show Best Practice introduced 2016-11-27 20:51 UTC by Report Bug Copy Issue Report Show Similar Issues like this It is generally recommended to explicitly declare the visibility for methods. Adding explicit visibility (`private`, `protected`, or `public`) is generally recommend to communicate to other developers how, and from where this method is intended to be used. Loading history...
85
86		/**
87		* Retrieve the message layout.
88		*
89		* @return string A message layout.
90		*
91		* @author Sean Kerr <[email protected]>
92		* @since 0.9.0
93		*/
94		public function getLayout()
95		{
96		return $this->layout;
97		}
98
99		/**
100		* Set the message layout.
101		*
102		* @param string A message layout.
103		*
104		*
105		* @author Sean Kerr <[email protected]>
106		* @since 0.9.0
107		*/
108		public function setLayout($layout)
109		{
110		$this->layout = $layout;
111		}
112		}
113

horros / agavi2

Issues (1131)

Security Analysis not enabled

src/logging/LoggerLayout.class.php (2 issues)

Labels

Severity

Introduced By

Upgrade to new PHP Analysis Engine

Duplication Side-by-Side

Filter issues like