Summary
PHP uses longjmp() for out-of-memory (OOM) errors to exit the current context and abort handling of the request. Some contexts may not properly account for this scenario and leave request memory in an uninitialized state before performing an allocation. The subsequent request cleanup procedure may read or branch on this memory. Multiple OOM strategies can consistently trigger this condition and lead to remote code execution (RCE).
Products not listed in the Impact Details section have not been evaluated. Furthermore, products that have exceeded any software maintenance time periods are also not evaluated and will not be published. Please consult End of Sale and End of Service Life - Extreme Networks for the EOL notices related to the product under question.
Products Potentially Affected
None
Impact Details
|
OS/Product
|
Exposure
|
|
ExtremeAnalytics for Site Engine
|
No
|
|
ExtremeCloud IQ (XIQ)
|
No
|
|
ExtremeCloud IQ - Site Engine (XIQ-SE)
|
No
|
|
ExtremeCloud Orchestrator (XCO/EFA)
|
No
|
|
Extreme Platform ONE
|
No
|
|
Extreme AirDefense
|
No
|
|
ExtremeCloud A3
|
No
|
|
ExtremeCloud Universal ZTNA
|
No
|
|
ExtremeControl for Site Engine
|
Investigating
|
|
ExtremeCloud SD-WAN Appliance
|
No
|
|
ExtremeCloud SD-WAN Orchestrator
|
No
|
|
Extreme OS ONE
|
No
|
|
Fabric Engine (VOSS)
|
No
|
|
SLX-OS
|
No
|
|
Switch Engine (EXOS)
|
No
|
|
CampusWirelessAP
|
No
|
|
ExtremeCloud IQ Controller (IQC/XCC)
|
No
|
|
IQ Engine (HiveOS)
|
Investigating
|
|
WiNG
|
Investigating
|
Repair Recommendations
None
Please see the full Security Advisory here for more details and future updates.
