Summary
A vulnerability in libcurl allows stale Host header state to persist across requests when reusing the same easy handle. If a custom Host: header is set for an initial request and not explicitly cleared before a subsequent request to a different host, libcurl may incorrectly include cookies associated with the original host in the follow-up request. This can result in unintended cross-domain cookie leakage, potentially exposing sensitive session information under specific application configurations that reuse connections and manipulate request headers.
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
|
Yes
|
|
ExtremeCloud IQ - Site Engine (XIQ-SE)
|
Yes
|
|
ExtremeControl for Site Engine
|
Yes
|
Repair Recommendations
ExtremeAnalytics for Site Engine:
Fixed in 26.6.11 or later.
ExtremeCloud IQ - Site Engine (XIQ-SE):
Fixed in 26.6.11 or later.
ExtremeControl for Site Engine:
Fixed in 26.6.11 or later.
Please see the full Security Advisory here for more details and future updates.
