Bug ID 603032: clientssl profiles with sni-default enabled may leak X509 objects

Last Modified: Aug 19, 2026

Affected Product(s):
BIG-IP All(all modules)

Known Affected Versions:
11.6.0, 11.6.0 hf1, 11.6.0 hf2, 11.6.0 hf3, 11.6.0 hf4, 11.6.0 hf5, 11.6.0 hf6, 11.6.0 hf7, 11.6.0 hf8, 11.6.1, 11.6.1 hf1, 11.6.1 hf2, 11.6.2, 11.6.2 hf1, 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.0.0 hf2, 12.0.0 hf3, 12.0.0 hf4, 12.1.0, 12.1.0 hf1, 12.1.0 hf2, 12.1.1, 12.1.1 hf1, 12.1.1 hf2

Fixed In:
13.0.0, 12.1.2

Opened: Jul 06, 2016

Severity: 2-Critical

Symptoms

SSL memory consumption grows when virtuals with sni-default-enabled clientssl profiles are modified.

Impact

The amount of leakage will depending on the number of virtuals with sni-default-enabled clientssl profiles and frequency of configuration manipulations. For large configurations, the leakage can be very noticeable over time.

Conditions

clientssl profile with sni-default enabled combined with configuration manipulations of virtuals with such profiles.

Workaround

No workaround short of not using sni-default.

Fix Information

SSL now handles sni-default-enabled clientssl profiles without leaking the X509 objects.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips