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/cdb.php (5 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 30 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
 * cdb inspector tool
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
 * @todo document
22
 * @ingroup Maintenance
23
 */
24
use \Cdb\Exception as CdbException;
0 ignored issues
show
This use statement conflicts with another class in this namespace, CdbException.

Let’s assume that you have a directory layout like this:

.
|-- OtherDir
|   |-- Bar.php
|   `-- Foo.php
`-- SomeDir
    `-- Foo.php

and let’s assume the following content of Bar.php:

// Bar.php
namespace OtherDir;

use SomeDir\Foo; // This now conflicts the class OtherDir\Foo

If both files OtherDir/Foo.php and SomeDir/Foo.php are loaded in the same runtime, you will see a PHP error such as the following:

PHP Fatal error:  Cannot use SomeDir\Foo as Foo because the name is already in use in OtherDir/Foo.php

However, as OtherDir/Foo.php does not necessarily have to be loaded and the error is only triggered if it is loaded before OtherDir/Bar.php, this problem might go unnoticed for a while. In order to prevent this error from surfacing, you must import the namespace with a different alias:

// Bar.php
namespace OtherDir;

use SomeDir\Foo as SomeDirFoo; // There is no conflict anymore.
Loading history...
25
use \Cdb\Reader as CdbReader;
0 ignored issues
show
This use statement conflicts with another class in this namespace, CdbReader.

Let’s assume that you have a directory layout like this:

.
|-- OtherDir
|   |-- Bar.php
|   `-- Foo.php
`-- SomeDir
    `-- Foo.php

and let’s assume the following content of Bar.php:

// Bar.php
namespace OtherDir;

use SomeDir\Foo; // This now conflicts the class OtherDir\Foo

If both files OtherDir/Foo.php and SomeDir/Foo.php are loaded in the same runtime, you will see a PHP error such as the following:

PHP Fatal error:  Cannot use SomeDir\Foo as Foo because the name is already in use in OtherDir/Foo.php

However, as OtherDir/Foo.php does not necessarily have to be loaded and the error is only triggered if it is loaded before OtherDir/Bar.php, this problem might go unnoticed for a while. In order to prevent this error from surfacing, you must import the namespace with a different alias:

// Bar.php
namespace OtherDir;

use SomeDir\Foo as SomeDirFoo; // There is no conflict anymore.
Loading history...
26
27
/** */
28
require_once __DIR__ . '/commandLine.inc';
29
30
function cdbShowHelp( $command ) {
31
	$commandList = [
32
		'load' => 'load a cdb file for reading',
33
		'get' => 'get a value for a key',
34
		'exit' => 'exit cdb',
35
		'quit' => 'exit cdb',
36
		'help' => 'help about a command',
37
	];
38
	if ( !$command ) {
39
		$command = 'fullhelp';
40
	}
41
	if ( $command === 'fullhelp' ) {
42
		$max_cmd_len = max( array_map( 'strlen', array_keys( $commandList ) ) );
43
		foreach ( $commandList as $cmd => $desc ) {
44
			printf( "%-{$max_cmd_len}s: %s\n", $cmd, $desc );
45
		}
46
	} elseif ( isset( $commandList[$command] ) ) {
47
		print "$command: $commandList[$command]\n";
48
	} else {
49
		print "$command: command does not exist or no help for it\n";
50
	}
51
}
52
53
do {
54
	$bad = false;
55
	$showhelp = false;
56
	$quit = false;
57
	static $fileHandle = false;
58
59
	$line = Maintenance::readconsole();
60
	if ( $line === false ) {
61
		exit;
62
	}
63
64
	$args = explode( ' ', $line, 2 );
65
	$command = array_shift( $args );
66
67
	// process command
68
	switch ( $command ) {
69
		case 'help':
70
			// show an help message
71
			cdbShowHelp( array_shift( $args ) );
72
			break;
73
		case 'load':
74
			if ( !isset( $args[0] ) ) {
75
				print "Need a filename there buddy\n";
76
				break;
77
			}
78
			$file = $args[0];
79
			print "Loading cdb file $file...";
80
			try {
81
				$fileHandle = CdbReader::open( $file );
82
			} catch ( CdbException $e ) {
0 ignored issues
show
Coding Style Comprehensibility introduced by
Consider adding a comment why this CATCH block is empty.
Loading history...
83
			}
84
85
			if ( !$fileHandle ) {
86
				print "not a cdb file or unable to read it\n";
87
			} else {
88
				print "ok\n";
89
			}
90
			break;
91
		case 'get':
92
			if ( !$fileHandle ) {
93
				print "Need to load a cdb file first\n";
94
				break;
95
			}
96
			if ( !isset( $args[0] ) ) {
97
				print "Need to specify a key, Luke\n";
98
				break;
99
			}
100
			try {
101
				$res = $fileHandle->get( $args[0] );
102
			} catch ( CdbException $e ) {
103
				print "Unable to read key from file\n";
104
				break;
105
			}
106 View Code Duplication
			if ( $res === false ) {
107
				print "No such key/value pair\n";
108
			} elseif ( is_string( $res ) ) {
109
				print "$res\n";
110
			} else {
111
				var_dump( $res );
0 ignored issues
show
Security Debugging Code introduced by
var_dump($res); looks like debug code. Are you sure you do not want to remove it? This might expose sensitive data.
Loading history...
112
			}
113
			break;
114
		case 'quit':
115
		case 'exit':
116
			$quit = true;
117
			break;
118
119
		default:
120
			$bad = true;
121
	} // switch() end
122
123
	if ( $bad ) {
124
		if ( $command ) {
125
			print "Bad command\n";
126
		}
127
	} else {
128
		if ( function_exists( 'readline_add_history' ) ) {
129
			readline_add_history( $line );
130
		}
131
	}
132
} while ( !$quit );
133