Last Modified: Sep 13, 2023
Affected Product(s):
BIG-IP APM
Known Affected Versions:
11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.1 HF10, 11.5.1 HF11, 11.5.2 HF1, 11.5.3 HF1, 11.5.3 HF2, 11.5.4 HF1, 11.5.4 HF2, 11.6.0, 11.6.1, 11.6.2, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4, 11.6.5, 11.6.5.1, 11.6.5.2, 11.6.5.3, 12.0.0, 12.0.0 HF1, 12.1.0 HF1, 12.0.0 HF2, 12.1.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.1 HF1, 12.1.1 HF2
Fixed In:
13.0.0, 12.1.2 HF1, 11.6.1 HF2, 11.5.4 HF3
Opened: Aug 10, 2016 Severity: 3-Major
When BIG-IP is used as SAML SP, and SLO is not properly configured on associated saml-idp-connector objects, IdP initiated SAML SLO may result in memory leak in SSO plugin.
SSO plugin leaks memory
- BIG-IP is used as SP. - Associated saml-idp-connector object has 'single-logout-uri' property configured, but 'single-logout-response-uri' property is empty. - User performs IdP initiated SAML SLO
There are two possible workarounds: - Fix misconfiguration: Configure SLO correctly by adding value to 'single-logout-response-uri' property of IdP connector object. - Disable SLO by removing single-logout-uri' property of IdP connector object.
When fixed, memory will no longer leak in SSO plugin even when SLO is misconfigured.