Last Modified: Sep 13, 2023
Affected Product(s):
BIG-IP SWG
Known Affected Versions:
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, 12.1.2 HF1, 12.1.2 HF2, 12.1.0, 12.1.1
Fixed In:
13.0.0, 12.1.2
Opened: Dec 11, 2015 Severity: 3-Major Related Article:
K05489319
When certain end user interface pages (e.g. 401 response) are served by the APM, these include a unique parameter in the URL. This results in the leak of objects representing caches for these pages, because their unique parameter renders caching ineffective.
A memory leak in the TMM.
This occurs when the following conditions are met: -- Use of SWG in Transparent mode. -- One of the following: + Use a logon page agent, an external logon page agent, or a 401 agent in the access policy. + Trigger an access policy evaluation when one is already in progress or when accessing a page that requires an established session.
None (when the triggering conditions are encountered).
This release corrects the possible memory exhaustion issue in access end-user interface pages for transparent proxy/SWG cases.