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.

maintenance/invalidateUserSessions.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
0 ignored issues
show
Coding Style Compatibility introduced by
For compatibility and reusability of your code, PSR1 recommends that a file should introduce either new symbols (like classes, functions, etc.) or have side-effects (like outputting something, or including other files), but not both at the same time. The first symbol is defined on line 36 and the first side effect is on line 28.

The PSR-1: Basic Coding Standard recommends that a file should either introduce new symbols, that is classes, functions, constants or similar, or have side effects. Side effects are anything that executes logic, like for example printing output, changing ini settings or writing to a file.

The idea behind this recommendation is that merely auto-loading a class should not change the state of an application. It also promotes a cleaner style of programming and makes your code less prone to errors, because the logic is not spread out all over the place.

To learn more about the PSR-1, please see the PHP-FIG site on the PSR-1.

Loading history...
2
/**
3
 * Invalidate the sessions of certain users on the wiki.
4
 * If you want to invalidate all sessions, use $wgAuthenticationTokenVersion instead.
5
 *
6
 * This program is free software; you can redistribute it and/or modify
7
 * it under the terms of the GNU General Public License as published by
8
 * the Free Software Foundation; either version 2 of the License, or
9
 * (at your option) any later version.
10
 *
11
 * This program is distributed in the hope that it will be useful,
12
 * but WITHOUT ANY WARRANTY; without even the implied warranty of
13
 * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
14
 * GNU General Public License for more details.
15
 *
16
 * You should have received a copy of the GNU General Public License along
17
 * with this program; if not, write to the Free Software Foundation, Inc.,
18
 * 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
19
 * http://www.gnu.org/copyleft/gpl.html
20
 *
21
 * @file
22
 * @ingroup Maintenance
23
 */
24
25
use MediaWiki\MediaWikiServices;
26
use MediaWiki\Session\SessionManager;
27
28
require_once __DIR__ . '/Maintenance.php';
29
30
/**
31
 * Invalidate the sessions of certain users on the wiki.
32
 * If you want to invalidate all sessions, use $wgAuthenticationTokenVersion instead.
33
 *
34
 * @ingroup Maintenance
35
 */
36
class InvalidateUserSesssions extends Maintenance {
37 View Code Duplication
	public function __construct() {
38
		parent::__construct();
39
		$this->addDescription(
40
			'Invalidate the sessions of certain users on the wiki.'
41
		);
42
		$this->addOption( 'user', 'Username', false, true, 'u' );
43
		$this->addOption( 'file', 'File with one username per line', false, true, 'f' );
44
		$this->setBatchSize( 1000 );
45
	}
46
47
	public function execute() {
48
		$username = $this->getOption( 'user' );
49
		$file = $this->getOption( 'file' );
50
51
		if ( $username === null && $file === null ) {
52
			$this->error( 'Either --user or --file is required', 1 );
53
		} elseif ( $username !== null && $file !== null ) {
54
			$this->error( 'Cannot use both --user and --file', 1 );
55
		}
56
57
		if ( $username !== null ) {
58
			$usernames = [ $username ];
59
		} else {
60
			$usernames = is_readable( $file ) ?
61
				file( $file, FILE_IGNORE_NEW_LINES | FILE_SKIP_EMPTY_LINES ) : false;
62
			if ( $usernames === false ) {
63
				$this->error( "Could not open $file", 2 );
64
			}
65
		}
66
67
		$i = 0;
68
		$lbFactory = MediaWikiServices::getInstance()->getDBLoadBalancerFactory();
69
		$sessionManager = SessionManager::singleton();
70
		foreach ( $usernames as $username ) {
0 ignored issues
show
The expression $usernames of type false|array is not guaranteed to be traversable. How about adding an additional type check?

There are different options of fixing this problem.

  1. If you want to be on the safe side, you can add an additional type-check:

    $collection = json_decode($data, true);
    if ( ! is_array($collection)) {
        throw new \RuntimeException('$collection must be an array.');
    }
    
    foreach ($collection as $item) { /** ... */ }
    
  2. If you are sure that the expression is traversable, you might want to add a doc comment cast to improve IDE auto-completion and static analysis:

    /** @var array $collection */
    $collection = json_decode($data, true);
    
    foreach ($collection as $item) { /** .. */ }
    
  3. Mark the issue as a false-positive: Just hover the remove button, in the top-right corner of this issue for more options.

Loading history...
71
			$i++;
72
			$user = User::newFromName( $username );
73
			try {
74
				$sessionManager->invalidateSessionsForUser( $user );
0 ignored issues
show
It seems like $user defined by \User::newFromName($username) on line 72 can also be of type false; however, MediaWiki\Session\Sessio...lidateSessionsForUser() does only seem to accept object<User>, did you maybe forget to handle an error condition?

This check looks for type mismatches where the missing type is false. This is usually indicative of an error condtion.

Consider the follow example

<?php

function getDate($date)
{
    if ($date !== null) {
        return new DateTime($date);
    }

    return false;
}

This function either returns a new DateTime object or false, if there was an error. This is a typical pattern in PHP programming to show that an error has occurred without raising an exception. The calling code should check for this returned false before passing on the value to another function or method that may not be able to handle a false.

Loading history...
75
				if ( $user->getId() ) {
76
					$this->output( "Invalidated sessions for user $username\n" );
77
				} else {
78
					# session invalidation might still work if there is a central identity provider
79
					$this->output( "Could not find user $username, tried to invalidate anyway\n" );
80
				}
81
			} catch ( Exception $e ) {
82
				$this->output( "Failed to invalidate sessions for user $username | "
83
					. str_replace( [ "\r", "\n" ], ' ', $e->getMessage() ) . "\n" );
84
			}
85
86
			if ( $i % $this->mBatchSize ) {
87
				$lbFactory->waitForReplication();
88
			}
89
		}
90
	}
91
}
92
93
$maintClass = "InvalidateUserSesssions";
94
require_once RUN_MAINTENANCE_IF_MAIN;
95