Completed
Push — update/media-extractor-summary... ( ea9570...96f076 )
by Jeremy
09:23
created

class.jetpack-client.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
class Jetpack_Client {
4
	const WPCOM_JSON_API_HOST    = 'public-api.wordpress.com';
5
	const WPCOM_JSON_API_VERSION = '1.1';
6
7
	/**
8
	 * Makes an authorized remote request using Jetpack_Signature
9
	 *
10
	 * @return array|WP_Error WP HTTP response on success
11
	 */
12
	public static function remote_request( $args, $body = null ) {
13
		$defaults = array(
14
			'url' => '',
15
			'user_id' => 0,
16
			'blog_id' => 0,
17
			'auth_location' => JETPACK_CLIENT__AUTH_LOCATION,
18
			'method' => 'POST',
19
			'timeout' => 10,
20
			'redirection' => 0,
21
		);
22
23
		$args = wp_parse_args( $args, $defaults );
24
25
		$args['blog_id'] = (int) $args['blog_id'];
26
27
		if ( 'header' != $args['auth_location'] ) {
28
			$args['auth_location'] = 'query_string';
29
		}
30
31
		$token = Jetpack_Data::get_access_token( $args['user_id'] );
0 ignored issues
show
$args['user_id'] is of type integer|string, but the function expects a boolean.

It seems like the type of the argument is not accepted by the function/method which you are calling.

In some cases, in particular if PHP’s automatic type-juggling kicks in this might be fine. In other cases, however this might be a bug.

We suggest to add an explicit type cast like in the following example:

function acceptsInteger($int) { }

$x = '123'; // string "123"

// Instead of
acceptsInteger($x);

// we recommend to use
acceptsInteger((integer) $x);
Loading history...
32
		if ( !$token ) {
33
			return new Jetpack_Error( 'missing_token' );
34
		}
35
36
		$method = strtoupper( $args['method'] );
37
38
		$timeout = intval( $args['timeout'] );
39
40
		$redirection = $args['redirection'];
41
42
		$request = compact( 'method', 'body', 'timeout', 'redirection' );
43
44
		@list( $token_key, $secret ) = explode( '.', $token->secret );
0 ignored issues
show
Security Best Practice introduced by
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...
45
		if ( empty( $token ) || empty( $secret ) ) {
46
			return new Jetpack_Error( 'malformed_token' );
47
		}
48
49
		$token_key = sprintf( '%s:%d:%d', $token_key, JETPACK__API_VERSION, $token->external_user_id );
50
51
		require_once JETPACK__PLUGIN_DIR . 'class.jetpack-signature.php';
52
53
		$time_diff = (int) Jetpack_Options::get_option( 'time_diff' );
54
		$jetpack_signature = new Jetpack_Signature( $token->secret, $time_diff );
55
56
		$timestamp = time() + $time_diff;
57
58
		if( function_exists( 'wp_generate_password' ) ) {
59
			$nonce = wp_generate_password( 10, false );
60
		} else {
61
			$nonce = substr( sha1( rand( 0, 1000000 ) ), 0, 10);
62
		}
63
64
		// Kind of annoying.  Maybe refactor Jetpack_Signature to handle body-hashing
65 View Code Duplication
		if ( is_null( $body ) ) {
66
			$body_hash = '';
67
		} else {
68
			if ( !is_string( $body ) ) {
69
				return new Jetpack_Error( 'invalid_body', 'Body is malformed.' );
70
			}
71
			$body_hash = jetpack_sha1_base64( $body );
72
		}
73
74
		$auth = array(
75
			'token' => $token_key,
76
			'timestamp' => $timestamp,
77
			'nonce' => $nonce,
78
			'body-hash' => $body_hash,
79
		);
80
81
		if ( false !== strpos( $args['url'], 'xmlrpc.php' ) ) {
82
			$url_args = array(
83
				'for'           => 'jetpack',
84
				'wpcom_blog_id' => Jetpack_Options::get_option( 'id' ),
85
			);
86
		} else {
87
			$url_args = array();
88
		}
89
90
		if ( 'header' != $args['auth_location'] ) {
91
			$url_args += $auth;
92
		}
93
94
		$url = add_query_arg( urlencode_deep( $url_args ), $args['url'] );
95
		$url = Jetpack::fix_url_for_bad_hosts( $url );
96
97
		$signature = $jetpack_signature->sign_request( $token_key, $timestamp, $nonce, $body_hash, $method, $url, $body, false );
98
99
		if ( !$signature || is_wp_error( $signature ) ) {
100
			return $signature;
101
		}
102
103
		// Send an Authorization header so various caches/proxies do the right thing
104
		$auth['signature'] = $signature;
105
		$auth['version'] = JETPACK__VERSION;
106
		$header_pieces = array();
107
		foreach ( $auth as $key => $value ) {
108
			$header_pieces[] = sprintf( '%s="%s"', $key, $value );
109
		}
110
		$request['headers'] = array(
111
			'Authorization' => "X_JETPACK " . join( ' ', $header_pieces ),
112
		);
113
114
		if ( 'header' != $args['auth_location'] ) {
115
			$url = add_query_arg( 'signature', urlencode( $signature ), $url );
116
		}
117
118
		return Jetpack_Client::_wp_remote_request( $url, $request );
119
	}
120
121
	/**
122
	 * Wrapper for wp_remote_request().  Turns off SSL verification for certain SSL errors.
123
	 * This is lame, but many, many, many hosts have misconfigured SSL.
124
	 *
125
	 * When Jetpack is registered, the jetpack_fallback_no_verify_ssl_certs option is set to the current time if:
126
	 * 1. a certificate error is found AND
127
	 * 2. not verifying the certificate works around the problem.
128
	 *
129
	 * The option is checked on each request.
130
	 *
131
	 * @internal
132
	 * @see Jetpack::fix_url_for_bad_hosts()
133
	 *
134
	 * @return array|WP_Error WP HTTP response on success
135
	 */
136
	public static function _wp_remote_request( $url, $args, $set_fallback = false ) {
137
		/**
138
		 * SSL verification (`sslverify`) for the JetpackClient remote request
139
		 * defaults to off, use this filter to force it on.
140
		 *
141
		 * Return `true` to ENABLE SSL verification, return `false`
142
		 * to DISABLE SSL verification.
143
		 *
144
		 * @since 3.6.0
145
		 *
146
		 * @param bool Whether to force `sslverify` or not.
147
		 */
148
		if ( apply_filters( 'jetpack_client_verify_ssl_certs', false ) ) {
149
			return wp_remote_request( $url, $args );
150
		}
151
152
		$fallback = Jetpack_Options::get_option( 'fallback_no_verify_ssl_certs' );
153
		if ( false === $fallback ) {
154
			Jetpack_Options::update_option( 'fallback_no_verify_ssl_certs', 0 );
155
		}
156
157
		if ( (int) $fallback ) {
158
			// We're flagged to fallback
159
			$args['sslverify'] = false;
160
		}
161
162
		$response = wp_remote_request( $url, $args );
163
164
		if (
165
			!$set_fallback                                     // We're not allowed to set the flag on this request, so whatever happens happens
166
		||
167
			isset( $args['sslverify'] ) && !$args['sslverify'] // No verification - no point in doing it again
168
		||
169
			!is_wp_error( $response )                          // Let it ride
170
		) {
171
			Jetpack_Client::set_time_diff( $response, $set_fallback );
172
			return $response;
173
		}
174
175
		// At this point, we're not flagged to fallback and we are allowed to set the flag on this request.
176
177
		$message = $response->get_error_message();
178
179
		// Is it an SSL Certificate verification error?
180
		if (
181
			false === strpos( $message, '14090086' ) // OpenSSL SSL3 certificate error
182
		&&
183
			false === strpos( $message, '1407E086' ) // OpenSSL SSL2 certificate error
184
		&&
185
			false === strpos( $message, 'error setting certificate verify locations' ) // cURL CA bundle not found
186
		&&
187
			false === strpos( $message, 'Peer certificate cannot be authenticated with' ) // cURL CURLE_SSL_CACERT: CA bundle found, but not helpful
188
			                                                                              // different versions of curl have different error messages
189
			                                                                              // this string should catch them all
190
		&&
191
			false === strpos( $message, 'Problem with the SSL CA cert' ) // cURL CURLE_SSL_CACERT_BADFILE: probably access rights
192
		) {
193
			// No, it is not.
194
			return $response;
195
		}
196
197
		// Redo the request without SSL certificate verification.
198
		$args['sslverify'] = false;
199
		$response = wp_remote_request( $url, $args );
200
201
		if ( !is_wp_error( $response ) ) {
202
			// The request went through this time, flag for future fallbacks
203
			Jetpack_Options::update_option( 'fallback_no_verify_ssl_certs', time() );
204
			Jetpack_Client::set_time_diff( $response, $set_fallback );
205
		}
206
207
		return $response;
208
	}
209
210
	public static function set_time_diff( &$response, $force_set = false ) {
211
		$code = wp_remote_retrieve_response_code( $response );
212
213
		// Only trust the Date header on some responses
214
		if ( 200 != $code && 304 != $code && 400 != $code && 401 != $code ) {
215
			return;
216
		}
217
218
		if ( !$date = wp_remote_retrieve_header( $response, 'date' ) ) {
219
			return;
220
		}
221
222
		if ( 0 >= $time = (int) strtotime( $date ) ) {
223
			return;
224
		}
225
226
		$time_diff = $time - time();
227
228
		if ( $force_set ) { // during register
229
			Jetpack_Options::update_option( 'time_diff', $time_diff );
230
		} else { // otherwise
231
			$old_diff = Jetpack_Options::get_option( 'time_diff' );
232
			if ( false === $old_diff || abs( $time_diff - (int) $old_diff ) > 10 ) {
233
				Jetpack_Options::update_option( 'time_diff', $time_diff );
234
			}
235
		}
236
	}
237
238
	/**
239
	 * Query the WordPress.com REST API using the blog token
240
	 *
241
	 * @param string  $path
242
	 * @param string  $version
243
	 * @param array   $args
244
	 * @param string  $body
0 ignored issues
show
Should the type for parameter $body not be string|null?

This check looks for @param annotations where the type inferred by our type inference engine differs from the declared type.

It makes a suggestion as to what type it considers more descriptive.

Most often this is a case of a parameter that can be null in addition to its declared types.

Loading history...
245
	 * @return array|WP_Error $response Data.
246
	 */
247
	static function wpcom_json_api_request_as_blog( $path, $version = self::WPCOM_JSON_API_VERSION, $args = array(), $body = null ) {
248
		$filtered_args = array_intersect_key( $args, array(
249
			'method'      => 'string',
250
			'timeout'     => 'int',
251
			'redirection' => 'int',
252
		) );
253
254
		/**
255
		 * Determines whether Jetpack can send outbound https requests to the WPCOM api.
256
		 *
257
		 * @since 3.6.0
258
		 *
259
		 * @param bool $proto Defaults to true.
260
		 */
261
		$proto = apply_filters( 'jetpack_can_make_outbound_https', true ) ? 'https' : 'http';
262
263
		// unprecedingslashit
264
		$_path = preg_replace( '/^\//', '', $path );
265
266
		// Use GET by default whereas `remote_request` uses POST
267
		if ( isset( $filtered_args['method'] ) && strtoupper( $filtered_args['method'] === 'POST' ) ) {
268
			$request_method = 'POST';
269
		} else {
270
			$request_method = 'GET';
271
		}
272
273
		$validated_args = array_merge( $filtered_args, array(
274
			'url'     => sprintf( '%s://%s/rest/v%s/%s', $proto, self::WPCOM_JSON_API_HOST, $version, $_path ),
275
			'blog_id' => (int) Jetpack_Options::get_option( 'id' ),
276
			'method'  => $request_method,
277
		) );
278
279
		return Jetpack_Client::remote_request( $validated_args, $body );
280
	}
281
282
}
283