HPE Aruba Networking EdgeConnect SD-WAN Orchestrator

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

CVE	Published	Affected versions	Fixed version information	Publisher evidence
CVE-2024-22444	24 Jul 2024	EdgeConnect SD-WAN Orchestrator 9.4.x: Orchestrator 9.4.1 (all builds) and below ≤ <=9.4.1; EdgeConnect SD-WAN Orchestrator 9.3.x: Orchestrator 9.3.2 (all builds) and below ≤ <=9.3.2; EdgeConnect SD-WAN Orchestrator 9.2.x: Orchestrator 9.2.9 (all builds) and below ≤ <=9.2.9; EdgeConnect SD-WAN Orchestrator 9.1.x: Orchestrator 9.1.9 (all builds) and below ≤ <=9.1.9	Please note that due to the structure of this specific vulnerability HPE Aruba Networking has patched them only in the following software branches and versions of Orchestrator: - Orchestrator 9.3.x: Orchestrator 9.3.1 (all builds) and above - Orchestrator 9.4.x: Orchestrator 9.4.0 (all builds) and above - Orchestrator 9.5.x: Orchestrator 9.5.0 (all builds) and above Older branches and branches not specifically named are not patched. Customers running an Orchestrator release before 9.3.x should refer to these instructions: https://www.arubanetworks.com/techdocs/sdwan-PDFs/docs/advisories/ec_adv_sec_settings_latest.pdf	Update reference ↗
CVE-2024-22443	24 Jul 2024	EdgeConnect SD-WAN Orchestrator 9.4.x: Orchestrator 9.4.1 (all builds) and below ≤ <=9.4.1; EdgeConnect SD-WAN Orchestrator 9.3.x: Orchestrator 9.3.2 (all builds) and below ≤ <=9.3.2; EdgeConnect SD-WAN Orchestrator 9.2.x: Orchestrator 9.2.9 (all builds) and below ≤ <=9.2.9; EdgeConnect SD-WAN Orchestrator 9.1.x: Orchestrator 9.1.9 (all builds) and below ≤ <=9.1.9	Please note that due to the structure of this specific vulnerability HPE Aruba Networking has patched them only in the following software branches and versions of Orchestrator: - Orchestrator 9.1.x: Orchestrator 9.1.10 (all builds) and above - Orchestrator 9.2.x: Orchestrator 9.2.10 (all builds) and above - Orchestrator 9.3.x: Orchestrator 9.3.3 (all builds) and above - Orchestrator 9.4.x: Orchestrator 9.4.2 (all builds) and above - Orchestrator 9.5.x: Orchestrator 9.5.0 (all builds) and above Older branches and branches not specifically named are not patched. Customers running an Orchestrator release before 9.3.x should refer to these instructions: https://www.arubanetworks.com/techdocs/sdwan-PDFs/docs/advisories/ec_adv_sec_settings_latest.pdf	Update reference ↗
CVE-2024-41914	24 Jul 2024	EdgeConnect SD-WAN Orchestrator 9.4.x: Orchestrator 9.4.1 (all builds) and below ≤ <=9.4.1; EdgeConnect SD-WAN Orchestrator 9.3.x: Orchestrator 9.3.2 (all builds) and below ≤ <=9.3.2; EdgeConnect SD-WAN Orchestrator 9.2.x: Orchestrator 9.2.9 (all builds) and below ≤ <=9.2.9; EdgeConnect SD-WAN Orchestrator 9.1.x: Orchestrator 9.1.9 (all builds) and below ≤ <=9.1.9	Please note that due to the structure of this specific vulnerability HPE Aruba Networking has patched them only in the following software branches and versions of Orchestrator: - Orchestrator 9.3.x: Orchestrator 9.3.1 (all builds) and above - Orchestrator 9.4.x: Orchestrator 9.4.0 (all builds) and above - Orchestrator 9.5.x: Orchestrator 9.5.0 (all builds) and above Older branches and branches not specifically named are not patched. Customers running an Orchestrator release before 9.3.x should refer to these instructions: https://www.arubanetworks.com/techdocs/sdwan-PDFs/docs/advisories/ec_adv_sec_settings_latest.pdf	Update reference ↗

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.