Issues (4122)

Security Analysis    not enabled

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.

includes/libs/HttpStatus.php (1 issue)

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

1
<?php
2
/**
3
 * List of HTTP status codes.
4
 *
5
 * This program is free software; you can redistribute it and/or modify
6
 * it under the terms of the GNU General Public License as published by
7
 * the Free Software Foundation; either version 2 of the License, or
8
 * (at your option) any later version.
9
 *
10
 * This program is distributed in the hope that it will be useful,
11
 * but WITHOUT ANY WARRANTY; without even the implied warranty of
12
 * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
13
 * GNU General Public License for more details.
14
 *
15
 * You should have received a copy of the GNU General Public License along
16
 * with this program; if not, write to the Free Software Foundation, Inc.,
17
 * 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
18
 * http://www.gnu.org/copyleft/gpl.html
19
 *
20
 * @file
21
 */
22
23
/**
24
 * @todo document
25
 */
26
class HttpStatus {
27
28
	/**
29
	 * Get the message associated with an HTTP response status code
30
	 *
31
	 * @param int $code Status code
32
	 * @return string|null Message, or null if $code is not known
33
	 */
34
	public static function getMessage( $code ) {
35
		static $statusMessage = [
36
			100 => 'Continue',
37
			101 => 'Switching Protocols',
38
			102 => 'Processing',
39
			200 => 'OK',
40
			201 => 'Created',
41
			202 => 'Accepted',
42
			203 => 'Non-Authoritative Information',
43
			204 => 'No Content',
44
			205 => 'Reset Content',
45
			206 => 'Partial Content',
46
			207 => 'Multi-Status',
47
			300 => 'Multiple Choices',
48
			301 => 'Moved Permanently',
49
			302 => 'Found',
50
			303 => 'See Other',
51
			304 => 'Not Modified',
52
			305 => 'Use Proxy',
53
			307 => 'Temporary Redirect',
54
			400 => 'Bad Request',
55
			401 => 'Unauthorized',
56
			402 => 'Payment Required',
57
			403 => 'Forbidden',
58
			404 => 'Not Found',
59
			405 => 'Method Not Allowed',
60
			406 => 'Not Acceptable',
61
			407 => 'Proxy Authentication Required',
62
			408 => 'Request Timeout',
63
			409 => 'Conflict',
64
			410 => 'Gone',
65
			411 => 'Length Required',
66
			412 => 'Precondition Failed',
67
			413 => 'Request Entity Too Large',
68
			414 => 'Request-URI Too Large',
69
			415 => 'Unsupported Media Type',
70
			416 => 'Request Range Not Satisfiable',
71
			417 => 'Expectation Failed',
72
			422 => 'Unprocessable Entity',
73
			423 => 'Locked',
74
			424 => 'Failed Dependency',
75
			428 => 'Precondition Required',
76
			429 => 'Too Many Requests',
77
			431 => 'Request Header Fields Too Large',
78
			500 => 'Internal Server Error',
79
			501 => 'Not Implemented',
80
			502 => 'Bad Gateway',
81
			503 => 'Service Unavailable',
82
			504 => 'Gateway Timeout',
83
			505 => 'HTTP Version Not Supported',
84
			507 => 'Insufficient Storage',
85
			511 => 'Network Authentication Required',
86
		];
87
		return isset( $statusMessage[$code] ) ? $statusMessage[$code] : null;
88
	}
89
90
	/**
91
	 * Output an HTTP status code header
92
	 *
93
	 * @since 1.26
94
	 * @param int $code Status code
95
	 */
96
	public static function header( $code ) {
0 ignored issues
show
header uses the super-global variable $_SERVER which is generally not recommended.

Instead of super-globals, we recommend to explicitly inject the dependencies of your class. This makes your code less dependent on global state and it becomes generally more testable:

// Bad
class Router
{
    public function generate($path)
    {
        return $_SERVER['HOST'].$path;
    }
}

// Better
class Router
{
    private $host;

    public function __construct($host)
    {
        $this->host = $host;
    }

    public function generate($path)
    {
        return $this->host.$path;
    }
}

class Controller
{
    public function myAction(Request $request)
    {
        // Instead of
        $page = isset($_GET['page']) ? intval($_GET['page']) : 1;

        // Better (assuming you use the Symfony2 request)
        $page = $request->query->get('page', 1);
    }
}
Loading history...
97
		static $version = null;
98
		$message = self::getMessage( $code );
99
		if ( $message === null ) {
100
			trigger_error( "Unknown HTTP status code $code", E_USER_WARNING );
101
			return false;
102
		}
103
104
		if ( $version === null ) {
105
			$version = isset( $_SERVER['SERVER_PROTOCOL'] ) &&
106
				$_SERVER['SERVER_PROTOCOL'] === 'HTTP/1.0' ?
107
					'1.0' :
108
					'1.1';
109
		}
110
111
		header( "HTTP/$version $code $message" );
112
	}
113
114
}
115