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/export/DumpFileOutput.php (3 issues)

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
 * Stream outputter to send data to a file.
4
 *
5
 * Copyright © 2003, 2005, 2006 Brion Vibber <[email protected]>
6
 * https://www.mediawiki.org/
7
 *
8
 * This program is free software; you can redistribute it and/or modify
9
 * it under the terms of the GNU General Public License as published by
10
 * the Free Software Foundation; either version 2 of the License, or
11
 * (at your option) any later version.
12
 *
13
 * This program is distributed in the hope that it will be useful,
14
 * but WITHOUT ANY WARRANTY; without even the implied warranty of
15
 * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
16
 * GNU General Public License for more details.
17
 *
18
 * You should have received a copy of the GNU General Public License along
19
 * with this program; if not, write to the Free Software Foundation, Inc.,
20
 * 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
21
 * http://www.gnu.org/copyleft/gpl.html
22
 *
23
 * @file
24
 */
25
26
/**
27
 * @ingroup Dump
28
 */
29
class DumpFileOutput extends DumpOutput {
30
	protected $handle = false, $filename;
0 ignored issues
show
It is generally advisable to only define one property per statement.

Only declaring a single property per statement allows you to later on add doc comments more easily.

It is also recommended by PSR2, so it is a common style that many people expect.

Loading history...
31
32
	/**
33
	 * @param string $file
34
	 */
35
	function __construct( $file ) {
36
		$this->handle = fopen( $file, "wt" );
0 ignored issues
show
Documentation Bug introduced by
It seems like fopen($file, 'wt') of type resource is incompatible with the declared type boolean of property $handle.

Our type inference engine has found an assignment to a property that is incompatible with the declared type of that property.

Either this assignment is in error or the assigned type should be added to the documentation/type hint for that property..

Loading history...
37
		$this->filename = $file;
38
	}
39
40
	/**
41
	 * @param string $string
42
	 */
43
	function writeCloseStream( $string ) {
44
		parent::writeCloseStream( $string );
45
		if ( $this->handle ) {
46
			fclose( $this->handle );
47
			$this->handle = false;
48
		}
49
	}
50
51
	/**
52
	 * @param string $string
53
	 */
54
	function write( $string ) {
55
		fputs( $this->handle, $string );
56
	}
57
58
	/**
59
	 * @param string $newname
60
	 */
61
	function closeRenameAndReopen( $newname ) {
62
		$this->closeAndRename( $newname, true );
63
	}
64
65
	/**
66
	 * @param string $newname
67
	 * @throws MWException
68
	 */
69
	function renameOrException( $newname ) {
70
			if ( !rename( $this->filename, $newname ) ) {
71
				throw new MWException( __METHOD__ . ": rename of file {$this->filename} to $newname failed\n" );
72
			}
73
	}
74
75
	/**
76
	 * @param array $newname
77
	 * @return string
78
	 * @throws MWException
79
	 */
80
	function checkRenameArgCount( $newname ) {
81
		if ( is_array( $newname ) ) {
82
			if ( count( $newname ) > 1 ) {
83
				throw new MWException( __METHOD__ . ": passed multiple arguments for rename of single file\n" );
84
			} else {
85
				$newname = $newname[0];
86
			}
87
		}
88
		return $newname;
89
	}
90
91
	/**
92
	 * @param string $newname
93
	 * @param bool $open
94
	 */
95
	function closeAndRename( $newname, $open = false ) {
96
		$newname = $this->checkRenameArgCount( $newname );
97
		if ( $newname ) {
98
			if ( $this->handle ) {
99
				fclose( $this->handle );
100
				$this->handle = false;
101
			}
102
			$this->renameOrException( $newname );
103
			if ( $open ) {
104
				$this->handle = fopen( $this->filename, "wt" );
0 ignored issues
show
Documentation Bug introduced by
It seems like fopen($this->filename, 'wt') of type resource is incompatible with the declared type boolean of property $handle.

Our type inference engine has found an assignment to a property that is incompatible with the declared type of that property.

Either this assignment is in error or the assigned type should be added to the documentation/type hint for that property..

Loading history...
105
			}
106
		}
107
	}
108
109
	/**
110
	 * @return string|null
111
	 */
112
	function getFilenames() {
113
		return $this->filename;
114
	}
115
}
116