{"containers":{"cna":{"affected":[{"product":"wp-cli","vendor":"wp-cli","versions":[{"status":"affected","version":"< 2.5.0"}]}],"descriptions":[{"lang":"en","value":"WP-CLI is the command-line interface for WordPress. An improper error handling in HTTPS requests management in WP-CLI version 0.12.0 and later allows remote attackers able to intercept the communication to remotely disable the certificate verification on WP-CLI side, gaining full control over the communication content, including the ability to impersonate update servers and push malicious updates towards WordPress instances controlled by the vulnerable WP-CLI agent, or push malicious updates toward WP-CLI itself. The vulnerability stems from the fact that the default behavior of `WP_CLI\\Utils\\http_request()` when encountering a TLS handshake error is to disable certificate validation and retry the same request. The default behavior has been changed with version 2.5.0 of WP-CLI and the `wp-cli/wp-cli` framework (via https://github.com/wp-cli/wp-cli/pull/5523) so that the `WP_CLI\\Utils\\http_request()` method accepts an `$insecure` option that is `false` by default and consequently that a TLS handshake failure is a hard error by default. This new default is a breaking change and ripples through to all consumers of `WP_CLI\\Utils\\http_request()`, including those in separate WP-CLI bundled or third-party packages. https://github.com/wp-cli/wp-cli/pull/5523 has also added an `--insecure` flag to the `cli update` command to counter this breaking change. There is no direct workaround for the default insecure behavior of `wp-cli/wp-cli` versions before 2.5.0. The workaround for dealing with the breaking change in the commands directly affected by the new secure default behavior is to add the `--insecure` flag to manually opt-in to the previous insecure behavior."}],"metrics":[{"cvssV3_1":{"attackComplexity":"LOW","attackVector":"NETWORK","availabilityImpact":"NONE","baseScore":9.1,"baseSeverity":"CRITICAL","confidentialityImpact":"HIGH","integrityImpact":"HIGH","privilegesRequired":"NONE","scope":"UNCHANGED","userInteraction":"NONE","vectorString":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.1"}}],"problemTypes":[{"descriptions":[{"cweId":"CWE-295","description":"CWE-295: Improper Certificate Validation","lang":"en","type":"CWE"}]}],"providerMetadata":{"dateUpdated":"2021-06-07T20:50:17.000Z","orgId":"a0819718-46f1-4df5-94e2-005712e83aaa","shortName":"GitHub_M"},"references":[{"tags":["x_refsource_CONFIRM"],"url":"https://github.com/wp-cli/wp-cli/security/advisories/GHSA-rwgm-f83r-v3qj"},{"tags":["x_refsource_MISC"],"url":"https://github.com/wp-cli/checksum-command/pull/86"},{"tags":["x_refsource_MISC"],"url":"https://github.com/wp-cli/config-command/pull/128"},{"tags":["x_refsource_MISC"],"url":"https://github.com/wp-cli/core-command/pull/186"},{"tags":["x_refsource_MISC"],"url":"https://github.com/wp-cli/extension-command/pull/287"},{"tags":["x_refsource_MISC"],"url":"https://github.com/wp-cli/package-command/pull/138"},{"tags":["x_refsource_MISC"],"url":"https://github.com/wp-cli/wp-cli/pull/5523"}],"source":{"advisory":"GHSA-rwgm-f83r-v3qj","discovery":"UNKNOWN"},"title":"Improper Certificate Validation in WP-CLI framework","x_legacyV4Record":{"CVE_data_meta":{"ASSIGNER":"security-advisories@github.com","ID":"CVE-2021-29504","STATE":"PUBLIC","TITLE":"Improper Certificate Validation in WP-CLI framework"},"affects":{"vendor":{"vendor_data":[{"product":{"product_data":[{"product_name":"wp-cli","version":{"version_data":[{"version_value":"< 2.5.0"}]}}]},"vendor_name":"wp-cli"}]}},"data_format":"MITRE","data_type":"CVE","data_version":"4.0","description":{"description_data":[{"lang":"eng","value":"WP-CLI is the command-line interface for WordPress. An improper error handling in HTTPS requests management in WP-CLI version 0.12.0 and later allows remote attackers able to intercept the communication to remotely disable the certificate verification on WP-CLI side, gaining full control over the communication content, including the ability to impersonate update servers and push malicious updates towards WordPress instances controlled by the vulnerable WP-CLI agent, or push malicious updates toward WP-CLI itself. The vulnerability stems from the fact that the default behavior of `WP_CLI\\Utils\\http_request()` when encountering a TLS handshake error is to disable certificate validation and retry the same request. The default behavior has been changed with version 2.5.0 of WP-CLI and the `wp-cli/wp-cli` framework (via https://github.com/wp-cli/wp-cli/pull/5523) so that the `WP_CLI\\Utils\\http_request()` method accepts an `$insecure` option that is `false` by default and consequently that a TLS handshake failure is a hard error by default. This new default is a breaking change and ripples through to all consumers of `WP_CLI\\Utils\\http_request()`, including those in separate WP-CLI bundled or third-party packages. https://github.com/wp-cli/wp-cli/pull/5523 has also added an `--insecure` flag to the `cli update` command to counter this breaking change. There is no direct workaround for the default insecure behavior of `wp-cli/wp-cli` versions before 2.5.0. The workaround for dealing with the breaking change in the commands directly affected by the new secure default behavior is to add the `--insecure` flag to manually opt-in to the previous insecure behavior."}]},"impact":{"cvss":{"attackComplexity":"LOW","attackVector":"NETWORK","availabilityImpact":"NONE","baseScore":9.1,"baseSeverity":"CRITICAL","confidentialityImpact":"HIGH","integrityImpact":"HIGH","privilegesRequired":"NONE","scope":"UNCHANGED","userInteraction":"NONE","vectorString":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.1"}},"problemtype":{"problemtype_data":[{"description":[{"lang":"eng","value":"CWE-295: Improper Certificate Validation"}]}]},"references":{"reference_data":[{"name":"https://github.com/wp-cli/wp-cli/security/advisories/GHSA-rwgm-f83r-v3qj","refsource":"CONFIRM","url":"https://github.com/wp-cli/wp-cli/security/advisories/GHSA-rwgm-f83r-v3qj"},{"name":"https://github.com/wp-cli/checksum-command/pull/86","refsource":"MISC","url":"https://github.com/wp-cli/checksum-command/pull/86"},{"name":"https://github.com/wp-cli/config-command/pull/128","refsource":"MISC","url":"https://github.com/wp-cli/config-command/pull/128"},{"name":"https://github.com/wp-cli/core-command/pull/186","refsource":"MISC","url":"https://github.com/wp-cli/core-command/pull/186"},{"name":"https://github.com/wp-cli/extension-command/pull/287","refsource":"MISC","url":"https://github.com/wp-cli/extension-command/pull/287"},{"name":"https://github.com/wp-cli/package-command/pull/138","refsource":"MISC","url":"https://github.com/wp-cli/package-command/pull/138"},{"name":"https://github.com/wp-cli/wp-cli/pull/5523","refsource":"MISC","url":"https://github.com/wp-cli/wp-cli/pull/5523"}]},"source":{"advisory":"GHSA-rwgm-f83r-v3qj","discovery":"UNKNOWN"}}},"adp":[{"providerMetadata":{"orgId":"af854a3a-2127-422b-91ae-364da2661108","shortName":"CVE","dateUpdated":"2024-08-03T22:11:05.507Z"},"title":"CVE Program Container","references":[{"tags":["x_refsource_CONFIRM","x_transferred"],"url":"https://github.com/wp-cli/wp-cli/security/advisories/GHSA-rwgm-f83r-v3qj"},{"tags":["x_refsource_MISC","x_transferred"],"url":"https://github.com/wp-cli/checksum-command/pull/86"},{"tags":["x_refsource_MISC","x_transferred"],"url":"https://github.com/wp-cli/config-command/pull/128"},{"tags":["x_refsource_MISC","x_transferred"],"url":"https://github.com/wp-cli/core-command/pull/186"},{"tags":["x_refsource_MISC","x_transferred"],"url":"https://github.com/wp-cli/extension-command/pull/287"},{"tags":["x_refsource_MISC","x_transferred"],"url":"https://github.com/wp-cli/package-command/pull/138"},{"tags":["x_refsource_MISC","x_transferred"],"url":"https://github.com/wp-cli/wp-cli/pull/5523"}]}]},"cveMetadata":{"assignerOrgId":"a0819718-46f1-4df5-94e2-005712e83aaa","assignerShortName":"GitHub_M","cveId":"CVE-2021-29504","datePublished":"2021-06-07T20:50:17.000Z","dateReserved":"2021-03-30T00:00:00.000Z","dateUpdated":"2024-08-03T22:11:05.507Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.1"}