Issues in wp-tests-config.php (master) - Issues in master - Automattic/jetpack - Measure and Improve Code Quality continuously with Scrutinizer

Issues (3867)

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.

tools/docker/config/wp-tests-config.php (3 issues)

Labels

Severity

Major 3

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
/**
 * A wp-config for testing.
 *
 * @package automattic/jetpack
 */

/* Path to the WordPress codebase you'd like to test. Add a forward slash in the end. */
define( 'ABSPATH', '/var/www/html/' );

/*
 * Path to the theme to test with.
 *
 * The 'default' theme is symlinked from test/phpunit/data/themedir1/default into
 * the themes directory of the WordPress installation defined above.
 */
define( 'WP_DEFAULT_THEME', 'default' );

// Test with multisite enabled.
// Alternatively, use the tests/phpunit/multisite.xml configuration file.
// phpcs:ignore Squiz.Commenting.InlineComment.InvalidEndChar
// define( 'WP_TESTS_MULTISITE', true );

// Force known bugs to be run.
// Tests with an associated Trac ticket that is still open are normally skipped.
// phpcs:ignore Squiz.Commenting.InlineComment.InvalidEndChar
// define( 'WP_TESTS_FORCE_KNOWN_BUGS', true );

// Test with WordPress debug mode (default).
define( 'WP_DEBUG', true );

// Enable error logging for tests.
define( 'WP_DEBUG_LOG', true );

// Additional constants for better error log.
@error_reporting( E_ALL ); // phpcs:ignore
// For example instead of
@mkdir($dir);

// Better use
if (@mkdir($dir) === false) {
    throw new \RuntimeException('The directory '.$dir.' could not be created.');
}
@ini_set( 'log_errors', true ); // phpcs:ignore
// For example instead of
@mkdir($dir);

// Better use
if (@mkdir($dir) === false) {
    throw new \RuntimeException('The directory '.$dir.' could not be created.');
}
@ini_set( 'log_errors_max_len', '0' ); // phpcs:ignore
// For example instead of
@mkdir($dir);

// Better use
if (@mkdir($dir) === false) {
    throw new \RuntimeException('The directory '.$dir.' could not be created.');
}

define( 'WP_DEBUG_DISPLAY', false );
define( 'CONCATENATE_SCRIPTS', false );
define( 'SCRIPT_DEBUG', true );
define( 'SAVEQUERIES', true );

// ** MySQL settings ** //

// This configuration file will be used by the copy of WordPress being tested.
// wordpress/wp-config.php will be ignored.

// WARNING WARNING WARNING!
// These tests will DROP ALL TABLES in the database with the prefix named below.
// DO NOT use a production database or one that is shared with something else.

define( 'DB_NAME', getenv( 'MYSQL_DATABASE' ) );
define( 'DB_USER', getenv( 'MYSQL_USER' ) );
define( 'DB_PASSWORD', getenv( 'MYSQL_PASSWORD' ) );
define( 'DB_HOST', getenv( 'MYSQL_HOST' ) );
define( 'DB_CHARSET', 'utf8' );
define( 'DB_COLLATE', '' );

/**#@+
 * Authentication Unique Keys and Salts.
 *
 * Change these to different unique phrases!
 * You can generate these using the {@link https://api.wordpress.org/secret-key/1.1/salt/ WordPress.org secret-key service}
 */
define( 'AUTH_KEY', 'put your unique phrase here' );
define( 'SECURE_AUTH_KEY', 'put your unique phrase here' );
define( 'LOGGED_IN_KEY', 'put your unique phrase here' );
define( 'NONCE_KEY', 'put your unique phrase here' );
define( 'AUTH_SALT', 'put your unique phrase here' );
define( 'SECURE_AUTH_SALT', 'put your unique phrase here' );
define( 'LOGGED_IN_SALT', 'put your unique phrase here' );
define( 'NONCE_SALT', 'put your unique phrase here' );

// phpcs:ignore WordPress.WP.GlobalVariablesOverride.Prohibited, VariableAnalysis.CodeAnalysis.VariableAnalysis.UnusedVariable
$table_prefix = 'wptests_';   // Only numbers, letters, and underscores please!

define( 'WP_TESTS_DOMAIN', 'example.org' );
define( 'WP_TESTS_EMAIL', '[email protected]' );
define( 'WP_TESTS_TITLE', 'Test Blog' );

define( 'WP_PHP_BINARY', 'php' );

define( 'WPLANG', '' );


1			<?php
2			/**
3			* A wp-config for testing.
4			*
5			* @package automattic/jetpack
6			*/
7
8			/* Path to the WordPress codebase you'd like to test. Add a forward slash in the end. */
9			define( 'ABSPATH', '/var/www/html/' );
10
11			/*
12			* Path to the theme to test with.
13			*
14			* The 'default' theme is symlinked from test/phpunit/data/themedir1/default into
15			* the themes directory of the WordPress installation defined above.
16			*/
17			define( 'WP_DEFAULT_THEME', 'default' );
18
19			// Test with multisite enabled.
20			// Alternatively, use the tests/phpunit/multisite.xml configuration file.
21			// phpcs:ignore Squiz.Commenting.InlineComment.InvalidEndChar
22			// define( 'WP_TESTS_MULTISITE', true );
23
24			// Force known bugs to be run.
25			// Tests with an associated Trac ticket that is still open are normally skipped.
26			// phpcs:ignore Squiz.Commenting.InlineComment.InvalidEndChar
27			// define( 'WP_TESTS_FORCE_KNOWN_BUGS', true );
28
29			// Test with WordPress debug mode (default).
30			define( 'WP_DEBUG', true );
31
32			// Enable error logging for tests.
33			define( 'WP_DEBUG_LOG', true );
34
35			// Additional constants for better error log.
36			@error_reporting( E_ALL ); // phpcs:ignore
			0 ignored issues – show Security Best Practice introduced 2020-01-31 22:45 UTC by Report Bug Copy Issue Report Show Similar Issues like this It seems like you do not handle an error condition here. This can introduce security issues, and is generally not recommended. If you suppress an error, we recommend checking for the error condition explicitly: // For example instead of @mkdir($dir); // Better use if (@mkdir($dir) === false) { throw new \RuntimeException('The directory '.$dir.' could not be created.'); } Loading history...
37			@ini_set( 'log_errors', true ); // phpcs:ignore
			0 ignored issues – show Security Best Practice introduced 2020-01-31 22:45 UTC by Report Bug Copy Issue Report Show Similar Issues like this It seems like you do not handle an error condition here. This can introduce security issues, and is generally not recommended. If you suppress an error, we recommend checking for the error condition explicitly: // For example instead of @mkdir($dir); // Better use if (@mkdir($dir) === false) { throw new \RuntimeException('The directory '.$dir.' could not be created.'); } Loading history...
38			@ini_set( 'log_errors_max_len', '0' ); // phpcs:ignore
			0 ignored issues – show Security Best Practice introduced 2020-01-31 22:45 UTC by Report Bug Copy Issue Report Show Similar Issues like this It seems like you do not handle an error condition here. This can introduce security issues, and is generally not recommended. If you suppress an error, we recommend checking for the error condition explicitly: // For example instead of @mkdir($dir); // Better use if (@mkdir($dir) === false) { throw new \RuntimeException('The directory '.$dir.' could not be created.'); } Loading history...
39
40			define( 'WP_DEBUG_DISPLAY', false );
41			define( 'CONCATENATE_SCRIPTS', false );
42			define( 'SCRIPT_DEBUG', true );
43			define( 'SAVEQUERIES', true );
44
45			// MySQL settings //
46
47			// This configuration file will be used by the copy of WordPress being tested.
48			// wordpress/wp-config.php will be ignored.
49
50			// WARNING WARNING WARNING!
51			// These tests will DROP ALL TABLES in the database with the prefix named below.
52			// DO NOT use a production database or one that is shared with something else.
53
54			define( 'DB_NAME', getenv( 'MYSQL_DATABASE' ) );
55			define( 'DB_USER', getenv( 'MYSQL_USER' ) );
56			define( 'DB_PASSWORD', getenv( 'MYSQL_PASSWORD' ) );
57			define( 'DB_HOST', getenv( 'MYSQL_HOST' ) );
58			define( 'DB_CHARSET', 'utf8' );
59			define( 'DB_COLLATE', '' );
60
61			/**#@+
62			* Authentication Unique Keys and Salts.
63			*
64			* Change these to different unique phrases!
65			* You can generate these using the {@link https://api.wordpress.org/secret-key/1.1/salt/ WordPress.org secret-key service}
66			*/
67			define( 'AUTH_KEY', 'put your unique phrase here' );
68			define( 'SECURE_AUTH_KEY', 'put your unique phrase here' );
69			define( 'LOGGED_IN_KEY', 'put your unique phrase here' );
70			define( 'NONCE_KEY', 'put your unique phrase here' );
71			define( 'AUTH_SALT', 'put your unique phrase here' );
72			define( 'SECURE_AUTH_SALT', 'put your unique phrase here' );
73			define( 'LOGGED_IN_SALT', 'put your unique phrase here' );
74			define( 'NONCE_SALT', 'put your unique phrase here' );
75
76			// phpcs:ignore WordPress.WP.GlobalVariablesOverride.Prohibited, VariableAnalysis.CodeAnalysis.VariableAnalysis.UnusedVariable
77			$table_prefix = 'wptests_'; // Only numbers, letters, and underscores please!
78
79			define( 'WP_TESTS_DOMAIN', 'example.org' );
80			define( 'WP_TESTS_EMAIL', '[email protected]' );
81			define( 'WP_TESTS_TITLE', 'Test Blog' );
82
83			define( 'WP_PHP_BINARY', 'php' );
84
85			define( 'WPLANG', '' );
86

Automattic / jetpack

Issues (3867)

Security Analysis not enabled

tools/docker/config/wp-tests-config.php (3 issues)

Labels

Severity

Introduced By

Upgrade to new PHP Analysis Engine

Duplication Side-by-Side

Filter issues like