Evidence-linked product lifecycle intelligenceSUPPORT · SECURITY · RETIREMENT
← Search results
CVE-LINKED INVENTORY98 SECURITY RECORDS

envoyproxy

envoy

Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.

Lifecycle evidence status

This identity is present in BlackTree CVE records, but no product-specific publisher support or retirement history is currently registered in Lifecycle.

A missing support date does not mean the product is supported. CVE publication dates and affected-version ranges must not be interpreted as EOL dates.

CVE-observed version history

CVEPublishedAffected versionsFixed version informationPublisher evidence
CVE-2024-39305 1 Jul 2024 >= 1.30.0, < 1.30.4; >= 1.29.0, < 1.29.7; >= 1.28.0, < 1.28.5; < 1.27.7 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2024-32974 4 Jun 2024 >= 1.30.0, <= 11.30.1; >= 1.29.0, <= 1.29.4; >= 1.28.0, <= 1.28.3; <= 1.27.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-32975 4 Jun 2024 >= 1.30.0, <= 11.30.1; >= 1.29.0, <= 1.29.4; >= 1.28.0, <= 1.28.3; <= 1.27.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-32976 4 Jun 2024 >= 1.30.0, <= 11.30.1; >= 1.29.0, <= 1.29.4; >= 1.28.0, <= 1.28.3; > 1.18.0, <= 1.27.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-34362 4 Jun 2024 >= 1.30.0, <= 11.30.1; >= 1.29.0, <= 1.29.4; >= 1.28.0, <= 1.28.3; <= 1.27.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-34363 4 Jun 2024 >= 1.30.0, <= 11.30.1; >= 1.29.0, <= 1.29.4; >= 1.28.0, <= 1.28.3 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-34364 4 Jun 2024 >= 1.30.0, <= 11.30.1; >= 1.29.0, <= 1.29.4; >= 1.28.0, <= 1.28.3; <= 1.27.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-23326 4 Jun 2024 >= 1.13.0, <= 1.30.1; >= 1.29.0, <= 1.29.4; >= 1.28.0, <= 1.28.3; <= 1.27.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-32475 18 Apr 2024 >= 1.30.0, < 11.30.1; >= 1.29.0, < 1.29.4; >= 1.28.0, < 1.28.3; >= 1.13.0, < 1.27.5 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2024-30255 4 Apr 2024 >= 1.29.0, < 1.29.3; >= 1.28.0, < 1.28.2; >= 1.27.0, < 1.27.4; < 1.26.8 Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 Update reference ↗
CVE-2024-27919 4 Apr 2024 >= 1.29.0, < 1.29.2 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2024-23322 9 Feb 2024 >= 1.29.0, < 1.29.1; >= 1.28.0, < 1.28.1; >= 1.27.0, < 1.27.3; < 1.26.7 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2024-23323 9 Feb 2024 >= 1.29.0, < 1.29.1; >= 1.28.0, < 1.28.1; >= 1.27.0, < 1.27.3; < 1.26.7 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2024-23324 9 Feb 2024 >= 1.29.0, < 1.29.1; >= 1.28.0, < 1.28.1; >= 1.27.0, < 1.27.3; < 1.26.7 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2024-23325 9 Feb 2024 >= 1.29.0, < 1.29.1; >= 1.28.0, < 1.28.1; >= 1.27.0, < 1.27.3; < 1.26.7 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2024-23327 9 Feb 2024 >= 1.29.0, < 1.29.1; >= 1.28.0, < 1.28.1; >= 1.27.0, < 1.27.3; < 1.26.7 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2023-35944 25 Jul 2023 >= 1.26.0, < 1.26.4; >= 1.25.0, < 1.25.9; >= 1.24.0, < 1.24.10; < 1.23.12 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-35943 25 Jul 2023 >= 1.26.0, < 1.26.4; >= 1.25.0, < 1.25.9; >= 1.24.0, < 1.24.10; < 1.23.12 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-35942 25 Jul 2023 >= 1.26.0, < 1.26.4; >= 1.25.0, < 1.25.9; >= 1.24.0, < 1.24.10; < 1.23.12 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-35941 25 Jul 2023 >= 1.26.0, < 1.26.4; >= 1.25.0, < 1.25.9; >= 1.24.0, < 1.24.10; < 1.23.12 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-35945 13 Jul 2023 >= 1.26.0, < 1.26.3; >= 1.25.0, < 1.25.8; >= 1.24.0, < 1.24.9; >= 1.23.0, < 1.23.11 The CVE's listed above affect the PostgresSQL pgadmin tool. If you have installed this tool, not required by EcoStruxure™ Power Operation 2024, we recommend you uninstall it from your EPO server and client machines.We strongly recommend customers take the following actions:• If waveform analysis and ETAP simulation features are not used, uninstall PostgreSQLOR• For those customers using waveform analysis and ETAP simulation features, we recommend all deployments of EPO only accept connections from localhost in PostgresSQL. Contact customer care for information on how to modify PostgreSQL. Further, we recommend you manually uninstall PostgreSQL 14.10 and update to PostgreSQL 14.17 or higher. EcoStruxure™ Power Operation 2024 CU2 includes an updated version of PostgreSQL and is available for download here: https://community.se.com/t5/EcoStruxure-Power-Operation/v2024-Release-amp-Updates-Install-Procedure/m-p/478928/thread-id/6997#M6997 Update reference ↗
CVE-2023-27496 4 Apr 2023 >= 1.25.0, < 1.25.3; >= 1.24.0, < 1.24.4; >= 1.23.0, < 1.23.6; < 1.22.9 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-27493 4 Apr 2023 >= 1.25.0, < 1.25.3; >= 1.24.0, < 1.24.4; >= 1.23.0, < 1.23.6; < 1.22.9 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-27492 4 Apr 2023 >= 1.25.0, < 1.25.3; >= 1.24.0, < 1.24.4; >= 1.23.0, < 1.23.6; < 1.22.9 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-27491 4 Apr 2023 >= 1.25.0, < 1.25.3; >= 1.24.0, < 1.24.4; >= 1.23.0, < 1.23.6; < 1.22.9 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-27488 4 Apr 2023 >= 1.25.0, <1.25.3; >= 1.24.0, < 1.24.4; >= 1.23.0, < 1.23.6; < 1.22.9 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2023-27487 4 Apr 2023 >= 1.25.0, <1.25.3; >= 1.24.0, < 1.24.4; >= 1.23.0, < 1.23.6; < 1.22.9 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-29227 9 Jun 2022 < 1.22.1 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2022-29226 9 Jun 2022 < 1.22.1 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2022-29228 9 Jun 2022 < 1.22.1 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2022-29225 9 Jun 2022 < 1.22.1 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2022-29224 9 Jun 2022 < 1.22.1 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2021-43826 22 Feb 2022 < 1.18.6; >= 1.19.0, < 1.19.3; >= 1.20.0, < 1.20.2; >= 1.21.0, < 1.21.1 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2021-43825 22 Feb 2022 < 1.18.6; >= 1.19.0, < 1.19.3; >= 1.20.0, < 1.20.2; >= 1.21.0, < 1.21.1 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2022-21655 22 Feb 2022 < 1.18.6; >= 1.19.0, < 1.19.3; >= 1.20.0, < 1.20.2; >= 1.21.0, < 1.21.1 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2022-21654 22 Feb 2022 >= 1.7.0, < 1.18.6; >= 1.19.0, < 1.19.3; >= 1.20.0, < 1.20.2; >= 1.21.0, < 1.21.1 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2022-21657 22 Feb 2022 >= 1.20.0, < 1.20.2; >= 1.19.0, < 1.19.3; < 1.18.6 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2022-21656 22 Feb 2022 < 1.20.2 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2022-23606 22 Feb 2022 >= 1.20.0, < 1.20.2; >= 1.21.0, < 1.21.1 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2021-43824 22 Feb 2022 >= 1.20.0, < 1.20.2; >= 1.19.0, < 1.19.3; < 1.18.6; >= 1.21.0, < 1.21.1 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2021-32780 24 Aug 2021 >= 1.19.0, < 1.19.1; >= 1.18.0, < 1.18.4 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2021-32781 24 Aug 2021 >= 1.19.0, < 1.19.1; >= 1.18.0, < 1.18.4; >= 1.17.0, < 1.17.4; >= 1.16.0, < 1.16.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2021-32779 24 Aug 2021 >= 1.19.0, < 1.19.1; >= 1.18.0, < 1.18.4; >= 1.17.0, < 1.17.4; >= 1.16.0, < 1.16.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2021-32778 24 Aug 2021 >= 1.19.0, < 1.19.1; >= 1.18.0, < 1.18.4; >= 1.17.0, < 1.17.4; >= 1.16.0, < 1.16.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2021-32777 24 Aug 2021 >= 1.19.0, < 1.19.1; >= 1.18.0, < 1.18.4; >= 1.17.0, < 1.17.4; >= 1.16.0, < 1.16.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2021-29492 28 May 2021 <= 1.18.2 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2021-21378 11 Mar 2021 = 1.17.0 1.17.1 Update reference ↗
CVE-2020-15104 14 Jul 2020 < 1.12.6; >= 1.13.0, < 1.13.4; >= 1.14.0, < 1.14.4 No fixed version is explicitly recorded in the structured CVE data. Use CVE record

How this record is maintained

The CVE inventory is reconciled automatically from cve.blacktree.nl. Exact identity matches link to existing Lifecycle product or package histories. Unmatched products stay in a prioritised publisher-source research queue, and Lifecycle marks the date gap instead of inferring a support boundary from vulnerability data.