{ "Definition": [ { "ID": "oval:org.altlinux.errata:def:20231422", "Version": "oval:org.altlinux.errata:def:20231422", "Class": "patch", "Metadata": { "Title": "ALT-PU-2023-1422: package `wp-cli` update to version 2.7.1-alt1", "AffectedList": [ { "Family": "unix", "Platforms": [ "ALT Linux branch p11" ], "Products": [ "ALT Container" ] } ], "References": [ { "RefID": "ALT-PU-2023-1422", "RefURL": "https://errata.altlinux.org/ALT-PU-2023-1422", "Source": "ALTPU" }, { "RefID": "CVE-2021-29504", "RefURL": "https://nvd.nist.gov/vuln/detail/CVE-2021-29504", "Source": "CVE" } ], "Description": "This update upgrades wp-cli to version 2.7.1-alt1. \nSecurity Fix(es):\n\n * CVE-2021-29504: 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.", "Advisory": { "From": "errata.altlinux.org", "Severity": "High", "Rights": "Copyright 2024 BaseALT Ltd.", "Issued": { "Date": "2023-03-13" }, "Updated": { "Date": "2023-03-13" }, "BDUs": null, "CVEs": [ { "ID": "CVE-2021-29504", "CVSS": "AV:N/AC:L/Au:N/C:P/I:P/A:P", "CVSS3": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N", "Href": "https://nvd.nist.gov/vuln/detail/CVE-2021-29504", "Impact": "High", "Public": "20210607" } ], "AffectedCPEs": { "CPEs": [ "cpe:/o:alt:container:11" ] } } }, "Criteria": { "Operator": "AND", "Criterions": [ { "TestRef": "oval:org.altlinux.errata:tst:3001", "Comment": "ALT Linux must be installed" } ], "Criterias": [ { "Operator": "OR", "Criterions": [ { "TestRef": "oval:org.altlinux.errata:tst:20231422001", "Comment": "wp-cli is earlier than 0:2.7.1-alt1" } ] } ] } } ] }